Preflight Check: Catch Print Errors Before They Cost You

Picture 5,000 brochures sliding off the press, and every one of them shows a blank white box where your client’s logo should be. The logo was white, set to “overprint,” and white ink does not exist on most presses. On your laptop it looked perfect. On paper it vanished.

A preflight check would have caught that for free, in seconds, before a single sheet printed.

Preflight is the single cheapest piece of insurance in the entire print workflow. It is an automated technical inspection of your print file, run before the file ever reaches a plate or press. Its one job is to confirm the file is ready, and if it isn’t, to tell you exactly what’s wrong and where.

Why this matters

The name comes from aviation. Pilots run a checklist on the ground because you cannot pull over and fix a problem at 30,000 feet. Print works the same way. Fixing a file on your desktop is free. Fixing it after the run is on the floor is not.

Here is the whole argument in one line of arithmetic:

• Caught at the desktop: costs you minutes, and is free to fix.
• Caught on press: costs reprints, wasted paper and ink, a blown deadline, and an angry customer.

A single missed RGB logo, one forgotten bleed, or one over-inked black can scrap an entire run. Preflight is a gate, not a guess. Your file either passes, or it produces a report listing every failure and pointing straight at the object that caused it.

Think of it as spell-check and grammar-check for a print file. It catches the mechanical, repeatable mistakes automatically. It cannot judge whether your message is right, so a human still has to proof the words. But everything machine-checkable, it checks.

Two terms you need first

Almost every preflight check leans on these two color models, so it’s worth 20 seconds to lock them down.

• CMYK is the four printing inks a press physically lays down: Cyan, Magenta, Yellow, and blacK. Everything in your file must end up here, plus any named spot inks.
• RGB is the Red, Green, Blue screen model. It cannot be printed directly. It has to be converted to CMYK, and that conversion shifts colors, often dulling bright blues, greens, and oranges.

If you remember nothing else: screens are RGB, presses are CMYK, and the gap between them is where a lot of “but it looked great on my monitor” disasters live.

What preflight actually checks

These are the repeatable, mechanical faults that ruin a run. None of them are about taste. They are all about whether the file is physically printable.

Resolution, measured the way that actually matters

Resolution is how many dots fit per inch, written as dpi. The standard for photos is 300 dpi at final print size for offset printing. Large-format work viewed from a distance can drop to 150 to 200 dpi, while crisp line art wants 1200 dpi.

The trap is effective resolution. Preflight reads the dpi at the size you placed the image, not the raw pixel count. Scale an image up in your layout and you silently destroy it:

• 300 dpi image at 100 percent → 300 dpi effective (perfect)
• 300 dpi image at 200 percent → 150 dpi effective (risky)
• 300 dpi image at 600 percent → 50 dpi effective (will print as mush)

Real example: a 600 by 400 pixel web JPEG dragged to fill an A4 cover lands at roughly 40 dpi effective. It looks fine on the laptop and prints as visible mush. The effective-resolution check flags it instantly, while a naive “it says 300 dpi” check would wave it through.

Color space, including spot colors you didn’t mean to add

Any stray RGB, Lab, or untagged object will shift unpredictably on press. Preflight also flags unexpected spot colors, like a rogue “PANTONE 286 C” hiding inside a logo that was supposed to be plain CMYK. Each named spot color is an extra physical printing plate, which means extra cost, so an unexpected one is either a surprise on your invoice or a bad automatic conversion.

Embedded fonts

A font is embedded when the file carries the actual letter shapes inside it. If it isn’t, the press software substitutes a different typeface, and your layout reflows and breaks. The rule is simple: all fonts must be embedded or outlined to curves. No exceptions.

Bleed

Bleed is background artwork extended past the trim line. The cutting blade drifts by a millimeter or two on every job, and bleed means that drift cuts into your background instead of leaving a thin white sliver along the edge.

Standard bleed is 0.125 inch (3 mm) on every side. There is also a safe zone: keep text and anything important at least 0.125 inch inside the trim, so nothing gets clipped. Preflight confirms the art actually reaches into the bleed area.

Ink limit (Total Area Coverage)

TAC is the sum of your Cyan, Magenta, Yellow, and blacK percentages in the heaviest area of the file. The theoretical maximum is 400 percent. Pile on too much ink and it won’t dry, causing smearing, sheets sticking together, and paper curl.

The ceiling depends on the paper and process:

Process and stock	Max TAC
Sheetfed offset, coated	320 to 340%
Heatset web (magazines)	300 to 320%
SWOP (US web publication)	300%
Uncoated / newsprint (coldset)	240 to 260% (most restrictive)

The classic mistake here is registration black: 100/100/100/100, a full 400 percent. That recipe belongs only on crop and registration marks, never in artwork or text. Drop it onto a newsprint run with a 240 percent limit and it never dries, smears onto the next sheet, and ruins the whole run.

Overprint settings

Two objects can interact in two ways. Knockout (the default) means the top object removes the ink beneath it. Overprint means the top object prints on top of what’s below, mixing the inks together. Preflight catches the two failures this creates:

• Overprint white makes a white object vanish, because there’s no white ink on most presses to print on top with. (This is the brochure disaster from the opening.)
• Accidental overprint mixing happens when a knockout object is wrongly set to overprint, so blue over yellow quietly turns green.

There’s a flip side worth knowing: small black text should overprint on purpose, so that if the press misregisters slightly, you don’t get thin white halos around every letter.

Hairlines, transparency, and compression

Three quieter checks that still scrap jobs:

