The packaging preflight checklist converters actually use

What preflight actually is

Preflight is the step where a print file is checked against the physical realities of the press, the substrate, and the finishing line — before anyone spends money on plates, tooling, or press time. The name is borrowed from aviation: pilots run a preflight checklist so problems are caught on the ground, not in the air. The idea translates exactly. A file that opens cleanly in a design application can still be impossible to print correctly, and preflight is where those problems surface while they're still cheap to fix.

Every converter — the company that actually manufactures your packaging — runs preflight in some form, whether it's a technician working through a checklist or an automated engine scanning the PDF. The output is a pass, or a list of issues to correct and resubmit. Understanding what those tools look for is the difference between a job that moves and a job that sits in a queue waiting on a corrected file.

Why print files get bounced

Most rejected files aren't badly designed — they're built for the screen instead of the press. A monitor emits light in RGB and forgives almost anything: infinite color, no physical edges, no ink. A press lays down four or more inks onto a moving substrate with real mechanical tolerances, then a die or knife trims it. The gap between those two worlds is where errors live. The usual suspects:

• Built in the wrong color space — RGB artwork headed for a CMYK press
• Missing bleed, or critical content sitting right on the trim line
• Low-resolution images that looked crisp on screen and pixelate in print
• Fonts that aren't embedded, so type reflows or substitutes on another machine
• A dieline mixed into the artwork instead of isolated on its own layer
• Too much total ink for the substrate to hold and dry
• Live transparency or effects that render differently at the RIP

None of these are exotic. It's the same handful of issues, job after job — which is exactly why a repeatable checklist works so well.

The packaging preflight checklist

Run every file through the same checks, in roughly this order. This is the list a careful prepress operator keeps in their head, and the one a good automated preflight profile encodes. Print it, or keep it open next to your export dialog.

Check	Why it matters	Fix
Bleed	Cutting tolerance exposes unprinted substrate as a white sliver at the edge	Extend background art ~3 mm past every trim and cut line
Safety margin	Content near the trim gets sheared off or folded through a crease	Pull text, logos, and barcodes ~3 mm inside the cut
Resolution / DPI	Low-res raster images print soft or pixelated	Place images at ~300 dpi at final size; keep logos and type as vector
Color mode	RGB shifts unpredictably when the RIP converts it to process ink	Build and export in CMYK; convert stray RGB to process
Spot colors	Duplicate or unintended spot swatches each add a printing plate	Name real spots correctly; convert the rest to process
Total ink (TAC)	Too much ink won't dry, offsets onto the next sheet, or soaks through	Keep total area coverage within the process limit (~280–320%)
Fonts	Un-embedded fonts substitute or reflow on another machine	Embed all fonts, or convert type to outlines (keep a live copy)
Dieline separation	A cut path buried in the artwork can't drive tooling	Put the die on its own named layer or spot, set to overprint
Overprint / knockout	The wrong setting makes elements vanish or colors mix by accident	Confirm overprint intent; knock out where art should replace what's beneath
Small text & thin rules	Fine detail fills in or breaks up on press, especially in reverse	Meet the minimum type and stroke sizes for the process
Barcodes	Poor contrast, scaling, or quiet zone fails to scan at retail	Use adequate quiet zone and contrast; avoid four-color black bars
Transparency	Live effects can render inconsistently in older workflows	Flatten, or export in a format that preserves it (PDF/X-4)
Image links	Missing linked images drop out or fall back to a low-res preview	Embed images, or supply every linked file with the artwork
Export format	The wrong PDF flavor loses spot, transparency, or color data	Export PDF/X-4 (or the exact spec your converter requires)

The checks that matter most, explained

The table is the quick reference. A few of these deserve a closer look, because they cause the most rework and the most confusion.

Bleed and safety

These are the two margins that trip everyone up, and they pull in opposite directions. Bleed extends the background artwork outward, past the cut line, so that normal tolerance in trimming never exposes the bare substrate. Standard bleed is 3 mm (0.125 in), though some flexible-packaging and label processes want more. Safety pulls important content inward, away from the cut, because anything closer than roughly 3 mm to a trim or fold risks being cut off or landing on a crease. A simple way to remember it: background bleeds out, important content stays in.

