PDF Metadata Viewer
Use PDF Metadata Viewer to inspect author, dates, software and XMP locally in your browser. Compare stored fields and export JSON without uploading files.
One PDF · Up to 50 MB
Read-only Document Info and XMP inspection. No page rendering, password unlocking or metadata removal.
Read the document behind the filename
A PDF can store descriptive fields in more than one place. Keep their sources visible instead of silently choosing one value.
Document Info fields
Inspect Title, Author, Subject, Keywords, Creator, Producer and saved dates. Creator usually identifies the authoring application; Producer identifies the software that made the PDF. Neither field establishes who wrote its contents.
Separate XMP view
Read the embedded XMP packet alongside Document Info. Compare author and date values across both sources before sharing a report. A mismatch deserves investigation, but is not by itself evidence of tampering.
Export a reproducible report
Download the extracted values as JSON and retain the original PDF separately. The report describes this file at the time you inspected it; it is not a signature check or a certification of its history.
Inspect the exact PDF you will send
Use the final attachment, not an earlier editable document or a screenshot of its properties.
Choose a local PDF
Select or drop one .pdf file up to 50 MB, then click Analyze metadata. Reading starts only after your click. This viewer does not render pages or ask you to upload a document.
Compare source fields
Review Document Info, parsed XMP and the original XMP text separately. Read PDF dates with their timezone suffix: a missing timezone must not be treated as proof of your local time.
Save and re-check
Export a JSON report. If another application edits or sanitizes your PDF, inspect that new output again. A clean Author field does not establish that annotations, attachments or page content are free of personal details.
Local reading, explicit limits
PDF.js reads document-level metadata in your browser. Your selected PDF and extracted values are not sent to our server.
- The tool reads metadata without executing document JavaScript, opening embedded links or changing the source file. Parser assets are served from this site, not a third-party PDF service.
- Password-protected PDFs that require an opening password are not supported in this version. Use an unlocked copy you are authorized to access. Damaged files may fail to parse.
- This is not a redaction, malware scanning, signature validation or metadata removal tool. A metadata report cannot establish that a document is safe to publish.
Method and primary references
This page documents the implemented reader, not an authenticity assessment. PDF fields are shown by source so you can investigate differences. For the parser API and metadata model, see:
Interpret the fields, not just the labels
Practical answers for document handoffs and privacy reviews.
A PDF can carry a legacy Info dictionary and a separate XML metadata packet. An editor may update one without synchronizing the other. Keep both values in your report and inspect the exporting application rather than deciding that one is automatically correct.
No. CreationDate and ModDate are stored declarations that software can change or copy. They are different from your operating system’s download or file modification time. Use a trusted source, signed record or document management history when chronology matters.
No. A missing document-level field means that this reader did not obtain a value there. Names can remain in visible pages, comments, forms, attachments or other structures outside this viewer’s scope. Review those separately before distribution.
For example, a report may be drafted in a word processor and converted by a separate PDF engine. Creator and Producer can describe those two stages. Their values are application-supplied strings, not reliable identities of individual authors.
No. This page is a read-only viewer with JSON export. It does not rewrite PDFs or bypass passwords. After using a separate authorized editing or sanitizing tool, load the resulting PDF here to compare its document-level fields.
The browser passes your local file bytes to Mozilla PDF.js and requests document metadata. No remote file URL is used. Files over 50 MB are rejected before parsing; encrypted or malformed files receive an error rather than an invented report.