Passwords and permissions: why courts reject locked PDFs
← All guides
A locked PDF fails e-filing at every layer that touches it. The rule sources agree:
- PDF/A prohibits encryption — the standard's own terms; a certified PDF/A file must be openable "by anyone or any software that processes the file", per Florida's portal FAQ.
- CM/ECF rejects encrypted or password-protected documents — on the Ninth Circuit's published list of content the system bounces.
- Tyler-based portals list password protection among the leading causes of the automated Court Response of Failure rejection.
Two locks, both must go
| Lock | What it does | Court impact |
|---|
| User password (open password) | Required to open the file at all | The clerk's system cannot open it — rejection |
| Owner password (permissions) | Restricts printing, copying, editing — the file opens fine | Also rejected: permission-locked files cannot be processed, and "no copying" is incompatible with a searchable public record |
Filers routinely clear the open password and forget the permissions — check both in the document's security properties before refiling.
Removing security, free
- Re-export from the source. If you have the Word (or other) original, export a fresh PDF with no security. This is the cleanest path — it also refreshes fonts and metadata.
- Print to PDF from an unlocked copy. If the file opens without a password (permissions-only lock), printing it to a new PDF produces an unencrypted, permission-free copy. Verify text stayed searchable — print pipelines rasterize sometimes.
- LibreOffice / free PDF tools. Open the unlocked file and re-export without security settings.
- If you cannot open it at all, you need the password from the author — that is the legitimate path. Circumventing protection on documents you don't control is a legal question, not a technical one.
After removal: re-verify everything
Security removal is an edit, and edits break things: re-export can swap fonts (check embedded again — see Florida's font trap), print-to-PDF can rasterize searchable text (Ctrl+F test), and a PDF/A re-export after decryption must be re-validated because the previous conformance report described a different file. Run the file back through the checker — encryption/permissions are among the checks — before refiling.
Security ≠ redaction
Don't confuse locks with redaction: applying a password does not hide text, and a black box over text (or white text) leaves it copyable — the Ninth Circuit's guide warns exactly this. Redaction is content removal, applied and flattened; security settings are metadata. A "secured" file with recoverable "redacted" text is the worst of both: rejected for mechanics and potentially disclosing privileged content.
Pre-flight: no open password · no permission restrictions · no encryption · and after any removal, fonts + searchable text + PDF/A status re-verified.
The checker on this site covers encryption, permissions and the re-checks in one pass.