Frequently Asked Questions: Remove PDF Metadata

Cleaning a PDF's hidden metadata with BlendPDF is a transparent, three-step process — and unusually for an online tool, you get to see exactly what is being removed before and after it happens.

Select Your PDF
Click "Select PDF" or drag and drop your file onto the upload area; you can also pick a file from Google Drive. Files up to 50MB are accepted. The moment the file is selected, BlendPDF reads its metadata locally in your browser — the document itself is never uploaded anywhere.

Review What Your PDF Reveals
A table appears listing every document-level metadata field: Title, Author, Subject, Keywords, Creator, Producer, Creation date, Modification date, and whether an XMP metadata stream is present. Fields that are set show their current values; empty fields are marked "Not set". Many people are surprised at this step — a personal name in the Author field, the exact software used, or a revealing modification timestamp are all common finds. A counter summarizes how many fields were found.

Remove and Verify
Click "Remove metadata". The tool clears the information fields, deletes the timestamps, and strips the XMP stream — then re-opens the cleaned file and reads the metadata back, updating the table into a before/after comparison. Each removed field shows its old value struck through and "Removed" in the after column, proving the file you're about to download really is clean.

Download the Clean PDF
Click "Download clean PDF" to save the cleaned copy, named with a "no-metadata-" prefix so you can't confuse it with the original. Your original file remains untouched, and the whole operation typically takes just a few seconds.

Almost every PDF carries information about itself that never appears on its pages. This metadata is written automatically by the software that created the file, and most people are unaware it exists — which is precisely what makes it a privacy concern.

The Document Information Fields
The classic PDF metadata lives in the document information dictionary: Title, Author, Subject, Keywords, Creator (the application the document was authored in, like Word or InDesign), and Producer (the software that generated the PDF itself). The Author field is the most sensitive — it is typically auto-filled with the account name or license name of whoever created the document, which often means a real personal name or an employer's name.

Timestamps
PDFs record a creation date and a modification date, down to the second and including a timezone. These can reveal more than you'd expect: that a "final" contract was edited five minutes before sending, that a report was written at 3 a.m., or that a document predates or postdates some event. The timestamps persist through emailing, uploading, and copying the file.

The XMP Metadata Stream
Beyond the basic fields, many PDFs embed an XMP (Extensible Metadata Platform) stream — a block of XML inside the file that repeats the same details and can add more, such as document IDs and editing history, depending on the creating application. Because it's a separate structure, XMP survives even when the basic fields are cleared, which is why a thorough cleaning must remove it too.

See It for Yourself
You don't have to take this on faith: drop any PDF into the BlendPDF Remove PDF Metadata tool and it will display every one of these fields and their current values, read locally in your browser. Checking a document you're about to share takes seconds and costs nothing.

The tool performs three distinct cleaning operations on your PDF, covering both the classic metadata fields and the modern XMP stream. Here is the precise list — no more, no less.

Document Information Fields Are Cleared
The six standard information fields — Title, Author, Subject, Keywords, Creator, and Producer — are all blanked. After cleaning, a PDF viewer's "Document Properties" dialog will show these fields empty. This is where personal names, company names, and software identifiers most commonly hide.

Timestamps Are Deleted
The creation date and modification date entries are removed from the document's information dictionary entirely. The cleaned file no longer discloses when it was made or last edited. (Your operating system will still show file-system dates for the downloaded file itself — those belong to your device, not to the PDF's internal data.)

The XMP Stream Is Stripped
The embedded XMP metadata stream is deleted from the document catalog. This matters because XMP duplicates the basic fields in XML form and can carry additional identifiers; tools that only blank the info dictionary leave this copy behind. BlendPDF removes the stream itself, and the before/after table explicitly shows "XMP metadata stream: Present → Removed" when one was found.

What Stays Untouched
The visible content of your pages — text, images, fonts, layout — is not modified in any way. Annotations, attachments, bookmarks, and form fields inside the document are also left as they are; this tool is scoped deliberately to document-level metadata. If sensitive information is visible on the pages themselves, that's a redaction task, not a metadata task.

No — and for this tool in particular, that's the whole point. The Remove PDF Metadata tool runs 100% in your browser. Your file never leaves your device: not for reading the metadata, not for removing it, and not for producing the cleaned copy.

The Irony In-Browser Processing Avoids
Think about what a server-based metadata remover asks of you: to protect your privacy, first send your private document across the internet to a stranger's server. You'd be trading known metadata exposure for unknown server-side exposure. BlendPDF's design removes that trade-off entirely — the document you are cleaning for privacy reasons never travels over the network at all.

How It Works Locally
When you select a file, your browser parses the PDF structure on your own device, reads the information dictionary and checks for an XMP stream, and displays what it finds. When you click "Remove metadata", the same local engine rewrites the file in memory and hands you the cleaned bytes as a download. BlendPDF's servers never see the file, its metadata, or its contents.

