Polotno

File inspector

PDF preflight checker

Drop a print PDF, get a report on what gets files rejected: sizes, trim, bleed, unembedded fonts, RGB colour, spot inks, overprint, transparency. Free, in your browser, nothing uploaded.

Quick answer

Most print rejections come down to a few things: no bleed, a missing TrimBox, a font nobody embedded, or artwork still in RGB. All four are checkable before you submit.

Formula: drop PDF → geometry + content checks → pass / warn / fail / not determined

Drop a PDF here, or

Checked in your browser. The file never leaves your machine.

The checks that catch most rejections

Print files fail for boring reasons far more often than exotic ones. A merged document with three page sizes. A flyer exported at the trim size with zero bleed. A headline in a font nobody embedded. A logo still in RGB. This tool reads both the PDF’s geometry and its page contents, and flags exactly those, in seconds, instead of the printer’s queue doing it overnight.

The rules come from a production preflight engine we built for a commercial printer, running against their real product profiles: digital, offset, large format, foil, and contour-cut work.

What it will not pretend to know

A preflight tool that cries wolf is worse than no preflight tool, and one that gives false comfort is worse still. So where the browser genuinely cannot know something, the report says so instead of inventing a verdict.

Image resolutionis the clearest case. Measuring true DPI needs each image’s placement size, which lives in the content stream we do not parse. What we can compute is the resolution an image would have placed at page size. Most images are placed smaller than that, and so print sharper — but one scaled past the page prints coarser, so the estimate is strong evidence rather than proof. The check only calls a file safe when it clears double the 300 DPI target, and otherwise reports the number and says plainly that it is an estimate.

Ink coverage needs an ICC colour engine, and PDF/X conformanceneeds a certified validator. Neither runs here. If your printer asks for a formal PDF/X report, use Acrobat Pro’s Preflight or veraPDF.

Fixing what it finds

FindingFix
No bleedRe-export at trim + bleed. The bleed calculator gives exact targets
No TrimBoxEnable printer’s marks / bleed settings in the export dialog
Mixed page sizesRebuild from one source at one size; check pages in the page size checker
Password protectionRe-save without security from any PDF viewer
Nonstandard sizeConfirm against the product spec. Custom sizes are often intentional

If the file needs rebuilding rather than re-exporting, the PDF to JSON converter opens it as an editable design where sizes and bleed can be set properly before a clean export.

Frequently asked questions

Q: What does this preflight check?

Two layers. Page geometry: password protection, consistent page sizes, TrimBox presence, bleed margins in mm, rotation flags, and standard-size match. Page contents: whether fonts are embedded, whether colour is RGB or CMYK, which spot inks the file uses, whether overprint is set, and whether the file relies on transparency. Together these cover the great majority of print rejections.

Q: What does it NOT check?

Three things, and it says so on screen rather than guessing. True image resolution, because that needs each image's placement size from the content stream — we estimate it at page-size placement instead, and only call a file safe when it clears double the 300 DPI target. Ink coverage, which needs an ICC colour engine. And PDF/X conformance, which needs a certified validator such as Acrobat Pro's Preflight or veraPDF. Run this first; if your printer asks for a formal PDF/X report, that is the tool they mean.

Q: What is preflight in printing?

The pre-submission inspection of a print file against the printer's technical requirements: sizes, bleed, colors, fonts, resolution. The name comes from aviation's pre-flight checks; the purpose is catching problems before they cost a print run.

Q: Why did my printer reject a PDF that looks fine on screen?

Screens forgive what presses don't. The usual suspects, in order: no bleed on an edge-to-edge design, wrong page size, RGB images that shift in CMYK conversion, and missing fonts. The first two are exactly what this tool checks in seconds.

Q: Is my file uploaded?

No. The structure is parsed entirely in your browser.

Want this in your app? Embed Polotno SDK.

TRUSTED BY

100,000+

CREATORS

300+

BUSINESSES

ExpediaUnbounceLovePopPostGridPredis.ai