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.
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.
Author: Jane Smith, Revision: 47, Keywords: CONFIDENTIAL, draft-v3, Manager: David ClarkeAuthor from your Windows/macOS username, CreationDate from the current system clock, Producer from the driver name, Creator from the application you printed from.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.
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
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:
Actually remove the metadata — not replace it
Both Info dictionary and XMP stream. Free, browser-only, nothing uploaded.
#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)
# 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 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:
# 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.
Frequently asked
exiftool -all= document.pdf), FileIntel's PDF Metadata Remover (browser, free), or Acrobat Pro's Sanitize Document function.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.This article describes how PDF print drivers handle metadata based on observable ExifTool output across common operating systems and applications. Behaviour may vary across OS versions, print driver versions, and application configurations. Always verify metadata removal with ExifTool on the specific output file before sharing sensitive documents.