Home› Blog› Does Printing to PDF Remove Metadata?

Does Printing to PDF Remove Metadata?

No. And the reason is stranger than most people expect — printing to PDF doesn't clean your document, it replaces one set of metadata with another. Here's exactly what happens.

📅 October 2026 ⏱ 9 min read ✎ Darshan Lamichhane 🔄 Updated October 2026
DL
FileIntel · October 2026 · 9 min read
Short answer

No. Printing to PDF does not remove metadata — it replaces the original document's metadata with new metadata from your print driver. The resulting PDF gets your OS username as the Author, the current timestamp as the CreationDate, and the print driver's name as the Producer.

To actually remove metadata, you need a dedicated stripping tool: FileIntel's PDF Metadata Remover (browser, free) or exiftool -all= document.pdf (command line, free).

A paralegal at a law firm had developed what she thought was a privacy workflow. Before sending documents to opposing counsel, she would open the file in Word, print it to PDF using Microsoft Print to PDF, and send the fresh output. Different file. No edit history. Clean.

Then a colleague ran ExifTool on one of those "clean" PDFs out of curiosity. The Author field said her name — pulled from her Windows account. The CreationDate showed the exact time she printed it. The Producer field announced "Microsoft: Print to PDF." The XMP stream had all of these fields in duplicate.

She hadn't removed metadata. She had replaced the original document's metadata with a fresh set that included her identity, the exact moment she processed the file, and evidence of the print-to-PDF workflow she'd been quietly using. The print-to-PDF step had, if anything, made the document more identifiable than the original Word export.

This is one of the most common misconceptions in document privacy. It comes from reasonable intuition — you're generating a new file, so surely the old metadata doesn't carry over. That's correct. But "doesn't carry over" and "gets removed" are different things.

The core fact

Printing to PDF doesn't remove metadata. It generates a brand-new file with brand-new metadata sourced from your operating system and print driver. You lose the original document's revision history — but you gain a new Author, a precise creation timestamp, and a Producer field identifying exactly how the file was made.

#1. What actually happens when you print to PDF

When you print a document to a PDF driver — Microsoft Print to PDF, macOS PDF filter, or any other — the driver renders the document as a visual output and generates a completely new PDF file from scratch. It treats the document like a printer would treat paper: it receives a stream of rendered pages and turns them into a file.

That new file has no memory of the original document's metadata. But it does have metadata — supplied by the print driver and the operating system at the moment of printing.

What happens during print to PDF — step by step
1
Original document — Word, Google Docs, InDesign
Contains: Author: Jane Smith, Revision: 47, Keywords: CONFIDENTIAL, draft-v3, Manager: David Clarke
2
Print driver receives rendered page output
The application sends rendered page images to the PDF print driver. Document structure, metadata, and edit history are not passed to the driver — only visual output.
3
Print driver generates new PDF with its own metadata
The driver creates a fresh PDF and populates its metadata from the OS: Author from your Windows/macOS username, CreationDate from the current system clock, Producer from the driver name, Creator from the application you printed from.
4
Result — a new PDF with replacement metadata
Original Revision: 47 gone. Original Keywords: CONFIDENTIAL gone. But: Author: Jane Smith (still there, from OS). CreationDate: [right now]. Producer: Microsoft Print to PDF. XMP stream with all fields duplicated.

The revision count, internal keywords, and manager field do disappear. But the most privacy-sensitive field — your name — stays, because it comes from your OS account rather than the document itself. And you get something new: a precise timestamp showing exactly when you processed the file.

#2. The real ExifTool output — before and after

Here's what actually happens to the metadata when you print to PDF, shown as real ExifTool output.

Original Word export Before print
Author : Jane Smith
Manager : David Clarke
Keywords : CONFIDENTIAL, draft-v3
Creator : Microsoft Word
Producer : Microsoft: Print To PDF
Revision : 47
Create Date : 2026:09:01
Modify Date : 2026:10:04
After print to PDF Different metadata
Author : Jane Smith ← still there (OS account)
Manager : [empty]
Keywords : [empty]
Creator : Microsoft Word
Producer : Microsoft: Print To PDF
Revision : [none]
Create Date : 2026:10:05 11:34:22 ← exact print time
XMP:all : All fields duplicated in XMP

