PDF Metadata Remover — Clean PDF Properties Online

The information a PDF carries about you, quietly

When a PDF is created — exported from a word processor, saved out of a design app, printed to PDF, or run through a converter — the software writes a set of hidden properties into the file alongside the pages you can see. These typically include a title, an author, a subject, a keyword list, and two “software” fields: the creator (the application the content was written in) and the producer (the library or driver that generated the actual PDF). Add to that the creation and modification timestamps, a document-language tag, and a unique document identifier, and a single file can quietly state who made it, on what software, and when.

None of that appears on the page. It surfaces in your operating system’s file-properties panel, in a PDF reader’s document-info dialog, and to anyone who opens the file with a tool built to read structure. Most of the time you never set any of it deliberately — it is filled in automatically — which is exactly why it is worth clearing before a file goes somewhere public. A resume can announce the template you started from and your login name. A contract can name the internal drafting tool and the exact time it was last touched. This tool exists to wipe all of that in a single pass so the file you share says only what its pages say.

Before it removes anything, the tool reads the file and shows you the properties it found, so you are looking at the truth of what the document actually contains rather than guessing. Nothing is written until you click to clean it.

What “remove metadata” clears, precisely

This is a one-pass tool, not a form. It does not ask which fields to keep — it removes them all, which is the right default when the goal is a clean file for release. Concretely, it deletes the nine standard entries in the document-information dictionary: title, author, subject, keywords, creator, producer, the creation date, modification date, and the trapped flag. It then removes the entire information dictionary from the file, not just its contents, so nothing is left behind that hints a field once existed.

Beyond those visible-in-properties fields, it clears two things most people never see. The first is the XMP metadata stream — a block of XML that many modern applications embed in addition to the old fields, holding its own copy of the title, author, and more. The second is the document identifier in the file trailer. It also drops the document-language tag. Removing the XMP stream matters because of a trap covered in the next section; removing the ID matters because that identifier is what lets a file be traced back to its original even after you change everything else.

After the properties are gone, the tool rebuilds the PDF and hands it back. Because it rewrites the file structure rather than re-rendering the pages, the document that comes out is the same document that went in with only its hidden data missing — and, as often as not, a little smaller, since the removed entries and any now-unreferenced objects are dropped from the rebuilt file.

The second copy: why the XMP stream has to go too

Here is the detail that trips up a lot of metadata tools. A PDF can store the same information in two places at once. The original mechanism is the small document-information dictionary — the title/author/etc. fields described above. Layered on top, many applications also write an XMP packet: an embedded block of XML carrying its own copy of the title, author, and more, in a richer format.

The problem is that the two copies can disagree. A tool that clears only the old dictionary and leaves the XMP packet alone will produce a file that looks clean in one viewer and still shows the old author and title in another — because several viewers prefer the XMP data when it is present. You would think the metadata was gone while a stale copy quietly rode along. To avoid that, this tool removes the XMP stream as part of the same pass, so there is no second copy left to leak. When the source file had no XMP stream to begin with, the confirmation message says so plainly rather than claiming a cleanup that did not happen.

What this tool does not do — and why that matters

It is worth being blunt about the limits, because the wrong assumption here is a genuine privacy risk. Removing metadata cleans the hidden properties of a file. It does absolutely nothing to the visible content on the pages. If a name, an address, a salary figure, or a signature is printed in the document, it is still printed there after you run this tool. Metadata removal is not redaction, and it is not a substitute for it. If you need to obscure something you can see on the page, that has to be done by redacting the page content before cleaning the metadata — not by this step.

The second limit is scope within the file’s hidden data. This tool targets the standard, well-defined places metadata lives: the information dictionary, the XMP stream, the document ID, and the language tag. That covers the overwhelming majority of what identifies an ordinary PDF. It does not go hunting through every corner where a determined author could have stashed custom data — inside page-content streams, file attachments, form fields, annotations, or embedded scripts. Those are uncommon in everyday documents, but if your situation calls for a guaranteed-clean file, treat this tool as the fast first pass and follow it with a manual review rather than assuming it caught everything. Being honest about that boundary is more useful than a promise it cannot keep.

When you would reach for this

The clearest case is double-blind review. Academic and grant submissions often require that a manuscript carry no trace of its authors, and reviewers can and do check the document properties — an author field left in place has unmasked plenty of “anonymous” submissions. Stripping the metadata before you upload removes that failure mode entirely.

The next is anything you send outside your organisation: a resume going to a hiring portal, a contract or proposal going to a client, an invoice, a report, a public download. In each case the metadata tends to carry details that are none of the recipient’s business — the login name of whoever exported it, the internal template it began as, the exact software and version in use, the precise time of the last edit. Clearing it is simply good hygiene before a file leaves your control. It is also a sensible habit before publishing any PDF on the open web, where the properties are one more thing a curious reader can inspect.

Why the work stays on your machine

Everything runs in your browser. The PDF is read into memory, its metadata is stripped, the file is rebuilt, and the cleaned version is offered straight back as a download — no byte is sent to a ToolMintX server. For a privacy tool that locality is not a nicety, it is the entire point. The information you are here to remove — your name, your organisation, the software you use, the dates you worked — is precisely the kind of personal detail you would not want to hand to a third-party server just to have it stripped out. A cleaner that uploads your file first would be creating the exact exposure it claims to prevent. Doing the work locally means the cleanup never leaks the thing it was meant to remove.

Because the tool reads and writes the PDF structure directly rather than re-rendering the pages, selectable text stays selectable and image quality is untouched. You are getting the same document back, minus its hidden history.

Remove everything, or edit field by field?

This tool is the blunt instrument: one click and the metadata is gone. That is what you want when the aim is a clean-slate file for release and you do not care to keep any of the properties. But sometimes you want the opposite — to seta proper title so it shows as the heading in search results and readers’ tabs, correct an author, or remove only the software fingerprint while keeping a useful subject line. For that, reach for the PDF metadata editor, which reads the current values, lets you change any field, and removes only the ones you clear. Same underlying respect for the file — a different level of control.

Related tools

If a PDF is locked and its properties can’t be read, remove the password first with Unlock PDF, then clean the unlocked copy. To keep some properties and rewrite others, the PDF metadata editor is the precise counterpart to this one. And when you are assembling several files for release, the Merge PDF tool combines them — worth knowing that a freshly merged document starts with clean, blank properties, so cleaning the parts first keeps the whole clean too.