Checklist: Share a PDF Securely
Ten checks before you send a PDF: the right file, extra pages, metadata, watermarks, passwords, and the channel you use.
3 min readQuickPDFKit
The attachment is the wrong version, the file still lists an internal project in its document info, or the password travels in the same email as the file. This is the short list of what to do before you hit send. Work on a copy and keep the original until that copy is the one you meant to send. These steps run in the browser, so the PDF is not uploaded to QuickPDFKit.
The file itself
- Confirm it is the right file. Open it. Check the title page, the date, and the last page. The filename is not proof. A name like Draft_final_v7.pdf has been the wrong file often enough to deserve the extra look.
- Remove pages the recipient should not see. Split out the pages that belong in this share. If a paragraph is confidential, delete it in the source and export again. Covering text with a white box is not removal. A later reader can still select or uncover it.
- Read headers, footers, and the file name. An excerpt can still name a client you did not intend to disclose. Rename the download to something that is accurate and not more revealing than the document.
- Decide whether document info matters. PDFs often store an author, a title, and the app that created them. That can reveal a staff name or an internal project. Edit PDF metadata changes the title, author, subject, and keywords locally. Hyper Compress PDF can clear title, author, subject, keywords, producer, and creator when a plainer copy is acceptable. Clear those fields on the copy you send. Keep your own original. What actually gets smaller is covered in the compression guide.
Marks, passwords, and signatures
- Mark drafts visibly. A watermark such as DRAFT, or the recipient's name, makes a forwarded file easier to recognize. Add a watermark can place text or an image across the pages. It does not stop copying or a screenshot. It makes an accidental forward obvious. Watermark the copy, not the archive original, unless the archive should carry the mark too.
- Add a password only when it helps. A password stops a casual forward from opening. Protect PDF applies that password in the browser. Use at least 6 characters, and use a password you have not used elsewhere. This is basic protection for ordinary sharing, not a substitute for a managed encryption system. A PDF permission flag is a weak barrier.
- Send the password by a different channel than the file. The file by email, the password by a call or a separate message. A password in the same email is not a control. Store the password yourself. If you lose it, the browser tool cannot recover the file. Keep an unprotected copy in a place only you can open.
- Sign when the visible signature is what the packet needs, and only after the text has stopped changing. Sign PDF places a signature image on the page. It is not a certificate-backed digital signature, and it will not prove later that the file was unchanged. For an agreement that needs that kind of signature, use a signing service that issues a certificate. Do not merge, split, or convert a file after you have signed the version people will keep.
The way it leaves
- Choose the channel for the contents. Email is fine for ordinary business files. For anything you would not want in a forwarded thread, use a share the recipient must sign in to open, and set it to expire. A public link with no password is a publication.
- Send the smallest correct copy. Compress only if the rewrite actually shrinks the file and the pages still match. If it does not shrink, send the original or a split excerpt. Do not attach both a compressed and an uncompressed version unless you mean to give the recipient a choice.
- After it leaves, tidy up. Remove the export from Downloads on a shared machine. If you sent the wrong file, say so in the same thread and send the correction. Asking someone to ignore the last attachment, without a replacement, leaves the wrong file as the one they will open.
If you only do three things, open the file, remove the pages that do not belong, and send any password by a second channel. The rest of the list is how you avoid the quieter mistakes: metadata, a draft that looks final, and a signature image that people will treat as more than it is. How QuickPDFKit handles pages and files is also described in the privacy policy.
Tools for this guide
- Protect PDF
Add a password in the browser for ordinary sharing. Keep an unprotected copy you can still open.
- Add a watermark
Mark a copy as a draft or with the recipient's name so a forward is obvious.
- Edit PDF metadata
Review or change the title, author, subject, and keywords before the file goes out.
- Sign PDF
Place a signature image on the page. This is not a certificate-backed digital signature.