When this tool is useful
Reducing exposed title, author, subject, keyword, creator, producer, and date fields before routine document sharing.
How local processing works
The browser loads the PDF, removes its standard document-information dictionary, and saves a new copy while keeping the page objects.
How to use it
- Choose the source files.
- Review the available settings and page order.
- Process locally, inspect the result, and download it.
Important limitations
Embedded XMP is not changed, and this does not guarantee removal of visible page content, comments, attachments, form values, hidden layers, revision remnants, or metadata inside embedded objects. Inspect sensitive files with a dedicated sanitization process.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
Does this tool upload my files?
No. Processing happens in your browser; closing the page clears the working session.
Will the output always match the source exactly?
Embedded XMP is not changed, and this does not guarantee removal of visible page content, comments, attachments, form values, hidden layers, revision remnants, or metadata inside embedded objects. Inspect sensitive files with a dedicated sanitization process.
Concrete input and output example
Input a 14-page report whose document properties show an author, title, keywords, producer, and dates. Download the rewritten PDF, reopen its properties, and remember that page content and embedded objects need separate inspection.
Browser compatibility notes
Reviewed against the implementation and required web APIs on 2026-08-12. Use a current browser where these APIs are available and verify important output on your device.
- Chrome / Edge (current desktop)
- Requires local PDF parsing, worker/canvas APIs where applicable, document creation, and Blob download.
- Firefox (current desktop)
- Uses the local PDF workflow; always verify the generated download in its destination viewer.
- Safari (current desktop)
- Uses the same local workflow; large page sets can have a lower practical memory ceiling.
A tool-specific question
Does this make a PDF safe for confidential release?
Not by itself. It clears supported document-level fields but does not guarantee removal of visible content, revisions, attachments, comments, or metadata in embedded objects.