The Bad Parameter Error
Why Acrobat refuses to password-protect your PDF.
The Short Answer
The message is The document could not be saved. Bad parameter. It has nothing to do with your password being invalid. Acrobat is telling you it cannot write the file.
Nine times out of ten the document is already digitally signed, and encrypting it would break that signature.
Encrypt a PDF without Acrobat →Cause 1: The Document Is Already Signed
A digital signature is a cryptographic fingerprint of the entire file. Encryption rewrites the file. The two cannot both survive, so Acrobat stops rather than handing you a document whose signature will show as invalid.
This catches people constantly with documents that arrive from e-signature platforms, because those files come back signed and you cannot then add protection to them.
Fix: the order matters. Password-protect first, then sign. If the document is already signed and you need it encrypted, you have to accept losing the signature.
Cause 2: The File Structure Is Damaged
PDF viewers repair a lot of damage silently as they render. The moment Acrobat has to write the file rather than display it, inconsistencies in the cross-reference table or the tag tree become fatal.
The tell is a file that opens and looks perfect but fails every save operation, not just encryption. If rotating or merging the same document also errors, the file is the problem.
Fix: produce a clean rewrite. Open the document and print it to PDF. This generates a fresh file with a valid structure.
Cause 3: An Empty or Content-Free Page
Less common, but real: a PDF with a page carrying no content stream at all can trigger the same error. This usually comes from documents assembled by scripts or exported from a system that produced a placeholder page.
Fix: delete the empty page, or split the document and check which section fails.
Working Out Which One You Have
| Symptom | Likely cause |
|---|---|
| Signature panel shows a signature | Already signed |
| Other save operations fail too | Damaged structure |
| Came back from an e-signature service | Already signed |
| Assembled by a script or export job | Damaged, or an empty page |
Skipping the Problem Entirely
Every cause above is Acrobat struggling to modify a file in place. A tool that builds a new encrypted PDF from scratch does not run into any of them.
The PDF Password Protector here does that, in your browser — which also means neither the document nor the password you type is uploaded anywhere. For a file you are encrypting precisely because it is confidential, that is the right property to have.
If the document is already protected and you need to change the password, remove the old one first with the PDF Password Remover.
Frequently Asked Questions
What does the bad parameter error actually mean?
It is Acrobat reporting that it cannot write the file you asked for, not that your password is wrong. The most common cause by far is that the document is already digitally signed, because a signed PDF cannot be re-encrypted without invalidating the signature. The second most common cause is a structural problem inside the file itself.
Why does signing the document first cause this?
A digital signature covers the whole file. Encrypting it would change those bytes and break the signature, so Acrobat refuses rather than producing a document whose signature no longer validates. The fix is order of operations: apply the password first, then sign.
How do I encrypt a PDF that keeps throwing this error?
Produce a clean copy and encrypt that. Open the PDF and print it to PDF, which writes a fresh file with none of the original structural problems and no signature, then apply the password to the new copy. You lose any existing signature, which was already unusable in this situation.
Does printing to PDF lose anything?
Yes, and it is worth knowing what. Bookmarks, tags, form fields and any existing signatures are flattened away. The visible pages are preserved. If you need form fields kept, fix the source document instead of reprinting it.
Is there a way to avoid Acrobat entirely?
Yes. Any tool that writes a new encrypted PDF rather than modifying the existing one sidesteps the whole problem, because it is not trying to patch a file it cannot parse cleanly. The PDF Password Protector on this site works that way and runs in your browser.