Get PDF Document Info Online — Inspect Properties, Fonts & Security
Check PDF document properties, page dimensions, PDF version, embedded fonts, encryption permissions, and metadata online for free in your browser.
DROP PDF FILES HERE
or click to choose target PDF document (.pdf)
How PDF Specification Inspection Works
Audit PDF headers, metadata dictionaries, typography resources, and security bitmasks in three steps.
Queue PDF Document
Select or drag your PDF document into the browser workspace. Files load directly into memory without transmission.
Parse Catalog & Fonts
The client engine traverses the Document Catalog, trailer dictionaries, page /Resources fonts, and security flags.
Review & Export Specs
Inspect properties on screen, copy the formatted report to clipboard, or download structured JSON for compliance logs.
Four Document Inspection Features
Analyze low-level PDF structural properties, embedded typography, and access restrictions with total data privacy.
Specification Inspection
Inspects header magic bytes for specification version (PDF 1.4 to 2.0), exact byte size, total page count, and producing software.
Metadata Extraction
Parses Title, Author, Subject, Keywords, and creation/modification timestamps from the root Document Catalog dictionary.
Font Descriptors
Scans page /Resources dictionaries to identify embedded font names, standard vector glyphs, and TrueType or Type1 font families.
Permissions & Encryption
Audits document /Encrypt dictionary flags to determine whether printing, copying, annotating, or form modifications are permitted.
Utilvo In-Browser vs Cloud Metadata Viewers
Why client-side in-memory document inspection provides superior privacy, zero credential exposure, and instant execution.
| Feature | Utilvo In-Browser | Cloud Metadata Viewers |
|---|---|---|
| Document Privacy | Zero bytes uploaded (100% in-browser memory) | Full documents transmitted to third-party cloud servers |
| Confidential Metadata Exposure | Document Title, Author, and timestamps never leave local RAM | Stored in server request logs and temporary disks |
| Processing Latency | Sub-second client parsing via WebAssembly & pdf-lib | Queue wait times and upload/download bandwidth lag |
| Security Permission Auditing | Direct client bitmask evaluation of /Encrypt dictionaries | Generic superficial file properties without permission details |
| File Quotas & Limits | Unlimited inspections with zero page or filesize caps | Daily inspection limits and upload size restrictions |
How PDF Info Dictionaries, XMP Streams & Encryption Flags Work
How our client engine parses Document Catalog dictionaries, font subsets, and security permission bits in local memory.
PDF Specification Header Parsing
Every valid PDF file begins with %PDF- followed by the specification version (1.0 to 2.0). The parser checks the first 1024 bytes and cross-references the Catalog /Version entry to determine structural compatibility.
Info Dictionary vs XMP Streams
PDF stores metadata either in classic /Info key-value dictionaries or modernized XML-based XMP metadata streams. The engine audits both to surface legacy and modern metadata tags without data loss.
Font Resource Traversal
Fonts are declared within individual page /Resources dictionaries under the /Font key. The inspector traverses page object trees, identifies PostScript font names, and confirms font descriptor subsetting.
Zero-Knowledge Privacy Guarantee
Document parsing, trailer inspections, and property evaluations happen entirely inside your browser memory sandbox. No document tokens, names, or metadata tags are ever transmitted to external servers.
Quick Audit Checklist for PDF Page Sizes, Fonts & Permissions
Verify these requirements before releasing public PDFs, court filings, or commercial prepress runs.
Verify Header Integrity
Ensure the file contains valid PDF magic numbers (%PDF-) and has not suffered binary truncation during transfer.
Review Author & Identity Tags
Audit author, creator, and producer strings before publishing sensitive public documents or legal exhibits.
Confirm Typography Embedding
Verify that commercial print fonts are embedded or subsetted to avoid font-substitution errors on press runs.
Check Permissions Bitmask
Examine permission flags to ensure intended recipients retain appropriate printing and copying privileges.
Document Formats vs Metadata Serialization
Comparing structural characteristics across PDF specifications, metadata standards, and inspection exports.
| Operation / Format | Standard | Processing Engine | Output Type | Role | Best Use Case |
|---|---|---|---|---|---|
| Unprocessed PDF Input | ISO 32000-1/2 | Local pdf-lib catalog parser | Binary PDF Stream | Source of this inspector | Legal briefs, corporate audits, commercial print prepress |
| Inspected JSON Report | RFC 8259 / ECMA-404 | Utilvo Client Metadata Engine | Structured .json audit | Target of this export | Pre-flight CI/CD pipelines, automated document compliance |
| Formatted Summary Text | RFC 3629 UTF-8 | Clipboard text generator | Formatted plaintext dump | Direct clipboard export | Quick documentation, email filing confirmation, support tickets |
| Adobe XMP Stream | ISO 16684-1 | Extensible Metadata Platform | Embedded XML Stream | Internal document schema | Dublin Core compliance, archival preservation, PDF/A auditing |
| Font Descriptor Catalog | PostScript / OpenType | Resource dictionary scanner | Typography metadata array | Embedded resource audit | Commercial offset printing, graphic design layout verification |
| Security Access Bitmask | PDF Reference §7.6.3 | Cryptographic flag evaluator | Boolean permissions map | Access rights verification | Enterprise DRM compliance, copyright management, legal protection |
Frequently Asked Questions
Understand how client-side PDF inspection parses Document Catalog dictionaries, font subsets, and security permission bits in local memory.
1What document specifications and properties does this inspector reveal?
It reveals the PDF specification version (e.g., 1.4 to 2.0), total page count, byte size, author, title, subject, producing software, and creation/modification timestamps.
2How does the tool detect embedded font descriptors and subsetting flags?
The client inspector scans page resource dictionaries (/Font dictionaries), extracting font PostScript names, font format types (Type 1, TrueType, CIDFont), and embedding flags.
3Are my confidential document metadata properties uploaded to cloud servers?
Never. All Document Catalog parsing, trailer inspections, and font audits run 100% locally inside your web browser RAM with zero network uploads.
4Can I inspect granular security permissions and encryption levels?
Yes. The tool inspects the document /Encrypt dictionary to check whether printing, content copying, form field modification, or annotating permissions are restricted.
5What is the difference between legacy Info dictionary and modern XMP metadata?
The legacy /Info dictionary contains basic key-value strings, while modern XMP streams store XML-based Dublin Core properties and PDF/A compliance flags.
6Can I export the complete metadata inspection report as JSON?
Yes. You can copy the formatted document properties to your clipboard with one click or download the full audit report as a structured JSON file.
Related PDF Metadata & Structure Inspection Tools
Discover complementary serialization, parsing, and document data extraction tools.