PDF Metadata Viewer

Every PDF carries an information dictionary: who wrote it, what produced it, when it was created and modified, plus a version number and page geometry. It is the first thing a forensic examiner reads and the last thing an author checks before sending a file out.

What the table shows

• Title, author, subject, keywords — the descriptive fields, often empty, sometimes embarrassingly full.
• Creator and producer — the writing application and the PDF-generating pipeline, which together usually identify exactly how a file came to exist.
• Creation and modification dates — as recorded by the producer, timezone quirks included.
• PDF version, page count, first page size — structural facts read from the document itself rather than the dictionary.
• Encrypted — whether the file carries an encryption dictionary, which explains why other tools refuse it.

Why it matters before sharing

Documents accumulate metadata silently: a résumé carries the word processor's author account name, a contract carries the law firm's template producer string, a scan carries the machine's serial in the creator field. Reading the dictionary takes a second and answers what the file will say about you.

Reading it elsewhere

The same values download as a JSON object, keyed exactly as shown, for anyone building metadata checks into a workflow — archiving, intake validation, or simply keeping a record of what a received document claimed about itself.