PDF Preflight Inspector
Select a PDF to get a local, privacy-first preflight screen. InkyValley reports what it can actually detect and labels compressed/advanced checks as inconclusive instead of pretending the PDF has passed.
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
Use this as a first-pass intake check before opening a file in a full production preflight system. It is especially useful for spotting obvious trim/bleed box mismatches and documenting what still needs professional validation.
How the calculation works
The browser scans readable PDF structure for page objects, page boxes and selected prepress tokens. Detected tokens are evidence of presence; missing text tokens are not proof of absence because PDFs can compress or encode object streams.
What this calculator cannot know
This lightweight browser inspection is not PDF/X conformance testing. A production preflight engine is still required for reliable font embedding, output intents, overprint, transparency, separations, image effective resolution, ink limits and full object-stream interpretation.