The Manager field and Keywords are gone — those came from Word's document properties and the print driver doesn't know about them. But the Author is still there because it comes from the OS, which the print driver reads directly. And the CreationDate is now a precise timestamp of when you printed, which tells any recipient exactly when the file was processed.

In the paralegal's case, this was actually worse than the original. The original Word export had a CreationDate of weeks ago. The print-to-PDF version had a CreationDate of the exact morning she sent it — revealing she had specifically processed the document before transmission, which is itself a piece of information.

#3. Other methods that don't remove metadata

Print to PDF is the most common misconception, but it's not the only one. Here's the full set of methods people try that don't actually clean metadata:

Common metadata myths
What people try
What actually happens
Print to PDF
Replaces metadata with new OS/driver metadata. Author stays. New timestamps added. XMP stream created.
Save As → PDF from Word
Preserves all existing metadata — Author, Manager, Keywords, revision count. Adds a new ModDate. Does not remove anything.
Re-saving in Acrobat Reader
Acrobat Reader doesn't save changes. Acrobat Pro saves but updates ModDate and may add Producer. Does not strip metadata.
macOS Preview → save
Preserves existing metadata and adds its own Producer field identifying Preview as the last tool. Adds metadata.
Renaming the file
Metadata is inside the file, not in the filename. Renaming has zero effect on embedded metadata.
Changing file extension
The file contents are unchanged. Metadata is embedded in the binary content, not the extension.
Compressing to ZIP
ZIP compression preserves file contents exactly. The PDF inside the ZIP has identical metadata to the original.
Screenshot and re-PDF
This actually works for removing text metadata — but the output is an image-based PDF with reduced quality, no searchable text, and new metadata from your screenshot application.

Actually remove the metadata — not replace it

Both Info dictionary and XMP stream. Free, browser-only, nothing uploaded.

Open PDF Metadata Remover →

#4. What actually removes metadata

Three methods reliably remove metadata from both the Info dictionary and the XMP stream — the two places where your name and timestamps live in a modern PDF.

Method 1 — ExifTool (free, command line)

Remove all metadata — Info dictionary + XMP stream # Install: brew install exiftool (Mac) | apt install libimage-exiftool-perl (Linux)
# Windows: exiftool.org/install.html

$ exiftool -all= -overwrite_original document.pdf

# Verify both stores are cleared
$ exiftool -Author -Creator -Producer -XMP:all document.pdf
# No output = fully clean

Method 2 — FileIntel PDF Metadata Remover (free, browser)

Drop your PDF into fileintel.me/pdf-metadata-remover. The tool removes the Info dictionary, trailer dictionary entries, and XMP stream in a single pass. Files are processed locally — nothing transmitted to any server. The Privacy Risk Score shows every field before and after stripping so you can confirm what was removed.

Method 3 — Adobe Acrobat Pro Sanitize Document

Tools → Redact → Sanitize Document. This performs a complete PDF rewrite — the most thorough approach, addressing metadata, embedded objects, and incremental update history. More thorough than ExifTool for complex documents. Always verify with ExifTool after, as behaviour varies across Acrobat versions.

✓ The correct workflow

The right sequence is: export your document to PDF normally from Word or whatever application you use, then run it through a dedicated metadata stripping tool before sending. Not: export → print to PDF → send. The print-to-PDF step adds a process layer that doesn't clean anything and timestamps the processing.

#5. When print to PDF is actually useful for privacy

Print to PDF is not useless for privacy purposes. It just serves a different purpose than metadata removal.