Resolution and DPI

Raster images — photographs, scanned textures — are made of pixels, and a press needs enough of them. The working standard is around 300 dpi at the final printed size. The catch is "at final size": enlarging a small web image to fill a panel doesn't add detail, it just spreads the existing pixels until they show. Vector art (logos, type, the dieline) is resolution-independent and stays crisp at any scale, so keep those elements vector wherever you can rather than flattening them into an image.

Color mode: CMYK and spot colors

Screens are RGB; most presses are CMYK — cyan, magenta, yellow, and black — plus any spot inks. RGB can describe vivid colors that simply don't exist in the CMYK gamut, so if you leave art in RGB, the RIP converts it for you, often with a visible shift. Build and export in CMYK so you control that conversion. Spot colors are premixed inks, usually referenced by a matching-system number, each printed from its own plate — ideal for an exact brand color or a metallic. The common mistake is stray or duplicate spot swatches that quietly add plates and cost; keep only the spots you mean to run and convert the rest to process.

Total ink coverage (TAC)

Total area coverage is the sum of the C, M, Y, and K percentages in the heaviest, darkest part of the file. A rich shadow might reach for 100% of every channel — 400% total — which no substrate can absorb. Lay down too much ink and it won't dry in time, offsets onto the next sheet, or soaks and buckles the material. Practical ceilings run roughly 280–320%, depending on the printing process and stock; the converter's profile or output intent sets the exact number. Good separations (with gray-component replacement) rebuild neutral shadows using more black and less CMY, which pulls the total back down without changing the look.

Fonts and the dieline layer

Every typeface used has to travel with the file: embed the fonts, or convert the type to outlines so it becomes vector shapes. An un-embedded font substitutes on the next machine, and your careful spacing reflows. Outlining is bulletproof but removes editability, so keep a live, editable copy for later revisions. Separately, the dieline — the cut and crease paths — must sit on its own named layer or spot separation, set to overprint, so tooling can be built from it without punching a hole in the artwork. If you're unsure how those line types should be structured, see our guide to what a dieline is.

Overprint, knockout, and small detail

Overprint means an ink prints on top of whatever is beneath it; knockout means it removes the area underneath so only the top color prints. Set these wrong and white text can vanish (white doesn't print, so overprinting white deletes it), or two colors mix into an unexpected third. Fine detail is the other trap: very small type, thin rules, and reversed (knocked-out) text can fill in or break up on press, so respect the minimum sizes for your process. Barcodes deserve their own line — give them a proper quiet zone, strong contrast, correct magnification, and ideally a single black rather than a four-color build, or they may not scan.

Transparency and flattening

Drop shadows, glows, blend modes, and reduced opacity are "live" transparency effects. Older print workflows require them to be flattened — baked into opaque artwork — because live transparency could render inconsistently at the RIP. Modern PDF/X-4 workflows preserve live transparency and handle it reliably, which is one reason many converters now prefer that format. Either way, the goal is the same: what you see in the design app is what the press produces.

Exporting a print-ready file: PDF/X-4

All of the above lands in the export. The PDF/X family is a set of ISO-standardized subsets of PDF built specifically for reliable print exchange — they require the things preflight checks for, so a correct PDF/X file is already most of the way to passing. PDF/X-4 is the common modern target because it supports live transparency and ICC color management. The older PDF/X-1a flattens everything and forces CMYK or spot, and some converters still ask for it. There's no universally "right" one — always match the exact spec your converter provides. When you export, embed the fonts and color profiles, set the correct output intent, and include trim and registration marks if the spec calls for them.

How PackOS automates preflight

PackOS runs these checks the moment a file is uploaded. It detects the package structure, isolates the dieline from the artwork, reads the color and separations, and flags the same issues a prepress operator would — bleed, resolution, ink coverage, stray spots, un-embedded fonts, transparency — before the file ever reaches a converter. Because it also rebuilds an editable, dimensioned model of the package and understands the substrate and production route, it can judge each check against how the job will actually be made rather than against a generic profile. The result is that print-readiness stops being a back-and-forth over email and becomes something you see immediately. You can read more about the quality and preflight layer on the technology page, or run it on a real file with Quick Quote.