Contracts and invoices name the author
The author field is whatever the exporting application wrote: an employee name, a client name, a template author. Invoices sent to customers routinely carry the internal account that generated them.
A PDF usually names the person who wrote it, the application that produced it — with a version — and often the original Word or InDesign document it was exported from. It can also carry an XMP block with a full editing trail. This tool empties both without touching page content, and it refuses outright to edit a PDF that is digitally signed, because that would invalidate the signature.
Engine
File API
Runs in
Web Worker
Needs account
No
Two places hold this data: the document information dictionary (the classic fields below) and an XMP metadata stream, which is an XML document that can hold far more.
The author field is whatever the exporting application wrote: an employee name, a client name, a template author. Invoices sent to customers routinely carry the internal account that generated them.
“Adobe PDF Library 15.0”, “Microsoft Word 2016”, “Skia/PDF m121” — each tells a reader which app and roughly which era the file came from, and sometimes which operating system. Combined with timestamps it narrows down a specific machine.
Many editors write an XMP packet alongside the classic fields: the source document, the export settings, the app that saved it last, occasionally the AI tool that generated an image placed inside. Emptying the information dictionary alone leaves that stream behind.
A signature covers the file as it was at signing time. Removing metadata changes the bytes, so the signature stops validating — and a contract that opens with “signature invalid” is worse than one with an author name in it. This tool refuses instead of quietly breaking it.
Drop a PDF into the panel. It is parsed in a Web Worker on your device.
Check the report. A signed file is flagged here and cannot be cleaned.
Download the cleaned copy and open it once to confirm the pages still render as expected.
Before you rely on it
A PDF is a graph of objects joined by a cross-reference table. Deleting a metadata object in place means rewriting offsets and risking a file that opens in one viewer and fails in another. This tool parses the document, empties the two metadata carriers and writes a new file, so the result is a valid PDF that any viewer accepts — at the cost of a new byte layout.
It should. Only the information dictionary and the XMP stream are emptied; pages, fonts, images and the outline are copied as they were. As with any file editor, keep the original until you have opened the cleaned copy once.
Because a signature is a hash of the whole file. Any change — including removing an author name — invalidates it. Silently producing a file whose signature no longer verifies would be worse than saying no.
No. Page content is untouched, including scanned images and their own embedded EXIF. This tool only handles the document-level metadata.
Most editors rewrite document properties when they save. Clean the file last, or clean it again after the final export — the same is true for Office documents.
No. Parsing and rebuilding happen in a Web Worker in your browser. There is no upload endpoint; the network panel will show no request carrying the file.