When this tool is useful
Creating an unencrypted working copy of a PDF you are authorized to access and modify.
How local processing works
The PDF is authenticated, protection is removed, then the output is reloaded to verify encryption is gone and page count is unchanged.
How to use it
- Choose the source files.
- Review the available settings and page order.
- Process locally, inspect the result, and download it.
Important limitations
A user password may open a PDF without permission to remove protection. In that case the owner password is required; this tool does not bypass passwords.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
Does this tool upload my files?
No. Processing happens in your browser; closing the page clears the working session.
Will the output always match the source exactly?
A user password may open a PDF without permission to remove protection. In that case the owner password is required; this tool does not bypass passwords.
Concrete input and output example
Input an AES-protected PDF and its valid password. The output is an unprotected PDF that retains the document’s page structure rather than page screenshots; keep it secured because access restrictions are removed.
Browser compatibility notes
Reviewed against the implementation and required web APIs on 2026-08-12. Use a current browser where these APIs are available and verify important output on your device.
- Chrome / Edge (current desktop)
- Requires local @libpdf/core parsing, encryption APIs, and Blob download support.
- Firefox (current desktop)
- Password bytes remain in the local workflow; verify the protected or unlocked download.
- Safari (current desktop)
- Uses the local encryption workflow; keep the tab active during larger rewrites.
A tool-specific question
Does unlock turn pages into images?
No. With a valid password, the local PDF workflow removes protection while retaining document page structure rather than rasterizing pages.