PDF preflight: how to verify a file before printing

1. What PDF preflight actually means

The term comes from aviation: the checks performed before take-off. In print production, preflight is the technical verification of a file before it is committed to production. French-speaking printers often call it “contrôle en amont” — both names describe exactly the same operation.

Preflight does not judge the creative work and does not replace the client’s proofreading. It answers a different and far more concrete question: will this file produce what the shop expects, without a surprise on press?

That is why a file that “opens fine” can still be unusable: missing bleed, an image placed at 96 dpi, a non-embedded font, unintended RGB colour, or ink coverage beyond what the process can hold.

• Prepress checking and preflight: same operation, two vocabularies.
• Scope: the technical properties of the PDF, not the editorial content.
• Expected outcome: an explicit decision — ready to produce, to correct, or to return to the client.

2. What a preflight must really check

A useful check covers five families: page geometry, resources, colour, file structure and readability. A check that misses one of them produces either abusive approvals or unjustified rejections.

Not every finding carries the same weight, and that is precisely where preflight quality is decided. A 250 dpi image on uncoated stock is not a defect; a non-embedded font is almost always blocking. The tool must separate the tolerable deviation from the error that will cost a print run.

• Finished size and page boxes: MediaBox, CropBox, TrimBox and BleedBox present, coherent and in the right order.
• Bleed that is genuinely present — not merely declared — including on rotated pages.
• Images: effective resolution at placed size, transparency, ICC profiles, missing, damaged or uninspectable images.
• Fonts: full embedding or subsets, missing glyphs, silent substitution on open or at the RIP.
• Colour: the spaces actually used (CMYK, RGB, grey, spot), overprint, white underprint, total ink coverage, output intent.
• Structure: base PDF version, declared PDF/X conformance, encryption, annotations, embedded actions, readability.

3. Three ways to run preflight today

Manual checking in Acrobat Pro remains the reference for a single file: open a profile, run the analysis, read the report. It is efficient and costs nothing extra when the licence is already installed, but every file requires human attention, and the outcome depends on who is looking.

Prepress plugins such as PitStop or pdfToolbox reach much deeper into the PDF structure and enable powerful corrections. They assume a dedicated workstation, a licence per seat, and an operator who knows which rule applies to which job.

Tools built for automated checking aim at something else: applying the same rule to every incoming file, only performing safe corrections, then separating the files that are ready from those needing a human decision. That is the model that holds when volume grows and several operators share the work.

• Single file, occasional need → manual checking is enough.
• Advanced prepress work, deep and custom corrections → prepress plugin.
• Steady volume, several operators, traceability → dedicated tool with a queue and statuses.

4. Why manual preflight breaks at scale

Manual preflight costs little for one file and a lot for fifty a day. The real cost is not the analysis itself — that takes minutes — but the decision: which operator looks, which rule they apply, and what they do when the file is ambiguous.

Without written rules, two operators make two different decisions on the same file. Without a trace, nobody can explain three weeks later why a job was accepted with borderline bleed. That ambiguity, more than the technology, is what generates rework.

• One rule per shop, not one rule per operator.
• An explicit status: ready to produce, to review, rejected — never “roughly fine”.
• A consultable trace: which file, which rule, which decision, on which date.

5. Checking a PDF in a few minutes: the method

Always start with geometry: expected finished size, page boxes, bleed. A mistake here invalidates the rest of the check, because missing bleed cannot be recovered after the run.

Then move to resources — effective image resolution, font embedding — and to colour: spaces in use, spot colours, total ink coverage compared with the process and the stock. Finish with structure: PDF/X conformance, output intent, file readability and absence of encryption.

If information is missing to decide, the correct outcome is REVIEW, never READY. Asking the client for a re-export costs far less than a reprint — and the commercial relationship survives a precise question much better than a failed run.

• Geometry → resources → colour → structure: always in that order.
• Compare every deviation with the job specification, not with a personal preference.
• When in doubt: REVIEW and return to the client, never a default approval.

6. False positives and false negatives: the usual traps

A preflight that is too strict rejects perfectly printable files and eventually exhausts clients and operators alike. A preflight that is too permissive lets through the defect that will cost a full run. Both errors are expensive, just not at the same moment.

The threshold must depend on the process and the substrate: the same total ink coverage can be acceptable in offset on coated stock and blocking in digital printing or on uncoated paper. That is why a production profile — not a universal limit — is the right way to configure a check.

• RGB is not an error by itself: late conversion must be intentional and controlled.
• A declared PDF/X is not proof of conformance: verify the properties, not the label.
• A declared bleed does not prove the artwork actually extends to the edge.
• An encrypted, truncated or uninspectable file must never default to ready-to-print.

7. Frequently asked questions about PDF preflight

Is there a free PDF preflight? Acrobat Reader does not perform preflight: the official tool ships with Acrobat Pro. Online viewers that accept your file upload are rarely compatible with confidential customer PDFs.

What is the difference between preflight and PDF/X? PDF/X is an exchange standard that reduces interpretation ambiguity; preflight is the verification operation. A PDF/X file can still fail the preflight of a given job.

Can you run preflight without Acrobat Pro? Yes: a dedicated tool reads the PDF structure itself and applies your production rules without depending on an external suite.

Do files have to be uploaded to the internet? Not necessarily. Checking locally on the workstation avoids exposing customer files and works offline.

Does preflight replace the prepress operator? No. It removes repetitive work and oversights, then leaves the human decision on genuinely ambiguous cases.