Nothing to Delete, Nothing to Trust
Server-based tools answer privacy questions with retention policies — "files are deleted within X hours." Those policies require trust. Here there is no server copy, so there is no retention window, no deletion schedule, and no operator access to worry about. You can verify it: load the page, go offline, and the tool still reads and cleans your PDF.

Because metadata answers questions you may not want answered: who made this document, with what, and when. Removing it is a small step that closes a surprisingly common information leak.

Names and Identities
The Author field is auto-filled by most software with the logged-in user's name or the license holder's name. A freelancer sending a proposal under an agency brand, a job applicant whose CV was edited by a friend, an employee publishing a document that carries a colleague's name, or an author who wants to remain anonymous — all of them leak identity through this one field. Clearing it keeps the document about its content, not its creator.

Timelines You Didn't Mean to Share
Creation and modification timestamps tell stories: a "carefully prepared" report generated an hour before the meeting, a backdated-looking contract whose file says otherwise, or a document edited after it was supposedly finalized. Whether the story is embarrassing or merely nobody's business, deleting the timestamps ends it.

Tooling and Workflow Traces
Creator and Producer fields reveal your software stack — which word processor, which PDF generator, sometimes which version. For businesses, this discloses internal tooling; combined with old software versions it can even hint at unpatched systems. Keywords and Subject fields sometimes carry internal project names or classification labels that were never meant for external eyes.

When to Make It Routine
Clean metadata before sharing CVs and cover letters, contracts and legal documents, reports published on a website, documents sent to journalists or regulators, anonymous submissions, and anything shared with clients under a company brand. Because BlendPDF shows you the fields first, a quick check costs seconds — and if the table shows "No metadata fields found", you can share with confidence.

Trust in a privacy tool should be verifiable, so BlendPDF builds verification into the workflow itself — and you can double-check independently with any PDF viewer.

Built-In Before/After Proof
After cleaning, the tool does something most metadata removers skip: it re-opens the cleaned file it just produced and reads the metadata back out of it. The results appear in a before/after table — each field's original value shown struck through in the "Before" column, and "Removed" in green in the "After" column. This isn't a claim about what the tool intended to do; it's a readout of what the downloadable file actually contains, including whether the XMP stream is still present (it shouldn't be).

Check It Yourself in a PDF Viewer
Open the downloaded "no-metadata-" file in Adobe Acrobat Reader, macOS Preview, or your browser's PDF viewer and look at the document properties (File → Properties, or Tools → Show Inspector). Title, Author, Subject, and the other fields should be empty, and the creation/modification dates should be absent. Independent verification with software you already trust is the strongest confirmation there is.

Re-Upload as a Final Check
You can also feed the cleaned file back into the Remove PDF Metadata tool itself. On a properly cleaned document, the inspection table will report no metadata fields found and no XMP stream present. This round-trip takes seconds and uses the same local, private inspection as the first pass.

Why Verification Matters
Metadata removal has a history of half-measures — tools that blank the visible fields but leave the XMP copy behind, so "cleaned" documents still carry author names in their XML. Reading the metadata back from the actual output file is the honest way to close that gap, and it's why the verification step is not optional in this tool's design.

No. Metadata removal is surgical: it operates on the document's hidden information structures and leaves every visible element of your PDF exactly as it was.

Pages Are Untouched
The text on your pages, fonts, images, colors, page dimensions, margins, headers and footers, tables, and graphics all pass through unmodified. The cleaning operations target the information dictionary and the XMP stream — structures that sit alongside the page content, not inside it. Your document will look pixel-for-pixel identical in any PDF viewer before and after cleaning.

Interactive Elements Survive Too
Bookmarks, internal links, hyperlinks, annotations, and form fields remain functional in the cleaned file. The tool does not flatten, re-render, or re-compress the document; it re-saves the same content with the metadata structures cleared. This also means Arabic and other right-to-left documents come through perfectly — the page content, text shaping, and layout are simply not touched.

One Visible Field to Be Aware Of
A subtle note: some PDF viewers display the document's Title metadata in the window or tab title bar. After cleaning, such viewers will fall back to showing the filename instead. That is the only user-visible difference you might notice, and it's the metadata removal working as intended.

File Size Stays Similar
Because only small metadata structures are removed, the cleaned file is approximately the same size as the original — typically marginally smaller. If you need to shrink the document itself, that's a job for the BlendPDF compression tool, which you can run on the cleaned file afterwards.

Honesty matters more in a privacy tool than anywhere else, so here is the explicit list of things this tool does not remove. Its scope is document-level metadata; other kinds of embedded or visible data need other treatments.

