How to sanitize a PDF before sharing
A clean-looking page is only one part of a safe release copy. Define which content and document features may leave your device before choosing a sanitization method.
Inventory the file
Inspect the visible pages, document properties, annotations, forms and attachments. Note whether searchability or accessibility must survive. Keep a restricted original so you can choose a different export if image reconstruction removes functionality the recipient needs.
Choose a scope for removal
For supported identifier redaction, CloakDoc’s batch workflow creates a fresh page-image PDF. It does not carry over the source text layer or original annotation and attachment objects. A comment or mark visible in the rendered page can still appear in the output image.
Set metadata deliberately
Keep Strip Metadata selected when source title, author and subject should not be copied by the batch export. The output still contains information needed to be a PDF and identifies CloakDoc as its creator and producer. Do not describe it as a file with no metadata.
Review what reconstruction does not solve
The original filename may identify a person. Unmatched visible information, embedded screenshots and handwritten notes can still be present. Sanitizing one file does not remove the source from a shared folder or an earlier email attachment.
Validate and release
- Open the saved output in a separate reader.
- Inspect every page and confirm expected page count and orientation.
- Check properties, attachments and selectable text.
- Review the filename and the files included in the outgoing message.
- Record the reviewer’s decision and handle retained copies according to your policy.
The manual overlay export and ordinary PDF merge or conversion utilities are different save paths. Do not assume they provide the same sanitization as the batch reconstruction workflow.