How to View PDF Metadata (Title, Author, Creation Date)

What PDF Metadata Is

PDF metadata is structured information embedded in the document that describes the file rather than its visible content. It lives in two places: the Info dictionary in the file's trailer, and, for modern PDFs, an XMP metadata stream. The standard fields are the title, author, subject, keywords, creator, and producer, plus creation and modification dates. The creator is the application that generated the original document, such as Microsoft Word, LibreOffice Writer, or a browser's print function. The producer is the software that wrote the final PDF, such as an Adobe application, a print driver, or a server-side conversion library like Ghostscript or ReportLab. That distinction matters more than people expect: a PDF whose producer is a basic driver but whose creator is a design suite tells you the file was likely printed or converted at some point rather than exported directly. Dates follow a specific format such as D:20240115143000Z, where the Z indicates a timezone and the digits encode year, month, day, hour, minute, and second. Fields that are absent, malformed, or contradictory are themselves information: a document with no creation date but a modification date is telling you it was re-saved by a tool that dropped the original history. Many PDFs fill only some of these fields, and files generated by older tools frequently leave the author and subject empty, so an incomplete metadata panel is normal rather than suspicious. Beyond the standard fields, the XMP stream can hold custom properties, such as a document version, an internal reference number, or the camera information for a scanned document. The full metadata picture is broader than the fields a typical viewer shows.

When Checking Metadata Is Useful

Metadata inspection answers practical questions that the document text itself cannot. Before signing a contract, you can confirm which application produced the file and when, which helps you judge whether you are looking at the version you expect or a later edit slipped in by a different tool. Auditing downloaded files, verifying that an invoice was created before a certain date, and checking whether a document was modified after you exported it all depend on these hidden fields. Support teams use metadata to identify which generator produced a problematic PDF when a user reports rendering or printing issues — the fix is often as simple as knowing which export path failed. Researchers and journalists check the author and creation date to corroborate when a document was produced and by what tool, which is useful for dating leaked or archived files. There is also a skeptical use that earns its keep. If a PDF claims to come from one source but the producer field names an unrelated application, or the dates are inconsistent with the document's stated history — a report dated before the meeting it summarizes, a contract modified after its signing date — that is a legitimate red flag worth investigating before you rely on the file. Metadata will not give you a verdict on its own, but it gives you the questions. Knowing the creation and modification dates of every document that reaches your desk is a form of due diligence that costs seconds and occasionally catches a real problem, such as an invoice that was regenerated to hide an earlier version.

How to View PDF Metadata

You do not need Acrobat or any installed editor to read PDF metadata. The PDF Metadata Viewer parses the file structure directly in your browser, so the document is never uploaded and processing happens entirely on your device. This is the quickest way to see the full field set without touching your installed software, and it works even when the PDF viewer you normally use hides the metadata panel or buries it several menus deep. Because nothing leaves your machine, it is also safe to use on confidential documents such as contracts, legal filings, and unreleased reports, which is precisely the class of file whose provenance you most want to check.

1. 1Open the PDF Metadata Viewer in your browser
2. 2Drag and drop your PDF file into the drop zone, or click to browse and select it
3. 3Wait a moment while the local parser reads the trailer and Info dictionary
4. 4Read the displayed fields: title, author, creator, producer, page count, and dates
5. 5Copy any field you need or close the tool — the file has not left your device

How to Read What You Find

Start with the creation and modification dates, which are the fields people most often misread. CreationDate is when the PDF was first written; ModDate is when it was last changed. A document whose ModDate predates its CreationDate is suspicious — that combination should not occur from a normal editor — as is a contract whose ModDate falls after the signature date, because it implies the file was touched after it was agreed. Keep two caveats in mind. First, ModDate only updates when an editor actively rewrites it, so it can be absent even in a file that was clearly edited, and some tools set it only when you save through their interface. Second, the author field is whatever the creating application set it to, which is frequently your operating system's username rather than a real name — treat it as a hint about which account produced the file, not a verdict about who wrote it. The creator and producer pair is where most of the diagnostic value lives. A document created in Microsoft Word and exported through a print driver has two different values, and the gap between them tells you about the conversion path. Cross-check the producer against the expected workflow: a file that claims to come from a professional design tool but shows a basic print driver as producer was likely converted somewhere unexpected, which matters if you care whether the file is a true original or a re-rendered copy. Finally, check the page count and compare it to what you expect; a missing page changes the document's meaning, and the metadata is the fastest way to catch it before you read all thirty pages.

Limits of Metadata as Evidence

Metadata is informative but never proof, and understanding its limits prevents you from drawing the wrong conclusion. Every field can be edited with a PDF tool, so a changed author name or a backdated timestamp does not make a document forged, and an unchanged one does not make it genuine. Some tools rewrite the Info dictionary on save and drop the original values entirely, which can look like tampering when it is really just the editor's behavior. A producer value of a known application only means the file was written by that software at some point; it says nothing about whether the content is authentic, complete, or approved. The absence of metadata proves nothing either, because many legitimate generators write none at all — a PDF produced by a minimal library may carry just a producer and no dates. Use the fields as corroborating evidence alongside the document text, the file hash, and the context in which you received the file. If you are auditing something important, compute a SHA-256 hash of the file before and after any metadata edit so you can detect later changes, and keep a snapshot of the metadata alongside the hash. The combination of a hash and a metadata snapshot gives you a baseline that the fields alone cannot: the hash proves whether the bytes changed, and the metadata tells you what the document claims about itself. Together they let you distinguish a cosmetic re-save from a substantive edit, which is the distinction that actually matters in most disputes.

Cleaning Metadata Before Sharing

PDFs you share publicly often carry more than you intend. The author field may expose your operating system username, and the creator or producer can reveal the exact software and version you use, which is more detail than most organizations want in the wild — it tells the world about your toolchain and can help an attacker target you. Before publishing a PDF, open it in the PDF Metadata Viewer and check what is embedded, then remove or rewrite the fields you do not want shared. Organizations also store internal naming conventions in the title or keywords fields, which is exactly the kind of detail that leaks through otherwise harmless-looking files, such as a budget labeled with an internal project code. Metadata hygiene for PDFs belongs in the same category as removing EXIF from photos: it takes seconds, it closes a class of accidental disclosure, and it should be part of any document release checklist. If you work with documents that carry client or employee names in the metadata, the same cleanup applies before a file goes outside your team. Make the check a habit at the point of export rather than a post-hoc repair, and verify with the viewer that the cleaned file shows only what you intend. A one-time habit costs less than a single embarrassing leak, and the tool makes the inspection so fast that skipping it is the harder choice.

Frequently Asked Questions

A few questions come up often enough that they deserve direct answers. Why is the author field showing my computer's name instead of my name? Because the creating application usually fills that field from the operating system's account name, and the default is rarely the person's real name — which is exactly why it is worth cleaning before sharing. Can you change metadata to hide that a document was edited? You can rewrite the dates and author fields with a PDF editor, but the change itself is not invisible: a file whose ModDate is earlier than its CreationDate, or whose dates contradict the file's own history, is a signal. What does it mean when the page count field is missing? Some generators simply omit it; the viewer can still count pages by parsing the document structure, so a missing field is not a problem. Is XMP metadata the same as the Info dictionary? They overlap, and modern viewers usually prefer the XMP stream, but an older file may carry values in the Info dictionary only. When in doubt, read both. Does viewing metadata ever alter the file? No. Reading the trailer and the Info dictionary is a purely read-only operation, so the document is never modified by inspection, which is also why the PDF Metadata Viewer is safe to use on files that are signed or otherwise sensitive to change.