Document property reader

Document Metadata Viewer

Open one PDF or Office document and read the properties stored around its visible content.

SupportedPDF · DOCX · PPTX · XLSX
Your file stays on this device.
Waiting for a file
One file · processed locallyDrop a file here

PDF · DOCX · PPTX · XLSX · up to 100 MB

ExifTool loads after you choose a file.Nothing is uploaded.

How to act on this result

  • Search all fields

    Field not found: search native fields as well as the summary. If parsing finished and it is still absent, it was not found in this copy. That cannot distinguish a field never recorded from one removed later.

  • Check reading limits

    Reading incomplete: a damaged block, unsupported format or interrupted parser is a reading limit, not an empty record. Read the warning and keep the original before trying another supported copy.

  • Compare the sources

    Value present: dates, names and coordinates record what the file says. They are editable. Compare source groups and the history of this copy before treating a value as evidence.

Documents: read PDF Info and XMP separately, or Office core and custom properties. Text, comments, revisions and attachments are content. Metadata cleanup is not redaction.

WHY IT MATTERS

Why inspect documents?

Document metadata can reveal authors, edit dates, software history, saved counts, and custom properties.

LOCAL, STEP BY STEP

How the document scan works

The browser inspects document properties locally. It does not upload the file or extract body text, cells, slide text, notes, attachments, or media.

  1. 01

    Choose one document

    Select a PDF, DOCX, PPTX, or XLSX up to 100 MB. Its bytes remain inside this browser tab.

  2. 02

    Verify the real format

    PDF signatures and Office ZIP content types are checked instead of trusting the extension.

  3. 03

    Read property records

    Local parsers read PDF dictionaries or OOXML Core, App, and Custom Properties without extracting visible document content.

  4. 04

    Build the document report

    ExifTool adds native fields while authoring labels, stored statistics, hashes, warnings, and exact paths become searchable.

  5. 05

    Forget the document

    Clear, replace, or refresh to stop both workers and remove the temporary in-tab report.

Have a document ready?Choose a document above

What this report cannot prove
  • Password-protected PDFs and encrypted Office packages are not decrypted or bypassed.
  • Legacy DOC, PPT, XLS and macro-enabled DOCM, PPTM, XLSM files are outside this tool.
  • Stored authors, dates, revisions, and statistics can be missing, stale, or edited.

Frequently asked questions

Will my document be sent to a server?

No. The PDF, OOXML, and ExifTool parsers run inside this browser tab. The document, filename, hashes, properties, and report are not posted to an upload endpoint.

Which document formats and properties are supported?

The viewer supports PDF, DOCX, PPTX, and XLSX up to 100 MB. It reads available title, author, subject, keywords, dates, application, revision, company, custom properties, PDF pages, Word statistics, PowerPoint counts, Excel worksheet counts, and native ExifTool fields.

Does the viewer read document text, cells, slides, or attachments?

No. It does not extract body text, spreadsheet values, slide text, speaker notes, attachments, embedded media, macros, OCR, or scripts. It reads document property records and safe package statistics only.

What happens with encrypted or older Office files?

The viewer does not bypass PDF passwords or Office encryption. Legacy DOC, PPT, XLS and macro-enabled DOCM, PPTM, XLSM packages are rejected with a clear message instead of being opened.

Can author, date, or revision properties prove who made a document?

No. These labels can be edited, copied, omitted, or left stale by an application. Treat them as useful context rather than identity or provenance proof.