Ensure 100% legal compliance. Securely remove author identities, creation software, draft paths, and XML metadata streams locally on your device.
Built for confidential workflows — files stay in your browser memory.
Saving “as PDF” often retains Info dictionary fields (/Author, /Creator, /Producer, dates) plus Adobe XMP packets that store edit history, software versions, and sometimes filesystem hints. Cloud “cleaners” require uploading the very contracts you wanted to anonymize. GoLocalPDF opens the PDF in-browser with pdf-lib, clears standard Info fields, targets nested XMP metadata streams, and rewrites a clean binary—without sending the file to our servers. Visible page content stays intact; only hidden property trails are purged.
Law firms scrub opposing-counsel packets before production. HR removes author trails from offer letters and RIF docs. Security teams sanitize PDFs leaving the corporate boundary. Journalists and whistleblowers strip creator fingerprints before publication. Procurement shares vendor RFPs without leaking internal usernames baked into document properties.
Load contracts, filings, or internal memos into the local sanitizer dropzone.
The client parser clears Info dictionary fields and nested XMP XML objects in memory.
Export a cleaned PDF ready for external sharing or e-filing.
| Feature Metric | Traditional Cloud Services | GoLocalPDF Sandbox |
|---|---|---|
| XMP / XML depth | ❌ Often clears visible Properties UI only | ✅ Scrubs Info tags and nested XMP metadata streams |
| Upload risk | ❌ File must reach a third-party cleaner | 🛡️ Entire wipe runs in browser RAM |
| Content safety | ❌ Some tools re-render/rasterize pages | ✅ Targets metadata catalogs; page visuals unchanged |
| Audit readiness | ❌ Soft “clear” that recovery tools reverse | ✅ Rewrites dictionaries into a fresh saved binary |
Typical Info fields such as author, title, subject, keywords, creator, producer, and creation/modification dates, plus embedded XMP XML streams that carry deeper history.
No. The sanitizer focuses on document information dictionaries and XMP—not body text, images, or page geometry.
Yes for confidentiality: the PDF never leaves your device during local scrubbing, so the cleaner cannot retain a copy.
No. Property inspection and purge run in the browser as a free Acrobat alternative for this specific metadata task.
Stripping metadata can invalidate digital signatures or strict PDF/A profiles. Re-validate compliance after cleaning if your workflow depends on those features.
