Inspect, edit, sanitize, and verify PDF metadata — privately in your browser. The original PDF remains untouched on your device.
Reading binary dictionary and XMP descriptors locally in memory...
or browse files from your device (Max 100 MB)
Prepare metadata for court and legal exchange. Strips individual author identity and software stamps while maintaining title context.
Removes author names, keywords, and software signatures for strict double-blind academic peer submissions.
Removes all standard document metadata, clears timestamps, and strips standard catalog XMP metadata packets.
| Field | Before (Original Value) | After (Resulting Value) | Action |
|---|
Note: This verification validates standard PDF dictionary properties. Deep structures such as hidden incremental streams or raw non-standard tags may require specialized binary flattening.
Standard metadata is only one category of information inside a PDF. Below is an audit of deeper structural objects present in this document.
This action will mark all supported standard metadata fields (Title, Author, Subject, Keywords, Creator, Producer, and Timestamps) for complete deletion upon download.
The original file will remain completely untouched.
Every time you export a PDF from software like Microsoft Word, Adobe InDesign, Google Docs, or macOS Preview, the application automatically embeds invisible metadata tags into the document binary. While invisible during normal reading, these properties can inadvertently expose personal identifying details, corporate workflows, software versions, and sensitive internal paths.
Standard document properties reside in the PDF's /Info dictionary. These standard keys include Title, Author, Subject, Keywords, Creator (origin software), Producer (PDF generation engine), and precise timestamps.
Beyond standard properties, modern PDFs often carry Extensible Metadata Platform (XMP) XML streams, document identifier hashes (/ID), annotation histories, comment logs, and embedded thumbnails.
Sharing uninspected PDFs in legal discovery, blind academic peer reviews, investigative journalism, or competitive business bids can reveal draft revisions, personal usernames, and internal server paths.
| Field Name | What It Contains | Potential Privacy Concern | Can Standard Sanitization Remove It? |
|---|---|---|---|
| Author | User account name, full name, or workstation identity of the writer. | Exposes author identity, real names, or internal staff aliases. | Yes — 100% Client-Side |
| Title | Internal file title or template name defined in software. | May contain project code names or obsolete internal identifiers. | Yes — Editable / Removable |
| Subject | Description or subject categorization of the file. | Could indicate confidential department tags or case numbers. | Yes — Editable / Removable |
| Keywords | Comma-separated indexing terms assigned during authoring. | Can reveal sensitive classification labels (e.g., "confidential", "draft"). | Yes — Editable / Removable |
| Creator | The originating application (e.g., "Microsoft Word for Mac 16.7"). | Reveals software licenses, operating systems, and versions. | Yes — Removable |
| Producer | The PDF generation engine (e.g., "macOS Quartz PDFContext"). | Exposes toolchains, rendering engines, and print drivers used. | Yes — Removable |
| Creation Date | Exact timestamp including time zone of document origin. | Reveals exact working hours, geographic time zones, and project age. | Yes — Removable |
| Modification Date | Timestamp of last modification or resave operation. | Indicates last-minute revisions and internal editing timeline. | Yes — Removable |
Our engine operates entirely within your browser's JavaScript runtime using WebAssembly and typed binary arrays. Your original file is loaded into local memory, parsed into standard PDF document objects, modified according to your specifications, and re-serialized into a clean, new PDF file.