Workflow page

Merge then protect

Combine several PDFs into one document, then add an open password and permission settings to the finished file before sharing it.

Why the password goes on last

Encryption should be the final thing you do to a document. Once a PDF has an open password, most tools, including a merge step, cannot read its pages until the password is removed. If you protect each file separately and then try to combine them, you end up unlocking everything again. Merging first gives you one finished file, and protecting it once means one password to manage instead of several.

It also keeps your editing options open. While the packet is unprotected you can still reorder pages, add page numbers, or compress it. After protection, treat the file as sealed.

How to do it

  1. Gather the documents, for example a contract, its schedules, and a signed cover page.
  2. Upload them to Merge PDF (up to 20 files, 100 MB total) and pick a Sort files option. Keep uploaded order works if you added them in sequence.
  3. Optionally tick Generate table of contents for longer packets.
  4. Download and review the merged PDF. Make any final changes now: numbering with Add Page Numbers, or size reduction with Compress PDF.
  5. Upload the final file to Protect PDF.
  6. Enter an Open password. This is what the recipient needs to open the document.
  7. Optionally set an Owner password and choose restrictions such as Disable printing, Disable copying text and content, or Disable document editing.
  8. Keep Encryption strength at the default 256-bit unless the recipient’s software cannot handle it.
  9. Download the protected copy and test it by opening it with the password.

An example

Picture a finance lead sending a quarterly pack to an external auditor: a balance sheet, a cash-flow statement, and a set of bank confirmations. She merges the three PDFs with Sort by file name, adds page numbers so questions can reference a page, and then protects the merged file with an Open password and Disable document editing. The password goes to the auditor by phone; the PDF goes by email.

What the permission settings really do

The open password is enforced by encryption: without it, the file cannot be read. Owner-password restrictions such as no printing or no copying are different. They are honored by the reading software rather than enforced by the encryption itself, so they discourage casual misuse rather than guarantee it (qpdf manual on encryption). If the content truly must not be copied, do not rely on permissions alone. Our guide on passwords vs permissions covers this in more detail.

Common mistakes

  • Protecting before the packet is final. If you spot a typo afterwards, you need Unlock PDF and the password, then the fix, then protection again.
  • Sending the password in the same email. Share it through a separate channel.
  • Forgetting the password. There is no recovery option. Keep your unprotected master in a safe place internally.
  • Picking 40-bit to be safe with old readers. Choose it only when you know you must; 256-bit is the modern default, and PDF 2.0 encourages AES-256 (Library of Congress).

When to choose another route

If the recipient uses a secure file-sharing system with its own access controls, a password may add friction without much benefit. For background, read secure a PDF before sharing and password protect a PDF.

Trust center

Trust pages

How We Want PDF handles your files: privacy, security, and how long uploads are kept.

privacy

Privacy

How We Want PDF handles the files you upload, what is needed to use the tools, and which tools send content to an AI provider.

Read page
security

Security

How We Want PDF checks uploads, delivers results, limits abuse, and removes queued job files.

Read page
retention

File retention

How long We Want PDF keeps uploaded files and results, and when they are removed.

Read page