PDF Page Size Inspector
Inspect readable PDF page dimensions and page-box metadata locally.
Inspect print-relevant PDF structure
This first-pass PDF inspection stays in your browser and separates detected structure from checks that remain inconclusive without a full preflight engine.
A PDF that opens is not automatically production-ready
Adobe's print-production tools treat MediaBox, CropBox, TrimBox, BleedBox and ArtBox as distinct page boundaries, while PDF/X-4 is a standardized print-exchange condition. The local inspector deliberately reports some checks as inconclusive because a browser token scan cannot certify a compressed PDF.
| Check | Local InkyValley triage | Full production preflight |
|---|---|---|
| Readable page boxes | Yes — detected dimensions and optional trim comparison | Yes — all pages/objects |
| Encryption token | First-pass detection | Definitive file-security validation |
| Font embedding | Token evidence only; absence is inconclusive | Verify every used font/resource |
| Output intent / color spaces | Readable-token evidence | Profile validity, object colors, separations and ink rules |
| Effective image resolution | Not reliable for arbitrary PDF objects | Object-by-object effective resolution |
| PDF/X-4 conformance | No certificate | Use a conforming preflight profile/engine |
What the result is useful for
PDF Page Size Inspector is useful before export or handoff because trim, bleed, safe area and PDF page boxes describe different production boundaries and should not be guessed from the visible page alone.
How the calculation works
PDF Page Size Inspector applies the labeled input values to the production arithmetic shown in the result; inputs are kept explicit so the assumption can be audited later.
What this calculator cannot know
A mathematical bleed or box size does not validate a PDF. Printer-specific marks, color spaces, fonts, overprint, transparency, ink limits and finishing tolerances still need preflight.