Content Inside the Pages
Text visible on the pages is never altered — including names, addresses, or account numbers written in the document body. Metadata removal is not redaction. If the sensitive information is part of the content itself, you must edit or redact the source document; no metadata tool can help with that, and any tool claiming otherwise should worry you.

Annotations, Comments, and Attachments
Sticky-note comments, highlights, drawing markups, and files attached inside the PDF are preserved, not stripped. Comments deserve attention before sharing: they can carry reviewer names and candid remarks. Check for them in your PDF viewer's comments panel if the document went through a review cycle.

Form Data and Bookmarks
Values typed into form fields, the field names themselves, and the document's bookmark tree are left intact. If you want form fields locked down or merged into the page, use the BlendPDF Flatten PDF tool — a complementary step, not a substitute for metadata cleaning.

Metadata Inside Embedded Images
Images embedded in a PDF can theoretically carry their own EXIF-style data from the camera or editor that produced them. This tool cleans the PDF's document metadata, not the internals of each embedded image. For most documents this is a non-issue, but for photo-heavy files with strict anonymity requirements, it's worth knowing the boundary. The practical rule: use this tool to remove what the PDF says about itself, and review the document's actual content separately before sharing.

XMP (Extensible Metadata Platform) is a second, more modern metadata system that lives inside many PDFs — and it's the one that half-hearted cleaning tools forget. Understanding it explains why BlendPDF's before/after table gives it a dedicated row.

A Metadata Format Within the File
XMP is a block of XML embedded in the PDF's document catalog. Adobe introduced it to standardize metadata across file formats, and most professional software — Acrobat, InDesign, Word's PDF export, and many others — writes an XMP packet into every PDF it produces. It typically contains the document title, creator tool, author, creation and modification dates, and unique document identifiers, all in machine-readable XML.

Why It's a Second Leak
The trouble is duplication: the same facts exist in both the classic information dictionary and the XMP stream. A tool that only blanks the info fields produces a PDF whose Properties dialog looks clean, while the XML inside still says who made the document and when. Anyone who opens the file in a text editor or metadata inspector sees everything. This split is one of the most common ways "cleaned" documents still leak.

How BlendPDF Handles It
The tool checks whether an XMP stream exists and reports it in the inspection table ("XMP metadata stream: Present"). When you clean the file, the entire stream is deleted from the document catalog — not edited, removed. The verification pass then re-opens the cleaned file and confirms the stream is gone, showing "Removed" in the after column. Both the check and the removal happen locally in your browser.

If No XMP Is Found
Simpler PDF generators skip XMP entirely, so the table may show it as "Not set". In that case there is nothing extra to strip, and the cleaning covers just the information dictionary fields and timestamps — the complete metadata footprint of that particular file.

Not directly. An encrypted PDF cannot be modified without its password, so metadata removal on a locked file is technically impossible — and the tool tells you so clearly instead of failing silently.

What Happens with an Encrypted File
When you select a password-protected PDF, the tool detects the encryption during its initial local inspection and shows a hint explaining the situation, with a link to the BlendPDF Unlock PDF tool. No metadata table is shown and no cleaning is attempted, because the encrypted structures can't be safely rewritten.

The Recommended Workflow
Unlock first, clean second: open the Unlock PDF tool, remove the password (you need to know it — this is for documents you own or are authorized to modify), then bring the unlocked file back here to strip its metadata. If the document should stay protected after cleaning, re-apply a password with the Protect PDF tool as a final step. Clean-then-protect gives you a file that is both metadata-free and encrypted.

Why This Order Makes Sense
Encryption protects a document's contents in transit and at rest; metadata removal controls what the file discloses about its origins. They solve different problems and combine well — but the cleaning must happen while the file is unlocked, since that's the only state in which its internal structures can be rewritten. Keeping the steps explicit also means you always know exactly what state your document is in.

The Remove PDF Metadata tool accepts files up to 50MB, with no restriction on page count. For metadata work, this limit is rarely a constraint in practice.

50MB Covers Almost Everything
Metadata lives in a few small structures regardless of how big the document is, so the documents people typically clean — CVs, contracts, reports, papers — are usually a few hundred kilobytes to a few megabytes. Files that push toward 50MB are generally image-heavy scans or design-heavy brochures, and even those fit under the limit in most cases.

Page Count Doesn't Matter Much
Whether your PDF has 2 pages or 2,000, the metadata to remove is the same handful of fields plus the XMP stream. The main cost of a larger file is parsing and re-saving it in your browser's memory, which modern devices handle quickly. There is no per-page processing step in metadata removal the way there is in, say, text extraction.

Output Size Mirrors Input Size
The cleaned file is approximately the same size as the original — usually a whisker smaller, since metadata structures were deleted. If your goal is also a smaller file, run the cleaned PDF through the BlendPDF compression tool afterwards.

