Password Protect a PDF

When to use Protect PDF

Use this before emailing or sharing a document that contains sensitive information — financial statements, contracts, medical records — so it can't be opened without the password. Share the password through a separate channel from the file itself.

How to Password-Protect a PDF

1. Select a PDF.
2. Enter and confirm a password.
3. Ensure the password is nonempty and the confirmation matches; the warning alone does not block export.
4. Export, then reopen the downloaded file and confirm it requires the intended password.

What this tool changes

• Encrypts the document so a password is required to open it.

What it preserves

• Page content is copied, but the active export rebuilds document structure and does not reliably preserve metadata, bookmarks, or certificate signatures.

Good to know

• PDF Editing Tools does not store your password. If you forget it, the password cannot be recovered.
• Known limitation: an empty password exports an unprotected copy, and a mismatching confirmation does not block export. Nonempty passwords need at least four characters.
• Password protection restricts opening the file; it is not equivalent to enterprise DRM.

A lock and a request are different things

A PDF can carry two kinds of password. The user password is required to open the document at all — the contents are genuinely encrypted and there is nothing to read without it. The owner password does not stop the document opening; it marks actions like printing or copying as restricted.

That second kind is enforced by convention, not cryptography. A viewer that honours the flags greys out the print button; a viewer that ignores them simply does not. Permissions are a request, and encryption is a lock.

This tool sets a real user password, so opening requires it. Alongside that it marks the document as not-to-be-modified and not-to-be-reassembled while leaving printing and text copying available — sensible defaults for a document you are sending someone to read.

Choosing a password, and there is no recovery

Length beats complexity. Four or five unrelated words are both stronger and easier to communicate than a short string with symbol substitutions, and since you have to pass this password to your recipient anyway, memorability matters less than you would think.

Make it unique to this document, and not derived from it — the client name, the invoice number, and the date are the first three things anyone would try.

Because nothing about your password leaves your device, there is no record anywhere to reset. No support process can recover it, here or in any tool that encrypts properly. Write it down before you close the tab, and send it to your recipient through a different channel than the file — a password in the same email thread as the attachment protects nothing.

Encrypt last, and know what it does not cover

Every other operation needs the document decrypted, so a file you encrypt first has to be unlocked again before it can be merged, split, cropped, or numbered. Assemble the document completely, check it, and encrypt as the final step before sending. If what you are holding is already encrypted and still needs work, remove a password you already know first, then protect the finished version again.

Encryption controls access to the file and has no reach past the moment your recipient opens it. It does not stop redistribution, does not meaningfully prevent copying, is not rights management, and does not prove who sent the document or that it is unaltered — that is what a signature is for.

It also does not hide the filename. 2026-redundancy-list.pdf has told the story before anyone types a password. And nothing about a password survives onto a printout or a screenshot, which is the case for also choosing to mark the document as confidential on the pages themselves — a label rather than a control, but one that travels with the content.

What encryption costs, measured

The historical 1,084-byte increase was measured with an isolated protection helper on one scan. The current UI also assembles pages before encryption, so do not infer metadata preservation or a fixed overhead from that measurement.

That is worth stating plainly because the expectation runs both ways. People sometimes avoid protecting large files in case it makes them larger, and sometimes hope protecting one will shrink it. Neither happens. If you need a smaller file, that is a separate job — compressing it or removing pages are the operations that move the number.

For certificate signatures, use a compatible encryption-and-signing workflow before the final signature and validate it afterwards. Do not pass a digitally signed original through this rebuilding export merely to add a password.