View PDF Metadata Inspector

Our inspection engine provides an exhaustive, multi-layered structural audit of any PDF document:

1. Document Identification & Provenance: Extracts Document Title, Author, Subject, Keywords, Creator application (e.g., 'Microsoft Word for Microsoft 365'), Producer engine (e.g., 'macOS Version 14.5 Quartz PDFContext'), Creation Date, and Modification Date.

2. Standardized XMP Metadata Streams: Parses the XML/RDF metadata packet stored in the document Catalog under /Metadata, revealing Dublin Core schemas, Adobe PDF tags, Rights Management declarations, and PDF/A or PDF/X archival conformance claims.

3. Structural and Version Specifications: Reports the exact PDF version (PDF 1.4 through ISO 32000-2 / PDF 2.0), linearization status (Fast Web View enabled vs. disabled), total page count, and encryption dictionary presence (AES-128, AES-256, or unencrypted).

Under ISO 32000-1 Section 14.11.2, a PDF page is defined not by a single width and height, but by up to five nested rectangular boundaries known as page boundary boxes. Our tool extracts and visualizes the exact dimensions of every box for each page in the document:

- /MediaBox: The physical medium boundaries representing the maximum paper size.

- /CropBox: The visible display boundaries displayed by reader software (defaults to MediaBox if unspecified).

- /BleedBox: The boundary encompassing bleed margins for commercial trimming.

- /TrimBox: The intended finished dimensions of the printed page after cutting.

- /ArtBox: The bounding box encompassing the meaningful visual content area.

Inspecting these boxes allows pre-press operators and graphic designers to catch misaligned margins, improper bleed settings, and hidden content residing outside the crop box before files are sent to expensive commercial printing presses.

A frequent cause of rendering failures, legal e-filing rejections, and commercial print errors is un-embedded or improperly encoded fonts. Our inspector traverses the document's /Pages tree, catalogs every font referenced in the page /Resources dictionaries, and provides an itemized typographic inventory:

- Font Family & PostScript Name: Identifying the exact typeface name.

- Font Subtype: Classifying fonts as Type 1, TrueType, OpenType (CFF), or Type 0 (CIDFont).

- Embedding Status: Declaring whether the font program is Fully Embedded, an Embedded Subset (identified by a 6-character tag like 'BAAAAA+Font'), or completely Un-Embedded (relying on system fallbacks).

- Unicode Encoding: Confirming the presence of compliant /ToUnicode CMaps for accurate text search and copy-paste operations.

In legal disputes, forensic document examiners inspect metadata for temporal and operational inconsistencies. If an agreement claims to have been finalized on January 15, 2024, but the internal /CreationDate or XMP <xmp:CreateDate> timestamp reads October 12, 2025, the document exhibits clear evidence of backdating.

Similarly, discrepancies between the /Info dictionary and the XMP stream often reveal that a document was modified using third-party tools that updated only one metadata layer. Our tool displays all raw timestamps, time zone offsets, and software signatures side by side, providing an objective, verifiable forensic profile for litigation and compliance investigations.

Inspecting sensitive legal discovery filings, merger prospectuses, patent applications, or confidential patient health records using third-party online metadata viewers creates severe regulatory breach liabilities. Uploading confidential files to external servers violates non-disclosure agreements, legal privilege rules, and statutory privacy frameworks (GDPR, HIPAA, SOC 2).

2run.tools operates with an uncompromising zero-cloud privacy architecture. The entire document parsing, metadata extraction, font cataloging, and page box analysis execute 100% locally inside your browser's WebAssembly sandbox. Not a single byte of your document is ever sent across the internet, ensuring an absolute air-gapped security model.

In legal discovery, corporate investigations, and compliance verification, inspecting a document's security dictionary is critical. Under ISO 32000 Section 7.6, encrypted PDFs utilize the Standard Security Handler (version numbers V=1 through V=5) to govern access.

Our inspection engine reads the /Encrypt dictionary, reporting:

- Cryptographic Algorithm: Identifying 40-bit RC4, 128-bit RC4, AES-128, or modern AES-256 (Revision 6) encryption.

- Permission Bitmask (/P): Decodes the 32-bit permission integer into human-readable flags: Print Allowed, High-Quality Print, Modify Contents, Extract Text & Graphics, Annotate & Form Fill, and Accessibility Screen Reader Access.

- Cryptographic Filters: Identifying public key security handlers (PKCS#7 certificates) or digital envelope DRM systems.

This forensic inspection allows legal teams to verify whether an electronic document was modified without authorization or whether printing and copying permissions were restricted prior to disclosure.

In litigation and regulatory compliance proceedings, establishing document authenticity requires verifiable proof. Attorneys and compliance officers must provide evidentiary declarations showing that metadata was inspected without altering file contents.

Our tool allows examiners to export a complete, cryptographically timestamped JSON or CSV audit log detailing every extracted metadata property, font embedding status, and page boundary measurement. This log serves as an objective, third-party verifiable record that can be appended directly to court exhibits, compliance certificates, or internal forensic investigation dossiers.