Over the Limit?
If a file exceeds 50MB, you'll get a clear message at selection time. Compress the PDF first, then clean the compressed copy — the metadata removal works identically on it. Since everything is processed locally, the limit exists to keep in-browser memory use sane rather than to protect any server.

No. Cleaning produces a brand-new file, and your original PDF — metadata and all — stays exactly as it was on your device.

A Clearly Named New File
The cleaned document downloads with a "no-metadata-" prefix added to the original filename: report.pdf becomes no-metadata-report.pdf. The naming makes it impossible to mix up the shared-safe version with the original, which is exactly what you want when the difference between the two files is invisible on the page.

Why Keeping the Original Can Be Useful
The original's metadata isn't always a liability — internally, the author field and timestamps can serve as a record of who produced a document and when. A sensible pattern is to archive the original for your own records and share only the cleaned copy. Because the tool never touches the source file, this pattern happens automatically.

Non-Destructive and Repeatable
You can re-clean the same original whenever you need a fresh shareable copy, or clean multiple different documents in a row — each run reads its source, produces its cleaned output, and changes nothing else. And since the entire process is local, "your device" is the complete list of places where either version of your file exists.

Yes. The Remove PDF Metadata tool works on smartphones and tablets, with the same local processing and the same verification table you get on desktop.

Full Workflow on a Phone
You can select a PDF from your phone's files app, cloud storage, or Google Drive, review the metadata table (it scrolls horizontally on narrow screens), tap "Remove metadata", and download the cleaned file to your device. The before/after verification works identically — you see each field's old value and its "Removed" status before you share anything.

A Realistic Mobile Scenario
Metadata cleaning on mobile is more useful than it might sound: documents are increasingly received and forwarded entirely on phones. Someone emails you a contract, you need to pass it to a third party, and you'd rather not forward the author trail and timestamps along with it. Open the tool in your mobile browser, clean the file, and share the "no-metadata-" copy — all without a computer.

Privacy Doesn't Depend on the Device
Because processing is in-browser, your document stays on your phone just as it would stay on your laptop. Nothing is uploaded over your mobile connection, which also means the tool is light on data usage and keeps working on flaky connections once the page has loaded. Processing speed depends on your phone's processor, and metadata removal is a light operation — even budget devices handle it in seconds.

Yes, completely free — no fees, no watermarks, and no premium tiers today. Privacy protection shouldn't be a paid upgrade, and BlendPDF treats metadata cleaning as a basic right of anyone sharing documents.

No Payment, Ever, for This Tool
There's no credit card wall, no trial countdown, and no cap on how many documents you can clean per day. Whether you're cleaning one CV or a folder of client deliverables one by one, the tool works the same way at the same price: zero.

No Account, No Sign-Up
You don't need to register or hand over an email address to clean a file. For a privacy tool, requiring you to identify yourself would be a strange start — so the tool simply doesn't. Open the page, select the file, clean, download.

Everything Included
The free tool is the whole tool: the full metadata inspection table, removal of all information fields and timestamps, XMP stream stripping, and the before/after verification pass. There is no "deep clean" held back for a paid tier — what you see described on this page is what every user gets.

Why It Can Stay Free
Because the processing runs in your browser, each use costs BlendPDF essentially nothing in server resources. That economic reality — the same design choice that keeps your file private — is what makes a genuinely free, unlimited metadata remover sustainable.

Metadata removal is a robust operation, but PDFs in the wild are messy, and a few situations can stop the process. Here's what they look like and how to get past them.

Password-Protected Files
The most common blocker. Encrypted PDFs can't be rewritten, so the tool shows a hint pointing to the Unlock PDF tool rather than attempting a clean that would fail. Unlock the document first (with its password), then clean it.

Files Over 50MB or Non-PDF Files
Oversized files are rejected at selection with a clear message — compress or split them first, then clean the result. Files that aren't actually PDFs (or PDFs with a wrong extension) fail at the reading stage; check that the file opens in a normal PDF viewer.

Malformed or Corrupted PDFs
Some PDFs have damaged internal structures that the parsing engine can't safely read or re-save; these produce a "failed to read" error. The inspection is deliberately tolerant — individual metadata getters that misbehave on malformed documents are skipped rather than crashing the whole table — but a fundamentally broken file can't be cleaned. Re-exporting the PDF from its source application, or running it through the BlendPDF repair tool, usually produces a cleanable file.

Trust the Verification, Not the Button
If a rare edge case prevented part of the cleaning — say, an unusual structure protecting its dates — the before/after table will show it, because the "after" column is read from the actual output file rather than assumed. That honesty is your safety net: if every field shows "Removed", the file is clean; if something still shows a value, you know before you share. For persistent failures, refresh the page and retry, and make sure your browser is up to date, since all processing happens in it.