Remove PDF Metadata
Strip a PDF's Info-dict fields and its XMP packet in memory; the pages are copied unchanged and nothing is stored.
What this PDF metadata remover does
A PDF carries a second document about itself: the Info-dict fields (title, author, subject, keywords, dates) and the XMP packet, an XML block that repeats them for cataloguers. This page removes both by rebuilding the file from its pages alone, without touching a single page's content.
How to use it
Choose a PDF file and press Run. The stripped file downloads as stripped.pdf with the same page count and the same pages, and the summary names what was removed: the count of Info fields and whether an XMP packet was present.
What is removed, and what is not
Removed: every Info-dict field the file carries and the whole XMP metadata stream. Kept: every page, its text, images, links and form fields. The writer stamps its own Producer tag, as every PDF writer does; that names the tool that wrote the file, not the document it came from.
A real capture
A one-page file carrying a title, an author, a subject, keywords and an XMP packet strips to one page with no Info fields and no XMP stream, in about two hundred milliseconds.
Privacy and safety
The file is sent to the tool server for that run and is not stored. Inputs are capped at 12 MB and 200 pages, and nothing from the file is logged.
Choose a PDF and this page rebuilds the file from its pages alone, dropping every Info-dict field and the whole XMP packet, and returns it as stripped.pdf.
The pages are copied unchanged: text, images, links and form fields survive, and the page count is the same. The summary names what was removed, the count of Info fields and whether an XMP packet was present.
The run happens on the tool server. The file is sent for that request and is not stored; inputs are capped at 12 MB and 200 pages.
What is removed, and what is kept
Removed: every Info-dict field the file carries — title, author, subject, keywords, dates — and the whole XMP metadata stream, the XML block that repeats those fields for cataloguers.
Kept: every page exactly as it was. Only the writer's own Producer tag remains, which names the tool that wrote the file rather than the document it came from.
- Info fields and the XMP packet go; pages stay
- Form fields and links survive the rebuild
- The summary reports the removed count
When stripping is not enough
Metadata is only one place a file can leak: the page content itself may carry names, and embedded images may carry their own EXIF. Stripping the document fields does not redact the visible text.
A file that must hide its words needs redaction, which rasterises the marked pages so the covered text is gone rather than hidden. A file that must hide its readers needs a password, which is the protect-pdf page.
How to use the file upload
Upload the PDF, within 12 MB and 200 pages, and run. The file is sent to the tool server for that request and not stored; the pages are rebuilt from the file's own content.
Download `stripped.pdf` with every Info-dict field and the whole XMP packet gone and the summary naming the removed count. Only the writer's own Producer tag remains; visible text and embedded-image EXIF are untouched.
What to Expect
Best for
- Sharing a PDF without its author and title fields
- Dropping the XMP packet before archiving
- Checking what metadata a file actually carries
Not ideal for
- Hiding names inside the visible page content
- Removing metadata from embedded images
- Restricting who may open the file
What this tool keeps
- Every page, byte-identical in content
- The page count and the page order
- Form fields, links and annotations on the pages
What may need cleanup
- Names visible in the page text itself
- The writer's own Producer tag, which always remains
- Fields an editor re-adds when it re-saves the file
Common errors
- Expecting stripping to redact visible words
- Assuming embedded images lose their metadata too
- Re-uploading the original instead of the stripped file
Example use cases
- Publishing a report without author fields
- Archiving files with a clean metadata slate
- Verifying a supplier file carries no stray fields
Sample input
Choose a PDF that carries title and author fields.
Sample output
stripped.pdf with the same pages, no Info fields and no XMP packet.
Who this is for
- Anyone sharing documents outside their organisation
- Archivists normalising file metadata
- Reviewers checking what a file discloses
Frequently asked questions
What exactly is removed?
Every Info-dict field the file carries and the whole XMP packet. The pages, their text, images, links and form fields stay untouched.
Does anything remain that names the file?
Only the writer's own Producer tag, which names the tool that wrote the file rather than the document it came from.
Is the file still a valid PDF afterwards?
Yes. It is rebuilt from its pages alone and re-opens with the same page count, minus the metadata.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.