See the Hidden Document Properties Inside a PDF

About the PDF Metadata Viewer

Every PDF stores a small block of document properties that most people never look at and which travels with the file wherever it goes. This viewer lays that block out as a table: title, author, subject, keywords, creator, producer, the creation and modification dates, the page count and the file size. Fields the document never set are shown with a dash rather than left ambiguous.

Two of those entries are routinely misread. Creator names the application the content was originally written in, while producer names whatever actually generated the PDF, so a document might show a word processor as creator and an export library as producer. Author is the one that catches people out, because it is frequently filled in automatically from whatever account or template the file came from. Nothing is altered and no file is produced — this reports and stops. The inspection happens in your browser.

Key Features

• Full property block: Title, author, subject and keywords alongside creator, producer and both timestamps.
• Creator and producer split: The authoring application and the generating application are shown separately rather than merged.
• Empty fields marked: Properties the document never set display a dash, so blank is clearly distinguished from missing.
• Page count and size: Structural details sit beside the descriptive ones for a complete picture in one table.
• Nothing is written: The document is read and left exactly as it was — this produces no output file.

How to Use the PDF Metadata Viewer

1. Add the PDF you want to inspect.
2. Read the table of properties.
3. Pay particular attention to author, title and producer if the file is going to someone outside your organisation.
4. Use the metadata editor if anything there needs changing before you send it.

How It Works

pdf-lib parses the document and its information dictionary is read field by field, with each lookup guarded so that a malformed or absent entry produces a dash instead of stopping the report. Dates are converted into your local formatting. The scope is worth being precise about: this reads the standard document properties, not the separate XMP packet that some publishing software also embeds, and it does not report per-page details, embedded file attachments or the specific permission flags an encrypted document may carry. A file showing little here can still contain other structures, so treat it as a check of the properties rather than an exhaustive audit.

When You Need It

Someone applying for jobs exports a CV to PDF and never thinks about the properties, where the author field is often still the name on the account that installed the software, and the title may read like a filename from three revisions ago. A recruiter opening document properties sees all of it. Checking first takes a moment and occasionally prevents an awkward disclosure about where a template came from. Consultants reviewing a deliverable before it reaches a client, and anyone verifying when a document was really produced, inspect properties for their own reasons.