PDF Print Preflight Checker
Verify bleed boxes (≥ 3 mm / 8.5 pt), TrimBox alignment, font embedding, and image placed resolution (PPI) before sending to press. Enfocus PitStop charges $40/mo and FlightCheck charges $249/yr; this inspects your PDF object hierarchy 100% locally in your browser.
Select or Drop Press PDF
Inspect books, brochures, flyers, catalogs, and packaging artwork.
Next in this job
Chosen from where these tools sit in the catalogue — the same workbench, the same category, the same words. Nothing here measures what you or anyone else opened.
- Markdown to print & PDF document formatterTransform raw Markdown into a beautifully typeset, printable HTML document with page headers, footers, and print styles.Another print tool
- Burst PDF by Rule and Dynamic NamingSplit bulk PDF statements and invoices by bookmark, blank page, or regex pattern match with dynamic output file naming.Another PDF tool
- Compare PDF Documents OnlineWhole-document stream comparison with reflow resilience. Detect insertions, deletions, moved clauses, and formatting changes between PDF contract drafts.Another PDF tool
- Compress PDFRewrite a PDF more compactly and re-encode the photos inside it.Another PDF tool
About this commercial print preflight checker
To preflight a PDF for commercial print: upload your print-ready document. The analyzer parses page boundary boxes (MediaBox, CropBox, BleedBox, TrimBox), verifies whether bleed margins meet the commercial standard of at least 8.5 pt (3mm), inspects embedded font descriptor dictionaries to catch non-embedded fonts, checks image XObjects for RGB color space usage, and calculates effective image PPI against placed page dimensions.
Commercial offset and digital printers reject customer files every day due to missing bleed margins, un-embedded fonts, low-resolution raster imagery, and RGB color space mismatches. Commercial desktop preflight software charges steep monthly subscriptions or hundreds of dollars for prepress profiles. This client-side preflight inspector provides graphic designers, print production managers, and self-publishing authors with an instant, objective technical inspection of PDF files directly in the browser. It uncovers missing bleed allowances, identifies un-embedded PostScript and TrueType fonts, highlights RGB images that need CMYK conversion, and calculates image pixel density to ensure crisp 300 PPI print reproduction.
Step by step
- 1Upload the print-ready PDFSelect or drag your PDF artwork file into the dropzone. The preflight engine inspects file header structures and opens the document dictionary entirely in local browser memory.
- 2Analyze page geometry and box boundariesThe inspector extracts the MediaBox (physical sheet dimension), TrimBox (finished cut dimension), and BleedBox (artwork extension boundary) for every page, calculating margin differences to determine whether standard 3mm (8.5 pt) or 5mm bleed exists.
- 3Inspect font embedding statusThe analyzer traverses page resource dictionaries and font descriptors. It checks whether each font is fully embedded or subset-embedded (indicated by standard 6-character tag prefixes), flagging any un-embedded system fonts that would risk text reflow at the print shop.
- 4Examine image color spaces and PPIImage XObjects embedded within page streams are evaluated for color spaces (DeviceCMYK, DeviceGray, or DeviceRGB) and bit depth. The engine calculates estimated placed PPI against page dimensions, highlighting raster assets under 300 PPI.
- 5Review preflight report and export JSONInspect page-by-page findings and the overall executive summary. Export the technical findings as a structured JSON report to share with print bureaus, clients, or prepress operators.
Why print preflight inspection is critical
In commercial printing, submitting a PDF with technical flaws leads to costly reprints, production delays, and ruined print runs. Unlike screen display where RGB colors shine and missing fonts can fallback to system defaults, commercial offset lithography and high-speed digital presses require strict adherence to mechanical and physical constraints.
Three issues account for the vast majority of commercial print rejections: missing bleed margins, un-embedded fonts, and low image resolution. Bleed is required because guillotine paper cutters have physical tolerances; without artwork extending beyond the trim line, paper shifts during cutting cause unsightly white paper borders along finished edges. Un-embedded fonts force RIP (Raster Image Processor) software to substitute generic typefaces, ruining typographic layout. Low-resolution images appear pixelated and blurry when screened onto paper.
Understanding PDF geometry: MediaBox, TrimBox, and BleedBox
A professional PDF contains up to five distinct rectangular boundaries defined in points (1/72 inch): MediaBox, CropBox, BleedBox, TrimBox, and ArtBox.
The MediaBox defines the total physical page medium upon which the printer prints. The TrimBox specifies the exact dimensions of the finished printed product after cutting and binding (for example, 210 × 297 mm for A4). The BleedBox specifies the boundary to which the artwork content should be clipped when output in a production environment. For commercial printing, the BleedBox must extend at least 3 mm (8.504 points), and ideally 5 mm (14.17 points), beyond the TrimBox on all four sides. This tool verifies the presence of both boxes and mathematically verifies that the bleed margin satisfies minimum industry tolerances.
Font embedding rules and subsetting verification
PDF documents can reference fonts in three distinct manners: fully embedded, subset-embedded, or un-embedded. Fully embedded fonts include the entire font file in the PDF stream. Subset fonts include only the glyphs actually utilized in the document, designated by a standard six-letter tag followed by a plus sign (e.g., "ABCDEF+Helvetica").
Un-embedded fonts include only font metadata (name, metrics, encoding) and rely on the host operating system or RIP to supply the actual glyph outlines. If a commercial RIP does not possess that specific typeface, it substitutes Courier or Arial, shifting baseline alignments and breaking text flow. This preflight checker inspects font dictionaries and FontDescriptor streams (FontFile, FontFile2, FontFile3) to guarantee that 100% of fonts are properly embedded before submission.
Image resolution (PPI) and color space verification
For commercial printing, raster images must maintain an effective resolution of at least 300 pixels per inch (PPI) at 100% reproduction scale. While web graphics display sharply at 72–150 PPI, half-tone printing screens require high pixel density to avoid visible pixelation and jagged stair-stepping artifacts.
Furthermore, commercial printing presses operate using cyan, magenta, yellow, and black (CMYK) ink separations rather than red, green, and blue (RGB) light primaries. Images saved in DeviceRGB must be converted via ICC color profiles to CMYK; un-managed RGB conversions at the RIP often result in muted, muddy, or unexpected color shifts. This tool scans all image streams, identifies color models, and flags RGB assets and sub-300 PPI images.
Engineering scope boundaries and local privacy guarantee
This tool provides comprehensive geometric, font descriptor, and image stream preflight analysis in client-side JavaScript. It does not perform full PostScript RIP rendering, ICC device-link color profiling, or overprint/trapping simulation. For spot color separations (Pantone PMS matching) or specialized ink coverage (Total Area Coverage / TAC) measurements, specialized prepress workflow software may still be required.
Every response from this site is served with a Content Security Policy whose connect-src directive is set to none. That is not a promise in marketing copy; it is an instruction to your browser, and the browser is the one enforcing it. While this page is open it cannot open a connection to anywhere — not to this site, not to anyone else — so there is no path by which your document could be uploaded, not by a bug, not by a future change, not by a script that should not be here. e2e/egress-proof.spec.ts asserts the served header and then tries to send data out by every route a page has and requires each attempt to be refused, and it runs on every build.
The second half of the guarantee is that the code has nowhere to send anything from. lib/tools/local-source-policy.test.ts reads every source file under lib/tools, workers, components and app on every test run and fails the build if any of them contains fetch, XMLHttpRequest, WebSocket, EventSource, sendBeacon or a peer connection, or even a remote address written down in a comment. A tool here cannot acquire an upload by accident, because the file that would have to contain one cannot be committed.
Questions people ask
- What is the standard bleed margin required for commercial printing?
- The standard minimum bleed margin across North America and Europe is 3 mm (approximately 8.5 points) beyond the trim line. Some large-format packaging and book cover printers require 5 mm. This tool checks that your BleedBox extends at least 8.5 points beyond your TrimBox.
- What happens if a font is not embedded in my PDF?
- If a font is not embedded, the print shop’s raster image processor must substitute a local font. This frequently alters kerning, line heights, and character widths, causing text overlap, missing characters, or dropped lines on the printed page.
- Why are RGB images flagged in the preflight report?
- Commercial presses use CMYK inks (cyan, magenta, yellow, black). RGB images must be converted to CMYK, which often shifts bright saturated blues, greens, and oranges to duller shades. Converting images to CMYK in your design program before exporting ensures you see accurate color proofs.
- What does the PPI check measure?
- The preflight tool calculates the effective pixel density by dividing image pixel dimensions by the rendered point dimensions on the page. Images with effective resolution below 300 PPI are flagged because they risk appearing pixelated or blurry in print.
- Does this preflight tool upload my artwork to a cloud server?
- No. All page box calculations, font dictionary inspections, image header analysis, and report generation execute 100% locally in your web browser. No document pages or artwork assets ever leave your device.