Take the password off a PDF.
Drop in a protected file, type the password you already know, and get back a clean, unrestricted PDF — with the text, fonts and layout completely untouched. Nothing is uploaded, because there is no server to upload it to.
Loading the PDF engine…
Most “free PDF unlockers” want your file
They upload it to a server, process it there, and ask you to trust a privacy policy. For a bank statement, a payslip or a contract, that is a genuinely bad trade. This one is built the other way round.
qpdf is compiled to WebAssembly and shipped to your browser as a 1.3 MB file. Decryption happens in a worker thread inside your tab. There is no upload endpoint in the code — check the network panel yourself.
Tools that convert your pages to images to strip protection destroy selectable text and balloon the file size. qpdf decrypts the real objects and rewrites the structure, so what comes out is what went in, minus the lock.
Once the page has loaded you can turn off your connection and keep unlocking files. That is the clearest possible demonstration that nothing is being sent anywhere.
How to remove a PDF password
Drag a protected PDF onto the box above, or click to browse. Several files at once is fine — they queue up and are handled one after another.
If the document needs one to open, a field appears. If it only carries printing or copying restrictions, GetPDF spots that and removes them without asking for anything.
You get back yourfile-unlocked.pdf — same pages, same text, same fonts, no password prompt and no permission flags.
What PDF encryption actually is
A protected PDF is not a zip file with a password on the outside. The encryption is part of the document format: an /Encrypt dictionary in the file's trailer describes the algorithm and key length, and the content streams and strings inside the file are individually encrypted against a key derived from your password.
What GetPDF does, step by step
- Reads the first kilobyte to confirm the file really is a PDF.
- Asks qpdf whether the document is encrypted but openable without a password — the owner-restrictions case.
- If not, tries to open it with no password at all. Success means the file was never protected.
- If that fails and an
/Encryptdictionary is present, it asks you for the password and passes it to qpdf. - On success qpdf writes a decrypted copy, which is handed to you as a download and then dropped from memory.
Read the longer write-up in how it works, including what to do when you do not have the password at all.
Questions people actually ask
No. GetPDF ships a copy of qpdf compiled to WebAssembly, and that engine runs inside your browser tab. Your file is read from disk into memory, decrypted there, and handed back as a download. Open your browser's network tab while you use it — after the page and the 1.3 MB engine have loaded, there are no further requests. You can also disconnect from the internet entirely and it will still work.
For a document open password, yes — this is not a cracking tool and it will not guess or brute-force anything. If the PDF only carries owner restrictions (it opens fine but blocks printing, copying or editing), no password is needed and GetPDF removes those restrictions on its own.
A user password — sometimes called the document open password — is required to view the file at all. An owner password leaves the file readable but sets permission flags that block printing, copying text, extracting pages or annotating. A PDF can have either, both, or neither. GetPDF detects which case it is looking at and tells you.
None. qpdf decrypts the document's existing objects and rewrites the file structure — it does not re-render, rasterise or recompress anything. Text stays selectable, vectors stay sharp, fonts and images are the originals, and form fields, bookmarks and links survive. The output is byte-for-byte the same content without the encryption layer.
Yes. Drop as many as you like and they queue up. If they share a password, tick “Try this password on every locked file” once and the rest unlock without you retyping it.
It depends entirely on the document and where you are. Removing protection from a file you own, or one you have been given permission to use — your own bank statement, a payslip, a document your employer sent you — is normally fine. Stripping protection from someone else's copyrighted or confidential material is not. You are responsible for having the right to do what you do here.
The engine works in your browser's memory, so very large files depend on your device. The interface caps uploads at 100 MB, which covers the overwhelming majority of statements, reports and scanned documents. A machine with plenty of RAM will handle the top of that range comfortably.