Document property reader
The tool reads common PDF document information fields, including title, author, subject, keywords, creator, producer, dates, and version.
Inspect the metadata stored inside a PDF, copy individual fields, or download the details as a JSON file.
Read title, author, creator, producer, dates, encryption, version, and page count.
Copy one field or export the complete metadata as JSON.
Use this PDF metadata viewer when you need document properties for audits, cleanup, publishing checks, digital asset records, or source verification.
Upload the PDF you want to inspect. The browser reads the file and looks for document information stored by the app that created or edited it.
Check title, author, subject, keywords, creator, producer, creation date, modified date, page count, PDF version, file size, and encryption status before exporting property values.
Copy a single metadata value for a report, or download the full result as JSON when you need a portable record of the document properties.

The tool reads common PDF document information fields, including title, author, subject, keywords, creator, producer, dates, and version.
Metadata appears in a clear table, so missing values, stale author names, and unexpected producer details are easier to spot.
The normal metadata lookup runs in the browser, which keeps the selected PDF local while fields are parsed and displayed.
Copy individual fields for quick checks, or download the complete metadata result as JSON for records, QA notes, or asset tracking.
Use the page before publishing a PDF to check whether hidden author, creator, title, subject, or keyword fields need attention.
Some PDFs do not include every metadata field, and encrypted or damaged files may block parsing even when the document opens elsewhere.
Extract PDF Metadata reads the selected file in the browser, displays available document properties, and creates copied fields or JSON downloads only when you choose them.
The selected PDF is parsed in the browser to read available document properties such as title, author, creator, producer, dates, and page count.
Metadata values, copied fields, and JSON downloads are created in the current session. Refreshing the tab clears the file and parsed details.
Extract PDF Metadata can be used without creating a Rune account, and the normal metadata lookup does not require sign-in.
Check these notes before relying on PDF metadata, especially when the file has passed through scanners, converters, design tools, or signing apps.
The normal metadata read happens in your browser, so the PDF does not need to be uploaded for property inspection.
Use the tool only with documents you are allowed to inspect, since metadata can expose names, software, dates, or internal project details.
Start with a readable PDF. Encrypted, damaged, or partially downloaded files can prevent the metadata parser from returning useful fields.
Metadata can be missing, stale, or inserted by the app that created the PDF, so verify important fields manually.
The JSON export reflects the fields the browser parser can read, including blank values for properties the PDF does not provide.
Treat metadata as a clue, not absolute proof of authorship or ownership, because fields can be edited by other software.
Extract PDF Metadata reads available document info in your browser, but encrypted, damaged, or unusual PDFs may hide fields or fail to parse.
It reads available PDF document properties such as title, author, subject, keywords, creator, producer, creation date, modified date, page count, version, file size, and encryption status.
No. The tool reads document properties and creates copyable or downloadable metadata details. It does not edit the PDF body or overwrite the source file.
Blank fields usually mean the PDF does not contain that property, the value was removed by another app, or the parser cannot read the field from that file.
Yes. After the metadata appears, use the JSON download option to save a structured record that includes the file name and available document properties.
Extraction can fail when the PDF is corrupted, encrypted, incomplete, too large for browser memory, or produced with metadata structures the parser cannot read.
4.5 (380 ratings)