Skip to content
PDFRuns in your browser

PDF Metadata Viewer

Inspect the PDF metadata of any file: title, author, producer, dates and page size.

Upload
Single file · 40 MB max
Privacy
Nothing is uploaded
Cost
Free · no sign-up · no watermark

Loading tool…

The tool is loading its code on your device. This happens once and is cached for later visits.

Processed entirely on your device

Your file is read, transformed and re-encoded inside this browser tab using JavaScript. There is no upload endpoint — nothing leaves your machine, nothing is stored, and the result is created as a local object URL that disappears when you close the page.

Overview

About the PDF Metadata Viewer

View PDF metadata free online: title, author, subject, keywords, creator, producer, dates, version, page count and page size — read locally and exportable as JSON.

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. This PDF metadata viewer lets you inspect all of these PDF properties online free, so you can check PDF author, dates and producer before sharing a file. It is the first thing a forensic examiner reads when checking PDF metadata and the last thing an author checks before sending a file out.

What the PDF metadata table shows

Twelve rows, in the order they appear:

  • 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.
  • Created and Modified — the two dates as the producer recorded them, decoded into a readable form.
  • PDF version — 1.4 to 2.0 in practice, and a rough guide to which features the file is allowed to use.
  • Pages and First page size — structural facts read from the document itself rather than from the dictionary.
  • Encrypted — whether the file carries an encryption dictionary, which explains why other tools refuse it.

Four of those repeat above the download button as a summary strip: pages, file size, PDF version and the encrypted flag. A field the producer never wrote still gets its own row in the PDF info checker, showing a dash where the value would be, which is itself information — see below.

How PDF metadata dates are read

PDF stores dates as D:20240315123000+01'00': year, month, day, hour, minute, second, then a UTC offset. This page reads the digits and renders them as an ordinary date and time, and it discards the offset. What you see is the wall clock the producing machine thought it was reading, not that instant converted into your own timezone.

That is usually the more useful of the two. A scan stamped 09:14 in its own office reads as 09:14 here, which is what you want when the question is whether a document existed before a meeting. It does mean two files created at the same instant in different timezones can display different times, and that a truncated value such as D:2024 is padded out to the first of January at midnight rather than shown as incomplete. Anything that does not follow the D: pattern at all is passed through exactly as the file wrote it, so an unusual producer still gives you the raw PDF metadata string to look at.

What this PDF properties viewer does not read

It reads the document information dictionary — the classic PDF properties structure, and the one every viewer exposes under “Properties”. Modern producers frequently write an XMP packet alongside it: an XML stream carrying Dublin Core fields, EXIF-style camera data, revision history and document IDs. That packet is not parsed here, so a file can hold considerably more metadata than this table shows. Treat a clean-looking table from this PDF metadata reader as “nothing in the classic dictionary”, not as “nothing in the file”.

The page size comes from the first page only, measured through a renderer that applies the page's rotation first. That makes the row a genuine check on orientation — turn a portrait A4 with the rotate tool and this reads 842 × 595 pt instead of 595 × 842 — but it also means a document with mixed page sizes is described by its first sheet alone.

Why checking PDF metadata matters before sharing

Documents accumulate PDF metadata silently: a résumé carries the word processor author name in its PDF metadata'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 PDF metadata dictionary takes a second and answers what the file will say about you.

Reading it elsewhere

The same values download as a JSON object, indented two spaces and keyed exactly as the table labels them, for anyone building metadata checks into a workflow — archiving, intake validation, or simply keeping a record of what a received document claimed about itself. The file is named after your PDF with -metadata.json appended.

Because that object carries the page count, the byte size and the encrypted flag alongside the descriptive fields, it is enough on its own to build an intake rule: refuse anything encrypted, warn on anything whose producer string is unfamiliar, log every author name for later review. None of it requires the document to be retained, which is the real point of reading metadata in the browser — the check happens, and the file goes nowhere.

Reading an empty table

Empty is common and rarely means broken. Metadata has always been optional, and applications fill it inconsistently: a LaTeX document usually carries a producer and little else, a browser print-to-PDF often carries a title and no author, and a scanner writes whatever its firmware was configured with. Files that have passed through a privacy tool may have had fields deliberately cleared, and anything produced by this site's own tools carries producer Collabs Tool plus a creator string naming the tool that built it — Collabs Tool — Merge PDF, Collabs Tool — JPG to PDF — with images-to-PDF output also taking its title from the first filename.

The interesting case is the opposite — a field that is full when nobody expected it to be. An author name from a shared template, a title left over from the document it was copied out of, or a modification date later than the one on the covering email. Those are the entries worth reading before a file goes out, and the ones a recipient with the same PDF metadata viewer would see immediately.

View PDF metadata free with complete privacy

This PDF metadata viewer reads the document information dictionary of any PDF file directly in your browser. View PDF properties including title, author, subject, keywords, creator, producer, creation and modification dates, PDF version, page count, page size and encryption status — all without uploading the file anywhere. The PDF info table presents twelve fields in a clear layout, and you can export the same data as a JSON file for scripting, archiving or intake validation. Whether you need to check PDF author before sharing a résumé, verify PDF metadata dates on a contract, or inspect a file's producer string for provenance, this PDF properties viewer gives you the answers instantly. View PDF metadata online free and know exactly what a file says about itself before it leaves your hands.

Step by step

How to use the PDF Metadata Viewer

  1. Drop a PDF onto the upload area, or click it to browse.

  2. Press Read metadata to view PDF properties — the PDF metadata dictionary is parsed in your browser by this PDF properties viewer.

  3. Review the table: authorship, producer, dates, version, page count and page size.

  4. Download the same twelve values as JSON, named source-metadata.json, for a script or a record.

Why use it

Benefits and common use cases

What this tool is good for, and what it deliberately does not try to do.

See what a file says about itself

Before sharing a document, use this PDF metadata viewer to know exactly which author name, producer string and creation dates travel inside it — the fields most people discover only after someone else reads them.

Provenance at a glance

In this PDF info table, the producer and creator strings reveal which application generated a file, and the PDF version hints at its feature set — useful when checking PDF metadata to debug why a document misbehaves in one viewer.

Machine-readable export

The PDF metadata JSON download carries all twelve fields in one pretty-printed object, so metadata checks can be scripted, diffed between versions, or archived alongside the document they describe.

Questions

Frequently asked questions

Short, honest answers about quality, limits and privacy.

What is the difference between creator and producer?

The creator is the application the author used to write the document — a word processor, say. The producer is the software that turned it into a PDF, often a print pipeline or library. Scanned files frequently show the scanner software in one field and a PDF library in the other.

Why are some fields empty?

PDF metadata is optional and applications fill it inconsistently. Many exporters write only a producer string; files whose PDF metadata passed through privacy tools may have had fields deliberately cleared. Empty is a normal, informative answer.

Can this tool edit the metadata?

Not yet — this page reads and exports. The Compress PDF tool clears title, subject and keywords as part of its rewrite, which is the usual reason people want metadata changed before sharing.