Removing revision history. Print to PDF loses the edit history embedded in the document structure. A Word document with 47 revision saves produces a print-to-PDF output with no revision count. If the RevisionNumber revealing your edit volume is the specific concern, print to PDF addresses it — though ExifTool does too, more cleanly.

Removing embedded macros and scripts. Print to PDF produces a static visual output. Active content — macros, embedded JavaScript, linked data sources — doesn't survive the render. For documents where you're concerned about active content reaching the recipient, print to PDF is more effective than a metadata strip alone.

Removing complex embedded objects. OLE objects, linked spreadsheets, embedded audio, and similar content don't survive print to PDF. The output is a static page image. If the concern is complex embedded content rather than standard metadata, print to PDF helps.

In all three cases, the right workflow is: print to PDF first, then strip the resulting PDF's metadata with ExifTool or FileIntel. You get the benefits of print-to-PDF (no revision history, no active content) combined with proper metadata removal. Not one or the other.

#6. How to verify your document is actually clean

After any cleaning method, run this single ExifTool command to check both stores simultaneously:

Complete verification — both Info dictionary and XMP stream $ exiftool -Author -Manager -Keywords -Creator -Producer -CreateDate -ModifyDate -XMP:all document.pdf

# If this returns NO output at all — the document is clean
# If anything is returned — those fields still contain data

The most common verification mistake is only checking Acrobat's Properties panel. That panel shows the Info dictionary — it does not show the XMP stream. A document can appear blank in Acrobat Properties while still carrying your full name, original creation date, and software version in the XMP store. ExifTool shows both. For sensitive documents, always check both.

For a complete technical breakdown of what the XMP stream contains and how to specifically target it, see our guide on removing XMP metadata from a PDF. For the full metadata removal workflow covering every method and every metadata layer, see how to remove metadata from a PDF.

Strip metadata properly — not just replace it

Author, Manager, Keywords, XMP stream — all removed in one step. Browser-only, free.

Open PDF Metadata Remover →

Frequently asked

No. Printing to PDF replaces the original document's metadata with new metadata from the print driver. The resulting PDF contains your OS username as Author, the current date and time as CreationDate, the print driver name as Producer, and an XMP stream duplicating all of these. Some original fields like revision count and internal keywords may not carry over — but your name and a fresh timestamp always do.
Print to PDF generates: Author (your Windows or macOS username), CreationDate (the exact moment you printed), Producer (the print driver name — e.g. "Microsoft Print to PDF" or "macOS PDF filter"), Creator (the application you printed from), and an XMP stream duplicating all of these fields. These are supplied by the operating system and print driver, not the original document.
No. Saving or exporting as PDF from Word, Google Docs, or any authoring application preserves all existing metadata and adds a new ModDate. Author, Manager, Keywords, revision count — all carried over. To remove metadata, use a dedicated stripping tool after the export: ExifTool (exiftool -all= document.pdf), FileIntel's PDF Metadata Remover (browser, free), or Acrobat Pro's Sanitize Document function.
No. Print to PDF removes the original document's Author field but immediately replaces it with your OS username. On Windows, that is your Windows account name. On macOS, it is your system account name. The resulting PDF has an Author field — just a different one sourced from the operating system rather than the document. To remove the Author field entirely, strip the PDF's metadata after printing using ExifTool or a dedicated tool.
When you print to PDF, the print driver renders the document as a visual output and generates a new PDF file. This new file gets metadata from the print driver and the operating system — your username, the current timestamp, the driver name. Metadata removal is not part of the PDF generation process. It requires a separate, explicit stripping operation on the output file using a dedicated tool like ExifTool.
Three methods work reliably: (1) ExifTool — exiftool -all= document.pdf removes both the Info dictionary and XMP stream; (2) FileIntel's PDF Metadata Remover at fileintel.me/pdf-metadata-remover — browser-based, removes both stores, nothing uploaded; (3) Adobe Acrobat Pro's Sanitize Document — Tools > Redact > Sanitize Document. After any method, verify with exiftool -XMP:all document.pdf to confirm the XMP stream was cleared.