How to decrypt an old password-protected pdf
- Step 1Recover the old password from your records — Check your password manager, old email, the application that created the file, or any documentation. Old passwords don't expire — if one doesn't work, it's likely recorded with a typo or case difference.
- Step 2Open the Remove Password tool — Go to the PDF Remove Password tool. The qpdf engine loads once, then is cached.
- Step 3Add the archived PDF — Drop in the single old file. It stays in the browser tab — nothing is uploaded, which matters for sensitive archived records.
- Step 4Enter the password — Type the recovered password in the Enter current password field. Either the open or the owner password works.
- Step 5Decrypt and verify — Run it. qpdf reads the RC4 or AES encryption and returns an open copy. Re-open it to confirm the prompt is gone and the content is intact.
- Step 6Convert to PDF/A for archival (optional) — For long-term retention, send the decrypted copy to the PDF/A converter so it remains readable for decades, then store it in your access-controlled archive.
Encryption by PDF era
Roughly which handler your archived file uses, and whether the decrypt pass reads it.
| Era / source | Likely encryption | Read with the password? |
|---|---|---|
| Pre-2008 PDFs, old Acrobat | RC4 40-bit or RC4 128-bit | Yes |
| ~2009–2015 exports | AES-128 | Yes |
| Modern (2016+) Acrobat / Word | AES-256 | Yes |
| Office / LibreOffice exports | AES-128 / AES-256 | Yes |
| Enterprise rights management | LiveCycle / AEM DRM | No — needs the issuing server |
Archive decrypt: behaviour and limits
What happens to an old file and the tier ceilings on input size.
| Aspect | Detail |
|---|---|
| Content fidelity | Byte-identical pages/text/images — decryption only, no re-render |
| Password accepted | User (open) or owner password |
| Output | Unencrypted PDF, no /Encrypt dictionary |
| Free tier | 2 MB / 50 pages per file |
| Pro tier | 50 MB / 500 pages per file |
| Pro + Media | 500 MB / 2,000 pages per file |
| Recommended next step | PDF/A conversion for long-term retention |
Cookbook
Decrypting the kinds of old files that accumulate in archives.
A 2013 tax return locked with RC4-128
An old tax PDF used RC4 128-bit. A current viewer warned about weak encryption but still asked for the password. Supply it and qpdf decrypts cleanly.
Input: tax-2013.pdf (RC4 128-bit) Field: Enter current password → <old password> Action: qpdf --password=… --decrypt Output: tax-2013.pdf, unencrypted, pages identical
Half-remembered owner password
You set both passwords years ago and only the owner password is in your notes. It decrypts the file just the same.
Input: board-minutes-2011.pdf (user + owner pw) Field: Enter current password → <owner password> Action: qpdf --decrypt → success (owner pw accepted) Output: open copy, ready to archive
Decrypt then convert to PDF/A for retention
After decrypting, run the open copy through PDF/A so it stays readable for the legally required retention period.
Step 1: decrypt old-statement.pdf here → open copy
Step 2: open copy → PDF/A converter → PDF/A-2b
Result: ISO-19005 archival file, no password,
durable for long-term storagePassword recorded with a case typo
The documented password fails because it was noted in the wrong case. Passwords are case-sensitive — try the exact casing you used originally.
Tried: Archive2010 → fails Tried: archive2010 → fails Tried: ARCHIVE2010 → success Lesson: passwords are case-sensitive; test variants
Old file is corrupted, not just locked
Years of storage left the file with a broken cross-reference table. Repair it first, then decrypt the repaired copy.
Decrypt directly → exit 2 ("could not process")
Step 1: PDF Repair → rebuilt cross-reference table
Step 2: decrypt the repaired copy with the password
Result: open, readable archive fileEdge cases and what actually happens
Password is genuinely lost
Not supportedThe tool decrypts only with the correct password and performs no cracking or recovery. For a strongly encrypted archive (AES), a lost password means the content is effectively unrecoverable — which is exactly what encryption is for. Exhaust your records and the original source application first.
Documented password fails (case/whitespace)
errorqpdf exits with code 2 and reports it could not process the file. Old passwords are often recorded with a case difference or a trailing space. Try the exact original casing and trim any stray spaces before re-running.
Legacy RC4 40-bit file
SupportedVery old PDFs use RC4 40-bit, which some current tools won't touch. qpdf reads it with the password and decrypts normally — this is a common reason to use this tool on archives specifically.
Owner password works without the user password
SupportedBy design, qpdf accepts either password for --decrypt. A half-remembered owner password from years ago unlocks the file fully; you don't need to find the open password as well.
File degraded in storage (corrupted)
errorBit-rot or a truncated copy can fail with the same exit-2 message even with the right password. Run PDF Repair to rebuild the structure, then decrypt the repaired copy.
Empty password field
Enter the current password.Running without a password stops at "Enter the current password." An encrypted archive file needs its password to decrypt.
Free-tier 2 MB / 50-page cap
LimitLarge scanned archives often exceed the free 2 MB / 50-page limit. Pro (50 MB / 500 pages) or Pro+Media (500 MB / 2,000 pages) handles bigger historical documents.
Decrypted but not yet archival-grade
By designDecryption removes the password but doesn't make a file PDF/A-compliant. For retention requirements, run the decrypted copy through the PDF/A converter so embedded fonts and colour are self-contained for the long term.
Server-DRM legacy document
Not supportedSome old enterprise PDFs used LiveCycle rights management rather than a password. If the original rights server is decommissioned, the document may be permanently inaccessible — this tool can't decrypt server-enforced DRM.
Frequently asked questions
What encryption was used in older PDFs?
PDFs from before roughly 2008 commonly used RC4 40-bit or RC4 128-bit. Files from around 2009 onward shifted to AES-128, and modern files use AES-256. This tool reads all of them — provided you supply the correct password. Legacy RC4 support is a key reason it works on old archives where newer tools sometimes don't.
Should I keep the original protected copy?
Until you've verified the decrypted copy opens and the content is intact, yes — keep the encrypted master. After verification, decide based on sensitivity: keep only the unlocked copy in an access-controlled archive, or retain both. Don't leave an unencrypted sensitive file in an unsecured folder.
What if the old password no longer works?
Passwords don't expire, so a failure almost always means it was recorded incorrectly — most often a case difference or a trailing space. Passwords are case-sensitive. Try the exact original casing and several plausible variants. If the file is truly corrupted rather than just locked, run PDF Repair first.
Will decrypting change the document's content?
No. qpdf removes only the encryption layer. Pages, text, scanned images, embedded fonts, and bookmarks are preserved byte-for-byte — there's no re-rendering or recompression, which matters for archival fidelity.
Are my archived documents uploaded?
No. The qpdf WebAssembly module and the decryption run inside your browser tab. The archived file and the password never leave your device. Only an anonymous usage count is recorded when you're signed in.
Can I use the owner password if I've lost the open one?
Yes. qpdf accepts either the user or owner password for decryption. If your notes only have the owner password from years ago, it unlocks the file completely — you don't also need the open password.
Should I convert decrypted files to PDF/A?
For long-term retention, yes. Decryption removes the password, but PDF/A (ISO 19005) is what guarantees the file stays renderable for decades by embedding fonts and standardising colour. Decrypt here, then run the open copy through the PDF/A converter.
How large an archived PDF can I decrypt?
Free tier handles up to 2 MB / 50 pages. Large scanned archives usually need Pro (50 MB / 500 pages) or Pro+Media (500 MB / 2,000 pages). The cap applies to the input file.
What does "qpdf could not process this PDF" mean for an old file?
Either the password was wrong (check case/whitespace) or the file degraded in storage and is now corrupted. For the latter, PDF Repair rebuilds the cross-reference table; decrypt the repaired copy afterward.
Can it remove the password from an old file with server DRM?
No. If the file used Adobe LiveCycle / rights-management DRM rather than a standard password, decryption requires the original rights server. If that server is gone, the document may be permanently locked — this is a limitation of server-enforced DRM, not of this tool.
Is decrypting my own old PDF legal?
Yes. Removing protection from a document you own or are authorised to access, using a password you hold, is entirely legal. The tool requires the password, so it can only ever decrypt files you can already access.
Can I batch-decrypt a whole archive folder?
The browser tool processes one file per run. For a large archive, automate it on a paid tier: fetch the schema from GET /api/v1/tools/pdf-remove-password, pair the @jadapps/runner, and POST each file with { "password": "…" } to 127.0.0.1:9789/v1/tools/pdf-remove-password/run. The runner decrypts locally on your machine — archive contents stay private.
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.