Password protect or unlock PDF made simpler, in your browser

Select the document, choose Add an opening password, and enter the new password twice. The two entries must match exactly. Use at least 12 characters; the maximum is 127 bytes when encoded as UTF-8, so some multilingual passwords reach the byte limit sooner than an ASCII phrase of the same character count. Process the file and download the protected copy. Open that download in a PDF reader and confirm that it asks for the password before displaying the contents.

An opening password suits a document that should only be read by people who know the password. Examples include a private report, a completed application, or personal records you need to store or share. The tool uses AES-256 PDF encryption and writes a separate file. Keep a usable original until you have checked the result and recorded the password somewhere appropriate. The site cannot retrieve a forgotten password because it does not receive or keep your password.

Choose Remove a known password, select the protected file, and enter its existing password. The tool uses that password to read the document and saves a working copy without standard password protection. Download it, close the reader, and reopen the saved copy without entering a password. This is useful when you repeatedly use your own statement, need to fill a compatible form, or must pass a document to another tool that requires unencrypted input.

The unlocked copy contains readable document data, so its storage and sharing conditions change. Give it a distinct filename and put it where you intend to keep working. Retain the protected source if you still need an encrypted archive copy. This tool requires you to supply the known password even for removal workflows. It does not search possible passwords, recover forgotten secrets, or remove a certificate-based encryption scheme. A failed password check produces no downloadable partial result.

Yes. Select Add an opening password, enter the current password in the existing-password field, and enter the replacement password twice. The current password allows the tool to read the source before it applies the new protection. For an unprotected PDF, leave the existing-password field empty. Confirm the replacement by opening the downloaded file with the new password. The previous source file remains a separate copy with its previous protection, so rename your files clearly to avoid confusing the two versions.

Changing a password does not withdraw earlier copies from other people or devices. Someone who already has an unlocked copy can still read that copy. Consider the whole document-sharing process when deciding which version to send and where to store it. Send the final protected file through your intended channel, and communicate its password separately when practical. For recurring team workflows, agree how recipients will identify the latest version before creating several similarly named protected files.

An opening password controls access to encrypted contents. A permissions or owner password is associated with restrictions such as printing, copying, or editing in readers that honor those settings. This tool adds an opening password and leaves normal document operations available after the recipient opens the file. It does not expose printing or copying restriction controls. That keeps the result appropriate for recipients who need to read, complete, print, or reuse the document once they have been given access.

Password encryption should not be described as preventing every later screenshot, printout, or change. Once someone can read the document, they can use what they can see. If your source has standard permission restrictions, removing protection creates an unrestricted working copy when the supplied password is accepted. Use that workflow for documents you are entitled to modify. Specialized rights-management files, certificate encryption, and documents requiring an external authorization service fall outside this tool's supported scope.

A longer, unpredictable password is preferable to a short name, date, document number, or phrase closely associated with the file. A password manager can generate and store a unique value, or you can choose a sufficiently long phrase whose words are not an obvious quotation. The 12-character minimum is an input rule, not a guarantee that every accepted password is difficult to guess. Do not reuse a password that protects an unrelated account, since document recipients need to know this one.

Spaces and multilingual characters count as part of the password and are not trimmed away. The confirmation field helps catch accidental differences. Null characters and line breaks are unsupported, and UTF-8 length must stay within the stated limit. If you enable Show passwords to inspect your entries, consider who can see your screen. The fields are hidden by default, and Clear files clears their contents. Reopening or refreshing the page also discards the application's in-memory document result.

The selected PDF is processed inside your browser using a local WebAssembly engine. The file bytes, password entries, and output are not sent to a processing server by this tool. Your browser still needs to load the site's page and engine assets. On a slow connection, that initial engine download can take time; later processing speed depends on your device and document complexity. A network problem while loading the engine produces an error and leaves you able to retry.

The working data remains in the current browser session while you use the page. Download the result to keep it, and use Clear files when you have finished. This local workflow does not make claims about the security of your device, browser extensions, downloaded-file backups, or other applications where you later open the PDF. Those are separate parts of your environment. The useful property here is that document processing does not require uploading your selected contents or secret to this site's server.

The engine rewrites PDF objects rather than printing every page to an image. Existing text, page geometry, images, bookmarks, links, and ordinary form objects are intended to remain part of the document. Check the saved copy in your own reader, particularly when forms contain important values or the file has unusual annotations. Signature fields, certified PDFs, and XFA forms are rejected. Rewriting a signed document could affect its signature validity, and this tool does not provide a signature-preserving workflow.

Check the selected file version and the exact password, including spaces, letter case, and copied characters. The file might use unsupported encryption, contain damage that another application repairs, or depend on a specialized reader. The tool does not silently accept warning-bearing engine output. Retry with the correct password or obtain a clean, unsigned source from the document owner. Avoid repeatedly changing unrelated settings when the source itself is the issue. Your original file is not overwritten by a failed attempt.

For protection, reopen the download and confirm both the password prompt and the readable contents after entry. For removal, reopen without a password. Review page order, Chinese text, links, bookmark navigation, and any form fields you rely on. AES-256 requires a reader compatible with modern PDF encryption; very old applications may need upgrading. Inputs are limited to 30 MB and 100 pages, with a 120 MB output ceiling. Finish other document edits before adding the final password so you can verify the exact version recipients will receive.

Choose a tool for the next step and review each output.

• Fill an unlocked form
• Add chapter navigation before protecting