How to Remove Metadata from a PDF File: Full Guide

Every PDF carries a small amount of invisible baggage. Author names, software versions, creation dates, and sometimes even GPS coordinates from a scanned photo can sit quietly in a file's metadata long after you've forgotten they're there. If you're sending a contract to a new client, submitting a report for peer review, or publishing a document publicly, that hidden data can reveal more than you intend. Here's how to find it and remove it properly.

What Metadata Hides Inside Your PDF

Metadata is descriptive information attached to a file rather than visible on the page. In a PDF it typically lives in two places: the Document Information dictionary (Title, Author, Subject, Keywords, Creator, Producer, creation/modification dates) and an XMP packet, which can store dozens of additional custom fields depending on which application generated the file.

In practice this means a PDF exported from Word might still list the original author's username, the company name from your software licence, and a full revision history if track changes was used before export. A PDF made from a scanned document can carry the scanner model and, occasionally, embedded image metadata including GPS coordinates accurate to within a few metres if the photo was taken on a phone. None of this is visible when you open the file and read it — you have to go looking.

Why You Might Need to Strip It Out

Removing metadata isn't paranoia; it's basic document hygiene in several common situations:

• Legal and court filings — many jurisdictions now require metadata scrubbing before submission, since author names or drafting notes can undermine anonymity or privilege.
• Job applications and CVs — recruiters have found candidates' previous employer names left in the "Company" field.
• Public sector and journalism — leaked or FOI-released documents have repeatedly exposed internal usernames and file paths through overlooked metadata.
• Client-facing work — freelancers and agencies often don't want a client seeing which other companies' templates they reused.

How to Check What Metadata Your PDF Contains

Before removing anything, look at what's actually there:

1. In Adobe Acrobat, open File > Properties to see the Description tab (Title, Author, Subject, Keywords) and the Custom tab for XMP extras.
2. In Preview on macOS, use Tools > Show Inspector > General for a basic view.
3. For a full dump including hidden XMP fields, a command-line tool like exiftool file.pdf is the most thorough option and is free.
4. Several browser-based PDF tools show a metadata summary before you download the cleaned file, which is a quick way to confirm nothing sensitive slipped through.

Step-by-Step: Removing Metadata from a PDF

Using Adobe Acrobat Pro

Open Tools > Redact > Remove Hidden Information. Acrobat scans the document and lists metadata, embedded fonts, attached files, and even hidden layers, letting you tick which categories to strip. This is the most granular option if you already own a licence, but it's a paid product and overkill for a one-off task.

Using a Browser-Based Tool

For most people, an online tool is faster: upload the PDF, the service rewrites the Document Info dictionary and XMP metadata to blank, and you download a clean copy — usually in under 30 seconds, no installation required. Konomic runs this kind of metadata removal alongside its other PDF tools at konomic.io/, processing files on EU-based servers in Germany and deleting every uploaded document automatically within an hour, with no account needed. That combination matters if the document itself is sensitive (a contract, a medical letter, an HR file) and you'd rather not have it sitting on a server indefinitely regardless of what the metadata says. iLovePDF and Smallpdf offer comparable metadata-stripping features and are perfectly capable tools, though both route uploads through infrastructure outside the EU by default and push free users toward account creation for repeated use; Sejda is closer in spirit, with a generous no-signup daily limit but a smaller EU footprint. Which one fits best depends mostly on where you need the processing to happen and how often you're doing this.

Using Command-Line Tools

If you're comfortable with a terminal, exiftool -all= file.pdf strips virtually all metadata in one command and is scriptable for batches. qpdf --linearize combined with exiftool is a common pairing for people processing dozens of files at once, such as before a bulk document release.

On Mobile

Most mobile PDF apps bury metadata editing several menus deep, if it's exposed at all. The practical workaround is to use a browser-based tool from your phone's browser — the interface works the same as on desktop and avoids installing an app just for one task.

What Metadata Removal Doesn't Do

It's worth being clear-eyed about the limits. Stripping metadata does not:

• Remove visible text, watermarks, or tracked changes still shown on the page — that's redaction, a separate process.
• Necessarily clean metadata embedded inside images placed inside the PDF (a photo's own EXIF data can survive inside the container).
• Remove attached files or hidden layers unless your tool specifically checks for those (Acrobat's Remove Hidden Information does; many simple online strippers only touch the Document Info fields).

If your goal is genuine anonymity — say, a whistleblowing document — pair metadata removal with a proper redaction pass and, ideally, flatten the PDF to an image-based format afterwards, accepting the trade-off in file size and searchability.

A Quick Checklist Before You Send

1. Check current metadata (Properties dialog or exiftool).
2. Remove it with your chosen tool.
3. Re-check the cleaned file to confirm the fields are actually blank, not just hidden in the viewer.
4. If the document contains embedded images or attachments, verify those separately.
5. Rename the file itself — filenames sent by email are a form of metadata too, and "Contract_v3_ClientName_INTERNAL.pdf" tells its own story.

Metadata removal takes a couple of minutes and closes off a surprisingly common source of accidental information leakage. It's a habit worth building into any document workflow that leaves your own machine.