PDF Metadata Viewer

How PDF metadata inspection works in seconds: Select any PDF up to 50 MB and the browser parses its document-info dictionary with pdf-lib to reveal title, author, subject, keywords, creator application, producer engine, creation and modification timestamps, plus total page count. Empty fields are skipped so only real data appears, with results in seconds at $0 cost, free and instantly offline with no signup required ever.

What hidden fields reveal: Author entries often leak usernames or email addresses like jsmith, while Creator paths can expose local folders such as C:/Users/John/Documents/report.pdf. Producer names identify the generating engine from Word to InDesign to Canva, and timestamps show when a file was truly built versus what a cover message claims. Reviewing these fields before external sharing prevents accidental disclosure of staff identities, software versions, and internal folder structures. Keywords and subject lines further reveal campaign codenames and client matter numbers that opposing parties should never see in litigation.

Austin legal verification: On 09/21/2026, an Austin attorney reviewing a $500 court filing confirms the Creator shows the approved Word build and the Author contains no personal staff name before e-filing. Scrubbing one leaked username avoids an embarrassing disclosure on the public docket. Because parsing stays local, privileged case strategy inside the brief never traverses any network. The fifty megabyte ceiling covers multi-hundred-page exhibits with scanned annexures intact.

Chicago and Miami production audits: On 09/19/2026, a Chicago publisher auditing a $2,000 manuscript submission verifies the Producer matches the promised professional toolchain rather than a free trial converter. A Miami design lead the same week confirms a $300 client PDF was exported from licensed InDesign on the invoiced date, validating $450 in billable layout hours with timestamp evidence.

Denver and Seattle leak prevention: A Denver analyst checking a $100 vendor contract discovers a hidden author email that must be stripped before forwarding to regulators. A Seattle program team reviewing a $400 quarterly report validates the modification date falls after the final data freeze, ensuring stakeholders never debate stale figures. Missing metadata is normal and simply means the exporter stripped fields for privacy. Government portals and court e-filing systems frequently strip these dictionaries on ingest, so rechecking after download confirms what truly shipped.

New York editorial review and privacy: On 09/20/2026, a New York editor inspects a $150 freelance submission, confirming illustrator credit in Author and a sane four-page count before routing to layout. This viewer never edits files and ignores XMP streams, focusing on the core dictionary most workflows actually use. Check the properties locally, scrub what must stay private, and share with confidence.