Protected PDF Keeps Asking for Password
Drop your PDF here or click to browse
Supports PDF files up to 10MB
Password-protect your PDF in seconds — no registration, no uploads
You protected a PDF and sent it to a colleague. They entered the password, the file opened — and then every time they closed and reopened it, the reader asked for the password again. Or it prompted a second time mid-session while scrolling through the document.
The protected PDF is not broken and the password is not wrong. A PDF that keeps asking for the password is almost always a reader-side behavior: how the recipient's PDF viewer handles session caching, not a flaw in the file's encryption.
Understanding the cause takes the guesswork out of fixing it.
Protect your PDF — free, standard encryption
No repeated prompts. Works across readers. No account needed.
Protect PDF Now — Free →How to Diagnose and Fix the Repeated Prompt
- Ask the recipient which app they use to open the PDF.
- Have them try the same file in Chrome's built-in PDF viewer.
- If the prompting stops in Chrome, the issue is the original reader's settings.
- If it persists in Chrome too, re-protect the file with a different tool.
- Test the replacement file in two readers before resending.
Most cases resolve at step 2 or 3. Chrome, Firefox, and Edge all cache the password for the current session automatically — no settings changes required.
[IMAGE: Chrome's PDF viewer opening a protected PDF with no repeated prompt, compared with an older reader asking for the password again on the second page]
Why a Protected PDF Keeps Prompting
The reader does not cache the password between sessions. PDF viewers are supposed to store the decryption key in memory for the current session so the file does not re-prompt on each open or page navigation. Some older readers — and corporate document management systems — do not do this by default. The recipient would need to find and enable session caching in the reader's preferences, if that option exists.
The file uses non-standard encryption headers. Some free online PDF protectors generate encryption output that is technically valid but unusual enough that certain readers re-validate the credential on every render cycle. The result is a repeated prompt even when the password is correct. This overlaps with the same issue that causes a protected PDF that will not open on some devices — the reader's parser is being cautious about headers it does not recognize.
Both an open password and a permissions password are active. PDFs can carry two distinct passwords: a user password to open the file, and an owner password to control printing, copying, and editing. A reader that checks both on each interaction may re-prompt if the session cache stores only one credential. This is uncommon in modern readers but appears in older Acrobat versions and some legal document platforms.
Special characters in the password. On older operating systems, some readers have encoding issues with passwords containing characters outside standard ASCII. The credential appears to validate on first open but gets re-processed differently on the next load. Re-protecting with a plain alphanumeric password is a quick way to rule this out.
How to Prevent It Next Time
Use a tool that produces standard AES encryption. Free, no registration, no paywall at download — you can protect a PDF at signmypdf.io/protect using AES-128 per the PDF specification, which every modern reader handles without repeated prompts.
Test before sending. Open the protected file in Chrome, Firefox, and one other reader. If none of them re-prompt, the recipient's experience should be the same. One minute of testing prevents a back-and-forth support call.
Stick to alphanumeric passwords for frequently-accessed documents. Special characters are fine for security, but if the file is opened dozens of times by different people on different systems, a simpler password reduces the chance of encoding edge cases.
Re-protect if the issue persists. If the file was protected with a tool that generated non-standard headers, protect a fresh copy using a standard tool and resend. For a deeper look at what the encryption is actually doing, is your password-protected PDF actually secure gives an honest breakdown of what AES-128 protects against.
FAQ
Why does the PDF open fine for me but prompt the recipient repeatedly? Your reader — likely Chrome or a recent version of Acrobat — caches the password session automatically. Their reader does not. Tell them to try opening the file directly in Chrome or Firefox, both of which handle this transparently.
Can I remove the password and re-protect the file? Yes, if you have the original unprotected version. Re-apply protection with a standard tool and test first. If you only have the protected copy and need to remove the password, you will need the password itself — options when you have forgotten your PDF password covers what is realistic.
Does this happen with all PDF protection tools? No. Tools that produce standard encryption headers are handled consistently by modern readers. The repeated-prompt problem is most common with niche or older tools that generate slightly non-standard encryption metadata.
Protect your PDF the right way — free
Standard AES encryption. No registration. No repeated prompts.
Protect PDF Now — Free →