What PDF Metadata Viewer does
PDF Metadata Viewer reads common properties from a selected PDF and displays them in the browser. The report includes filename, file size, page count, title, author, subject, keywords, creator, producer, creation date, and modification date. It can also be downloaded as a JSON file for a simple record.
These values describe the document but are not necessarily visible on its pages. They may be absent, incorrect, copied from a template, or changed by software. Metadata can provide useful clues during cataloging and troubleshooting, but it should not be treated as verified evidence of authorship or creation time.
When to use this tool
Use the viewer before publishing, editing, or archiving a PDF to identify generic titles, outdated author names, unexpected software fields, or missing descriptions. It can also confirm a page count without rendering every page.
The report is useful when comparing exports from different applications. For a targeted update, open Edit PDF Metadata after recording any values that should be preserved.
- Check whether a report has a useful title before publication.
- Identify the producer application for troubleshooting.
- Record creation and modification dates supplied by the file.
- Review common properties before editing or distribution.
How to view PDF metadata
- Select the PDF using the drop area or file picker.
- Choose View metadata and allow the local parser to read the document.
- Review every displayed field, including entries marked Not set.
- Download the JSON report if a machine-readable record is useful.
- Use Metadata Editor for corrections, then inspect the revised PDF again.
Practical examples
A publishing team receives a file named final-v7.pdf. The viewer shows a generic title, an outdated author, and the office application's producer field. That information helps the team decide what to correct, but the page content and document history still need their own review.
Two visually identical exports have different file sizes. Their producer and modification fields can suggest that they came from different workflows. Metadata alone cannot explain all size differences, but it provides a useful first diagnostic alongside page count and visual inspection.
Tips for better results
- Treat dates and author fields as claims supplied by software, not authenticated facts.
- Save a JSON report before editing when an audit trail is needed.
- Compare metadata with the visible title page and filename.
- Look for personal names inherited from document templates.
- Use specialist inspection software for XMP, attachments, scripts, and full object analysis.
Planning and quality checks
Interpret the report in context. Compare the metadata title and author with the cover, footer, filename, and known publishing workflow. A producer value may identify the application that last wrote the file, not the person or organization responsible for the content. Creation and modification dates can reflect a computer clock, template, conversion, or later rewrite, so document any inference separately from the raw values.
For a repeatable review, download the JSON and retain it alongside the exact PDF version or a trusted file hash. Metadata can change when a PDF is optimized, printed to PDF, merged, signed, or edited, even if pages look the same. Compare like-for-like versions and note the inspection tool and date. The JSON report itself does not include a cryptographic link to the source and should not be presented as immutable evidence.
A privacy review must go further than the displayed fields. Inspect annotations, form values, embedded attachments, layers, scripts, thumbnails, and alternate metadata with specialist software when risk warrants it. The viewer is deliberately narrow and useful for routine properties; that clarity is more valuable than implying a complete forensic scan that a browser interface does not perform.
Where dates matter, preserve their original displayed time zone and raw source rather than silently normalizing them into an unsupported timeline.
Limitations and important details
The viewer reports a defined set of common fields. It does not enumerate every XMP namespace, custom property, embedded attachment, annotation author, form value, JavaScript action, hidden layer, or incremental revision. A “Not set” result means the parser did not return that common property.
Metadata can be forged, removed, or rewritten and therefore does not establish provenance. Creation and modification dates may reflect export software settings rather than real-world events. Encrypted files that cannot be opened are not readable through this viewer.
Frequently asked questions
Does viewing metadata change the PDF?
No. The viewer reads properties and creates an optional JSON report. It does not save changes to the selected document.
Is the listed author guaranteed to be correct?
No. Author is an editable metadata field and may be blank, outdated, or intentionally inaccurate.
What does Not set mean?
The selected PDF did not provide a readable value for that common field through the parser.
Does this find all hidden information?
No. It is a common-property viewer, not a complete forensic or sanitization scanner.
Why download JSON?
JSON provides a structured text record that can be archived, compared, or read by other software.