A private PDF workflow, from password to download.

1. Pick a PDF

Choose a PDF from your device or drag it into the unlocker. Your browser reads the file privately from local storage using the standard File API. The site does not send it to an upload API, cloud drive, or third-party processing service — there is simply no endpoint for your document to travel to.

2. Provide the password

When the PDF asks for a password, the in-browser PDF engine uses the password you enter to open the document. The password input is not saved, logged, or transmitted. It exists only in the tab’s memory for as long as the tool is working, and it is gone when you close the tab.

3. Rebuild an unlocked copy

After the document opens, the tool produces a new PDF without an open-password prompt and hands it to your browser as a normal download. How that new file is produced depends on the method you choose — which brings us to the most important choice on this page.

Image-based vs. direct decryption

The tool offers two ways to create the unlocked copy, and they make different trade-offs:

• Image-based (default). Each page is rendered and placed into a fresh PDF as a high-quality image. This is the most compatible option and works with a wide range of PDFs, but because pages become images, it can flatten selectable text, form fields, annotations, bookmarks, layers, and accessibility tags. It is ideal when you mainly need to view, print, or share the visual document.
• Direct decryption. This removes the open-password protection while keeping more of the original PDF structure intact — so selectable text, forms, and metadata are more likely to survive. Choose it when those interactive or text features matter, for example a fillable form or a contract you will search and copy from.

A simple rule of thumb: if you just need to see or print the document, image-based is fine; if you need to edit, search, or fill it, prefer direct decryption.

What “processed in your browser” really means

The heavy lifting is done by PDF libraries compiled to WebAssembly (Wasm) and JavaScript that run inside your browser tab. WebAssembly is a fast, sandboxed runtime built into every modern browser; it lets code that would normally live on a server execute locally on your device instead. In practice, that means the bytes of your PDF and the password you type are handled by code running on your own machine, not on ours. The website itself is delivered as static files, so there is no application server sitting in the middle of your document.

What stays private?

• The original PDF bytes stay in your browser tab.
• The password is held in memory only while the tool runs, then discarded.
• There is no sign-up, tracking form, or backend upload route for your document.

The website does use Google Analytics and Google AdSense for the site itself, which set cookies and collect standard usage data. That is separate from your document, which the ad and analytics code never sees. The details are in our Privacy Policy.

Important limitations

Because the image-based flow rebuilds pages visually, the output may flatten selectable text, interactive forms, annotations, bookmarks, layers, and accessibility tags. If you need those preserved, use direct decryption or a trusted desktop PDF application. The tool also cannot recover a forgotten password or bypass permission restrictions — you must supply the current open password. Only unlock files you own or are authorized to access.

When a desktop app is the better choice

A browser tool is convenient for one-off documents and for keeping files off remote servers. But a desktop application such as Adobe Acrobat, or Preview on a Mac, is worth using when you need to preserve complex forms, accessibility structure, or digital signatures, or when you routinely process large batches. There is no single "best" method — the right one depends on what you need the unlocked file to do. Our guide on removing a PDF password compares the options in more detail.