Protect a PDF Before You Send It to a Client

A polite “please don’t forward” in the email body doesn’t stop anyone. If the file is sensitive — contracts, offers, ID packets — lock it before it leaves your outbox.

Order of operations

1. Assemble with /tool/merge-pdf if you have multiple files.

2. Clean blanks or order with /tool/edit-pdf-pages.

3. Shrink with /tool/compress-pdf if size is a problem.

4. Optional visible stamp via /tool/pdf-text-watermark (DRAFT / CONFIDENTIAL).

5. Lock with /tool/protect-pdf.

Follow the same sequence on /protect-pdf-before-sharing when you want the guided workflow.

Passwords

Use a unique password from a manager. Send the PDF and the password on different channels (email + chat). Keep an unlocked master offline. Never put the password in the same message as the attachment.

Unlocking your own file

If you locked something you own and need to edit again, /tool/unlock-pdf removes the password. Don’t unlock documents you aren’t authorized to open.

Watermark vs password

Watermarks deter casual screenshots and “oops” forwards. Passwords control who can open the file. Use both when the stakes are high.

What to check before you hit send

Open the locked file on a second device and confirm it actually asks for the password. A common miss is protecting a draft, then attaching the unlocked master that was still sitting in Downloads. Read the first and last page so a blank sheet or the wrong exhibit did not survive the merge. If the client will print the packet, a heavy watermark can make body text hard to read — use a lighter stamp or skip it and rely on the password. Tell the recipient which file name to expect so a forwarded copy is easier to spot. Store the password in your manager next to the project, not in the PDF’s filename.