Preflight: Validating a File Before It Prints
Preflight is the single cheapest piece of insurance in the entire print workflow. It is an automated technical inspection of a print file — almost always a PDF (Portable Document Format, the universal "frozen" page format that presses use) — performed before the file goes to plate or press. Its one job: confirm the file meets every requirement for a clean print run, and if it doesn't, say exactly what is wrong and where.
The name is borrowed from aviation. Pilots run a pre-flight checklist on the ground because you cannot pull over and fix a problem at 30,000 feet. Print is the same: fixing a file on the desktop is free; fixing it after 5,000 sheets have printed wrong is not.
10.1 What preflight is — and why it saves money
Preflight is a gate, not a guess. The file is run against a defined ruleset called a preflight profile (more on that below). It either passes, or it produces a report listing every failure and pointing to the offending object.
Why it saves money is simple arithmetic of when you catch the error:
- Caught at the desktop: costs minutes and is free to fix.
- Caught on press: costs reprints, wasted paper and ink, blown deadlines, and an angry customer.
A single missed RGB logo, a missing bleed, or one over-inked black can scrap an entire run.
10.2 What preflight actually checks
Before the list, two terms that every check leans on:
- CMYK
- The four printing inks — Cyan, Magenta, Yellow, blacK — that presses physically lay down. Everything must end up here (plus any named spot inks).
- RGB
- Red/Green/Blue — the screen color model. It cannot be printed directly; it must be converted to CMYK, and the conversion shifts colors.
1. Resolution / effective dpi
Resolution is how many dots (pixels) fit per inch — dpi (dots per inch). The standard for photos is 300 dpi at final print size for sheetfed/offset; ~150–200 dpi is fine for large-format viewed at distance; line art wants 1200 dpi.
The trap is effective resolution: preflight reads the dpi at the placed/scaled size, not the raw pixel count. Scaling an image up in the layout silently degrades it.
300 dpi image scaled to: 100% -> 300 dpi effective (perfect) 200% -> 150 dpi effective (half - risky) 600% -> 50 dpi effective (junk - will print as mush)
2. Color space — stray RGB and unexpected spot colors
Presses print CMYK plus named spot inks. Any stray RGB, Lab, or untagged object shifts unpredictably — bright blues, greens, and oranges go dull or wrong. Preflight also flags unexpected spot/Pantone colors: each named spot is an extra plate and extra cost. A logo that should be CMYK but carries a stray "PANTONE 286 C" either adds a plate or converts badly.
3. Embedded fonts
A font is embedded when the file carries the actual letter shapes. If a font is not embedded, the RIP (the press's Raster Image Processor — the software that turns the PDF into dots) substitutes a different typeface, reflowing and breaking the layout. All fonts must be embedded or outlined to curves.
4. Bleed presence
Bleed is background artwork extended past the trim line so that when the cutting blade drifts (it drifts ~1–2 mm), no white slivers appear. Standard bleed is 0.125 in (1/8") = 3 mm on every side (Europe/some printers ask 5 mm). The safe / quiet zone keeps text and critical elements at least 0.125 in (¼" for high-stakes jobs) inside the trim. Preflight checks the art actually extends into the bleed and that a BleedBox is defined.
5. Ink limits — Total Area Coverage (TAC)
TAC (also called TIC) is the sum of C+M+Y+K percentages in the heaviest area; the maximum possible is 400%. Too much ink won't dry or trap, causing smearing, set-off, picking, sticking sheets, and paper curl. Standard ceilings by process and stock:
| Process / stock | Max TAC |
|---|---|
| Sheetfed offset, coated | 320–340% |
| Heatset web (magazines) | 300–320% |
| SWOP (US web publication) | 300% |
| Uncoated / newsprint (coldset web) | 240–260% (most restrictive) |
6. Overprint settings
Knockout (the default): the top object removes the ink beneath it. Overprint: the top object prints on top of what's below, mixing inks. Two failures preflight catches:
- Overprint white — white "ink" doesn't exist on most presses, so an overprinting white object simply vanishes.
- Unintended overprint mixing — a knockout object accidentally set to overprint mixes into the background (blue over yellow turns green).
Conversely, small black text should overprint so press misregistration doesn't leave white halos around the letters.
7. Minimum line weight / hairlines
A hairline is a stroke thinner than about 0.25 pt. These can drop out, print inconsistently, or break up. Preflight flags them and bumps them to a safe minimum (often 0.25–0.5 pt). It also flags thin rules and small reversed type (light text on dark) built from more than one ink, which smear or fill in unless registration is tight.
8. Transparency / flattening
Transparency means live effects — drop shadows, blends, opacity. Flattening bakes those effects into plain opaque artwork the press can handle. PDF/X-1a requires flattening; PDF/X-4 keeps transparency live and lets the RIP handle it. Bad flattening leaves artifacts preflight tries to prevent: thin white "stitching" lines, color/text shifts, fattened text, and stray white rectangles inside artwork.
9. Image compression / encoding
Preflight flags destructive or over-aggressive JPEG compression (blocky artifacts), wrong encoding, and oversized images, recompressing cleanly where it can.
10. Page geometry — PDF page boxes
A PDF carries several nested "boxes" that define sizes. Getting them right is half of being print-ready:
+--------------------------------------------+ MediaBox (full sheet) | +------------------------------------+ | | | +----------------------------+ | | BleedBox (trim + 3 mm) | | | | | | | | | TrimBox | | | TrimBox (finished size - | | | (finished page) | | | the key one) | | | | | | | | +----------------------------+ | | | +------------------------------------+ | +--------------------------------------------+ Rule: BleedBox > TrimBox, MediaBox >= BleedBox
- MediaBox
- The full sheet size.
- TrimBox
- The finished page size after cutting — the most important box; it defines the actual print size.
- BleedBox
- Trim plus bleed (3–5 mm larger than TrimBox).
A missing or wrong TrimBox or BleedBox is a preflight failure.
10.3 Preflight profiles & PDF/X compliance
A preflight profile is a saved bundle of rules — for example: "error if RGB present", "warn if image < 300 dpi", "error if TAC > 320%", "require all fonts embedded". Printers keep one profile per press/stock combination and run every incoming file through it.
PDF/X is the ISO "print-safe" subset of PDF; preflight verifies compliance with it. The main variants:
| Variant | Color | Transparency | Notes |
|---|---|---|---|
| PDF/X-1a | CMYK + spot only, no RGB | Must be flattened | Fonts embedded, no JS/encryption/forms, output intent required. Safest, most universal. |
| PDF/X-3 | Adds ICC-managed color; RGB allowed if tagged with an ICC profile | Flattened | RIP converts at output. Common in Europe. |
| PDF/X-4 | ICC-managed color | Live (no flattening) | OpenType fonts. The modern, preferred standard today. |
Every PDF/X file requires an output intent: an embedded or referenced ICC profile (an International Color Consortium color description) or named printing condition — such as FOGRA39/FOGRA51 in Europe or GRACoL/SWOP in the US — that tells the RIP the intended printing condition so it interprets colors correctly instead of guessing.
10.4 How the tools work
- Adobe Acrobat Pro preflight (Tools → Print Production → Preflight) ships press-ready profiles, runs PDF/X validation, reports every issue with clickable jump-points to the offending object, and offers built-in fixups.
- Enfocus PitStop Pro — the prepress industry standard, an Acrobat plug-in — pairs a Preflight Profile (the check ruleset) with an Action List (a recorded sequence of edits/fixes). An "Allow fixes" toggle decides whether problems are auto-corrected or only logged. It produces a clear report with visual highlights and clickable jumps. PitStop Server automates the same via hot folders.
- Others: callas pdfToolbox (the engine behind many systems), Markzware FlightCheck, and many free online DPI/bleed/CMYK checkers.
Tools run in two modes: report-only (flag it, let a human decide) versus auto-fixup (correct it in place). Production shops automate with hot folders so files are checked and corrected without manual touch.
10.5 Fixups — automatic correction
Many problems can be repaired automatically:
- RGB → CMYK conversion via the destination ICC profile.
- Downsample over-resolution images; flag under-resolution (you cannot invent pixels — a 72 dpi photo can't be made sharp).
- Flatten transparency for PDF/X-1a targets.
- Add/define bleed by extending edge content; set TrimBox/BleedBox.
- Embed/subset fonts; outline thin text if needed.
- Bump hairlines to a minimum stroke weight.
- Reduce ink to the max-TAC limit (often using GCR/UCR to swap CMY under-color for K).
- Fix overprint (turn off overprint-white, set black text to overprint).
- Add output intent / convert to PDF/X.
10.6 Reporting issues to non-technical users (the UX last mile)
A store owner uploading artwork must never see "RGB object in TrimBox, effective res 96 ppi, TAC 367%." That is developer output and it reads as "broken." Every check must be translated into plain language + a clear fix:
| Technical problem | What the customer should read |
|---|---|
| Low effective resolution | "This photo will print blurry. Use a sharper version (at least 300 dpi at this size)." |
| RGB content | "Your colors may shift when printed. We'll convert them for print — preview to confirm." |
| No bleed | "Add 1/8 inch of background past the edge so there's no white border after trimming." (offer auto-fix) |
| Text in quiet zone | "Move text in a little so it isn't cut off at the edge." |
| Missing font | "A font isn't included. Outline your text or embed the font." |
10.7 A realistic preflight checklist
- File format: export as PDF/X-1a (safe CMYK) or PDF/X-4 (transparency/ICC); output intent set (FOGRA/GRACoL/SWOP).
- Page boxes: correct TrimBox (finished size) + BleedBox (trim + 3 mm).
- Bleed: artwork extends 0.125 in / 3 mm past trim on all sides.
- Safe zone: text/logos ≥ 0.125 in inside trim.
- Resolution: raster ≥ 300 dpi effective at placed size (line art 1200 dpi); no upscaled images.
- Color: CMYK/spot only (no stray RGB); spot colors intentional and named correctly.
- Fonts: 100% embedded or outlined.
- Ink limit (TAC): within stock ceiling — 240–260% uncoated/news, 300% SWOP, 320–340% sheetfed coated.
- Black recipes: large blacks use rich black (~60/40/40/100 or shop recipe); never 400% registration black in art/text; small black text = 100% K only, set to overprint.
- Overprint: no overprinting white; black text overprints; no accidental overprint mixing.
- Hairlines: no strokes < 0.25 pt.
- Transparency: flattened (X-1a) or correctly live (X-4); no flatten artifacts.
- Compression: no destructive JPEG artifacts; images sensibly sized.
- Misc: single page per page (no spreads unless requested), correct orientation, all links/images present, no security/encryption, and a final human content review (preflight can't catch typos).
- Preflight is an automated pass/fail gate on the print PDF that catches mechanical errors when they're free to fix, not when they're catastrophic.
- It checks effective resolution, color space, embedded fonts, bleed, ink limit (TAC), overprint, hairlines, transparency, compression, and page boxes — against a saved profile, often verifying PDF/X compliance with a required output intent.
- Tools like Acrobat Pro and Enfocus PitStop report issues with clickable jumps and offer auto-fixups (RGB→CMYK, flatten, add bleed, embed fonts, reduce ink) — but low-res and spot-color decisions still need a human.
- Standard figures to remember: 300 dpi photos, 3 mm bleed, 0.125 in safe zone, 0.25 pt hairline floor, and TAC ceilings of 240–260% (uncoated) up to 320–340% (coated sheetfed). Never 400% registration black in art.
- For non-technical store owners, translate every failure into plain language with a visual proof, the consequence, and a recovery action — never a raw error code or a silent rejection.