• Hairlines are strokes thinner than about 0.25 pt. They can drop out or print broken, so preflight bumps them up to a safe minimum.
• Transparency means live effects like drop shadows and blends. Flattening bakes those into plain opaque art the press can handle. Bad flattening leaves thin white “stitching” lines and stray rectangles, so preflight watches for it.
• Compression catches destructive JPEG artifacts and oversized images, recompressing cleanly where it can.

Page boxes, the geometry of “print-ready”

A PDF carries several nested boxes that define its sizes. Getting them right is half the battle:

• MediaBox is the full sheet size.
• TrimBox is the finished page size after cutting. This is the most important box, because it defines your actual print size.
• BleedBox is the trim plus bleed, 3 to 5 mm larger than the TrimBox.

The rule is straightforward: BleedBox is bigger than TrimBox, and MediaBox is at least as big as BleedBox. A missing or wrong TrimBox or BleedBox is a preflight failure on its own.

Profiles and PDF/X, the rulebook behind the gate

A preflight profile is a saved bundle of rules, like “error if RGB is present,” “warn if an image is under 300 dpi,” “error if TAC is over 320 percent,” and “require all fonts embedded.” A good printer keeps one profile per press-and-paper combination and runs every incoming file through it.

PDF/X is the official ISO “print-safe” subset of PDF, and preflight verifies whether your file complies. The three you’ll meet:

Variant	Color	Transparency	In plain terms
PDF/X-1a	CMYK and spot only, no RGB	Must be flattened	The safest, most universal choice. When in doubt, send this.
PDF/X-3	Adds ICC-managed RGB if tagged	Flattened	Common in Europe; the press converts color at output.
PDF/X-4	ICC-managed color	Live, no flattening	The modern preferred standard when your printer supports it.

Every PDF/X file also needs an output intent: an embedded color profile or named printing condition (like FOGRA39 in Europe or GRACoL/SWOP in the US) that tells the press exactly which printing conditions you designed for, so it interprets your colors correctly instead of guessing.

The tools that run it

You don’t do any of this by eye. The industry uses dedicated software:

• Adobe Acrobat Pro has a built-in preflight (Tools → Print Production → Preflight) with press-ready profiles, clickable jump-points to each problem object, and built-in fixups.
• Enfocus PitStop Pro is the prepress industry standard, an Acrobat plug-in that pairs a check ruleset with an “Action List” of recorded fixes. Its server version automates the whole thing through hot folders.
• Others include callas pdfToolbox (the engine inside many systems), Markzware FlightCheck, and plenty of free online dpi, bleed, and CMYK checkers.

These tools run in two modes: report-only, which flags problems and lets a human decide, and auto-fixup, which corrects them in place.

Common misconceptions

“It looked perfect on my screen, so it’ll print fine.” Your screen is RGB and backlit. The press is CMYK ink on paper. Bright colors dull, white overprints vanish, and low-res images that look crisp at laptop size fall apart at print size.

“My image is 300 dpi, so resolution is handled.” Only at 100 percent placement. Scale it up in the layout and the effective resolution drops in lockstep. A “300 dpi” photo placed at 300 percent is really 100 dpi.

“Black is just black.” There are several blacks. Plain 100 percent K for small text, a rich-black recipe for large solid areas, and 400 percent registration black that belongs only on printer’s marks and nowhere near your artwork.

“Auto-fixup will rescue anything.” It rescues a lot, but it has hard limits. You cannot invent pixels, so a 72 dpi photo can’t be made sharp. And an automatic spot-color conversion can shift your brand color. Risky fixes need a human and customer sign-off.

How to pass preflight on the first try

Run this checklist before you send a file, and again the moment it arrives at the printer. The earliest catch is always the cheapest.

1. Export as PDF/X. Use PDF/X-1a for safe CMYK, or PDF/X-4 for live transparency and ICC color. Set the output intent (FOGRA, GRACoL, or SWOP).
2. Set the page boxes. Correct TrimBox for the finished size, BleedBox at trim plus 3 mm.
3. Add bleed. Extend background art 0.125 inch (3 mm) past the trim on all four sides.
4. Respect the safe zone. Keep text and logos at least 0.125 inch inside the trim.
5. Check effective resolution. Raster images at 300 dpi or more at placed size, line art at 1200 dpi, and no upscaled images.
6. Clean the color. CMYK and intentional spot colors only, with no stray RGB.
7. Embed every font or outline it to curves.
8. Stay under the ink limit. Match the TAC ceiling for your stock: roughly 240 to 260 percent for uncoated, up to 320 to 340 percent for coated sheetfed.
9. Get your blacks right. Rich black for large areas, plain 100 percent K set to overprint for small text, and never 400 percent registration black in art.
10. Audit overprints. No overprinting white, black text set to overprint, no accidental mixing.
11. Kill hairlines. No strokes thinner than 0.25 pt.
12. Do a final human read. Preflight can’t catch a typo. You can.

One more tip if you’re building software that shows these results to non-technical customers: never display “RGB object in TrimBox, effective res 96 ppi, TAC 367%.” That reads as “broken.” Translate every failure into plain language with a visual proof, the consequence, and a recovery action. “This photo will print blurry, please upload a sharper version” beats a raw error code every single time.

Conclusion

The one idea to keep: preflight catches mechanical errors when they’re free to fix instead of when they’re catastrophic. It is the boring, automated gate that stands between a clean run and 5,000 wrong sheets, and it costs you nothing but a few minutes and the discipline to run it.

But notice what preflight can’t do. It confirms your file is printable, not that your colors will look the way you imagined them. A file can pass every check and still come back with a sky that’s the wrong shade of blue, because the gap between your screen and the press is its own deep subject. That’s where color management and proofing come in, and it’s where a lot of the real craft of print actually lives.