A PDF carries more than the pages you can see. Producer strings name the software that made it, timestamps record when, and title and author fields often survive from whatever document it was exported from. The PDF Metadata Viewer reads those fields out of the file structure and shows them without opening a reader.
The parse happens against the raw bytes in your browser. Nothing is uploaded, which is the point when the file is a signed contract or a CV, and it means you can inspect a document you would not be willing to hand to a web service.
What comes back is page count, PDF version, file size, and the document information dictionary: title, author, subject, keywords, creator, producer, plus creation and modification dates. Drag a file onto the panel or click to pick one.
What Each Metadata Field Tells You
- Producer names the library that wrote the file, and Creator names the application the content came from. A mismatch between them is the usual sign of an export pipeline rather than a direct save.
- Version is the PDF specification level, which determines what features a reader must support. Most modern files sit at 1.4 through 1.7.
- Author and Title are frequently left as whatever the source document held, which is why a published PDF sometimes carries a filename or an employee name nobody meant to ship.
- Creation and modification dates come from the document dictionary rather than from the filesystem, so they survive copying and emailing where file timestamps do not.
- Only the first 8 MB of the file is scanned. The metadata dictionary is normally near the start or the end of the structure, so this covers ordinary documents while keeping a 200 MB scan from locking the tab.
What Happens When a PDF Will Not Parse
- An encrypted PDF returns
Could not parse the PDF. The file may be corrupted or encrypted. Its metadata strings are encrypted alongside the content and cannot be read without the password. - Anything that is not a PDF is rejected up front with
Please upload a valid PDF file., checked before any parsing is attempted. - Fields the document simply does not carry are shown as empty rather than invented. A blank Author means the field is absent, not that the tool failed.
- Newer files often carry XMP metadata as an XML stream in addition to the classic dictionary, and the two can disagree. This reads the dictionary, which is the one most tools write.
- Reading metadata is not the same as removing it. If your goal is to strip identifying fields before sending a document, you need a writer, and this tool only reads.