What extracts metadata from PDFs and what fields are hidden inside?
A PDF metadata extractor reads a document's classic Information Dictionary (Title, Author, Creator, Producer, CreationDate, ModDate) and its XML XMP packet directly inside your browser via PDF.js, alongside page geometry and text-layer checks, with zero uploads.
PDF files store provenance in two places: the legacy Info dictionary and an ISO 16684 XML XMP stream. Two fields catch document discrepancies fastest: Creator records the authoring app (such as Microsoft Word or InDesign), while Producer (shown as Written by) records the engine that wrote the final PDF bytes (such as Ghostscript, iText, or headless Chromium).
| Metadata Layer | Extracted Fields | What It Reveals |
|---|---|---|
| Document Info Dictionary | Title, Author, Subject, Keywords, Creator, Producer, CreationDate, ModDate, PDFFormatVersion | Who authored the file, which app exported it, which library built the bytes, and timezone-offset timestamps (D:YYYYMMDDHHmmSS) |
| XMP Metadata Packet | Total property count + first 6 property keys from meta.metadata.getAll() | Presence of extended ISO 16684 XML namespaces such as dc:creator or xmp:CreatorTool |
| Geometry & Text Layer | Page count, mm size + standard label (A4, Letter, Legal, Tabloid, A3, A5), rotation, mixed-size flag (25 pages), text layer check (5 pages) | Whether pages are searchable vector text or scanned images needing OCR, plus print-layout mismatches |
| Document Security & Objects | Permission flags, bookmark outline count, embedded attachment filenames, AcroForm field count | Copy/print restriction flags, hidden embedded files, and interactive form counts |
For a complete inventory of hidden PDF fields and how to scrub them before sharing, read what metadata is stored in a PDF and how to remove hidden metadata before sharing a PDF.
How to view and extract PDF metadata online
- Open the PDF. Drop the file onto the box above, or click to browse. PDF.js reads the document information dictionary, XMP packet, and page geometry locally.
- Inspect Author, Creator, and Producer. Review Title, Author, Subject, Keywords, Creator application, Producer library, PDF version, and timezone-decoded timestamps.
- Check text-layer and structural findings. Verify page dimensions in mm (A4, Letter, Legal), mixed page sizes across the first 25 pages, text layer vs scanned status across 5 pages, restrictions, bookmarks, attachments, and form fields.
- Copy or download the metadata report. Click Copy details to place all extracted properties on your clipboard, or click Download report (.txt) to save a record.
What the tool reports
- Identity fields: Title, author, subject, and keywords recorded in the PDF dictionary.
- Decoded dates: Created and modified timestamps parsed from PDF
D:YYYYMMDDHHmmSSstrings into readable dates with UTC offsets. - Software trail: Creating application (
Creator), producing library (Producer), and PDF specification version. - Page geometry: Width and height in millimetres, matching paper names (
A4,A3,A5,Letter,Legal,Tabloid), rotation degrees, and mixed-size alerts across up to 25 pages. - Text layer status: Samples up to 5 pages to tell whether selectable text exists or pages are image scans requiring OCR.
- Structure & restrictions: Permission flags, outline bookmark count, embedded attachment names, form field count, and XMP property count.
Which PDFs work and sampling limits
Every unencrypted PDF from version 1.0 to 2.0 opens locally regardless of total page count. To keep inspection responsive on 500+ page documents, mixed page sizes check the first 25 pages and the text-layer check samples the first 5 pages.
PDFs protected by an open password display a clear prompt to unlock the file first. Documents with only printing or copying permission flags read normally and report that restriction flags are present.
Why reading metadata locally matters more than usual
Parsing runs through PDF.js inside your browser, so the file never crosses the network.
People inspect PDF metadata specifically because it can expose sensitive facts: an author name, an internal file path in the title, a mismatched timestamp, or licensed software in the Producer string. Uploading a private PDF to a server converter discloses that metadata before you ever see it.
What metadata cannot tell you
Metadata is a self-reported record and carries four boundaries:
- Every field is editable: Authors and timestamps can be modified by PDF editors, so treat metadata as evidence rather than cryptographic proof.
- Blank fields mean unrecorded: Many browsers and privacy scrubbers omit Author and Title fields entirely.
- Timezone offsets reflect the generating clock: Stored offsets match whatever local timezone the authoring machine had configured.
- Full XMP XML trees are summarized: The extractor reports the total XMP property count and previews the first 6 property keys rather than expanding full edit-history XML nodes.
This tool inspects properties rather than extracting page prose or tables.
Who reads PDF metadata
- Verifying document provenance: Confirming whether an invoice or contract was actually scanned or exported from a browser or generator script.
- Pre-release privacy checks: Finding an author name, username, or internal folder path before publishing a PDF online.
- Print and prepress QA: Catching mixed page dimensions, unexpected rotation, or missing standard A4/Letter sizing before printing.
- Diagnosing extraction failures: Confirming in seconds whether a PDF lacks a text layer and needs OCR before running text or table extraction.
PDF metadata compared with Office metadata and content extraction
This tool inspects file properties. To pull the actual words out of a PDF, use the PDF text extractor; to convert tables to CSV, use the PDF table extractor; to save embedded images, use the PDF image extractor.
When this extractor reports no text layer, send the pages through image to text OCR. Need to audit Word, Excel, or PowerPoint metadata before exporting to PDF? Use the Office metadata extractor or browse all PDF extraction tools.
PDF metadata format standards and edge cases
PDF has two parallel metadata systems: the document information dictionary (PDF object
with keys /Title, /Author, /Producer,
/Creator, /CreationDate and /ModDate) and XMP metadata
(an XML stream in ISO 16684 format in the document's /Metadata stream). When
both exist, XMP takes precedence per ISO 32000-2. PDF date strings follow the format
D:YYYYMMDDHHmmSSOHH'mm'.
Three edge cases: (a) many PDF creators — including macOS Preview and web browsers — leave
/Author empty but set xmp:CreatorTool to their own application name;
(b) the /Producer field records the library that serialised the bytes
(Ghostscript, iText, PDF.js) rather than the application the user saw — a Canva export
shows iText as Producer, not Canva; (c) creation and modification dates can be identical
(the library wrote them at the same instant) or decades apart (an InDesign file from 2008
last opened in 2024).
Frequently asked questions
How do I see who created a PDF?
Drop the file onto this page. EasyExtract reads the Author, Creator (authoring app), and Producer (PDF writing library) fields locally in your browser.
Is my PDF uploaded to a server?
No. PDF.js parses the binary document inside browser RAM with zero server uploads.
Can PDF metadata be trusted?
Treat metadata as supporting evidence rather than proof. PDF fields can be edited or stripped by export tools and privacy cleaners.
How do I know if a PDF is scanned?
Check the Text layer row. None found means the sampled pages are images requiring OCR; present means selectable text is embedded.
Why does it say my pages are different sizes?
The extractor compares up to 25 pages and flags mixed sizes when width or height differs by more than 2 pt, common in merged PDFs.
What does the Restrictions row mean?
The PDF carries permission flags limiting printing or copying rather than an open password.
Can it read a password-protected PDF?
Not if a password is required to open the document. Remove the open password in a PDF reader first; permission-only PDFs open normally.
Does it show the XMP metadata in full?
It reports the total count of XMP properties returned by PDF.js and displays up to 6 property keys.