RunLocalTools

CMYK Print Color Simulator & Ink Coverage Checker

Upload a PDF and preview how its colors will shift in CMYK print, spot likely out-of-gamut zones, and check total ink coverage against offset and digital press limits — free, and it never leaves your browser.

What it does

Upload a PDF and this tool rasterizes each page in your browser, then shows you a rough preview of how its colors will look once printed in CMYK — screen colors (RGB) and print colors (CMYK) don’t map onto each other cleanly, and a lot of print jobs get an unpleasant surprise the first time they come off press. Alongside the color simulation, it runs a set of prepress QA checks most free tools skip entirely: an out-of-gamut warning overlay, per-pixel total ink coverage analysis with over-limit flags, individual C/M/Y/K channel separations, and a pure-K black finder. You can export the simulated pages as images or a new PDF, and download the ink coverage numbers as a text report or CSV.

One thing to know up front: this is a soft-proofing and QA tool, not a file converter. A browser genuinely cannot write real embedded CMYK color into a PDF or image file — canvas and JPEG encoding are RGB-only, with no client-side path to a true CMYK color space. Nothing calling itself a “PDF to CMYK converter” that runs entirely in a browser is doing that honestly. What this tool gives you instead is an accurate-as-possible simulation of the shift, plus the ink-coverage math, which is arguably more useful before you send a file to print anyway.

How it works

Each page is rendered to a canvas using pdf.js, then processed pixel by pixel:

  • Color simulation converts each pixel’s RGB to CMYK using the standard subtractive formula, then applies a simulated dot-gain curve before converting back to RGB for display. Dot gain — ink spreading slightly wider on paper than the plate specifies — is the single biggest reason a printed midtone looks darker and muddier than it did on screen, so this is what actually produces a visible, physically-grounded shift rather than a no-op round trip. Three profile presets (coated stock, standard offset, uncoated/newsprint) use different gain amounts, since gain varies a lot by paper stock.
  • Out-of-gamut warning flags pixels in the hue/saturation ranges process CMYK inks are well known to struggle with — vivid blues, deep-mid greens, and any very high-chroma “neon” color regardless of hue. This is a heuristic based on documented CMYK weak points, not a true ICC gamut-boundary calculation (that needs a color-management engine no browser ships with), and the tool says so rather than overstating its precision.
  • Ink coverage analysis computes total ink (C+M+Y+K, summed) for every pixel and flags zones over the conventional safe ceilings — 240% for digital press, 300% for offset — the same thresholds most print shops quote for preflight.
  • Pure-K black finder flags near-black areas built from K alone with little or no supporting cyan/magenta/yellow. Small text usually should stay pure K (mixing inks on fine type risks visible misregistration blur), but a large pure-K fill often looks flatter on press than a “rich black” mix — this tool tells you where those pure-K zones are so you can decide.

How to use it

  1. Drop a PDF onto the tool, or click to browse for one. It’s kept in your browser between visits (via IndexedDB) so you don’t have to re-upload it every time — there’s a “Remove & clear saved copy” button whenever you want it gone.
  2. Pick a print profile (coated / standard / uncoated) to match roughly what you’re printing on — this only changes the simulated dot gain, not the ink-coverage math.
  3. Switch the View dropdown between the original, the CMYK simulation, the out-of-gamut overlay, the ink coverage heatmap, the combined view, the pure-K black finder, or an individual C/M/Y/K channel separation.
  4. On the simulated view, turn on the compare slider to drag between the original and the simulated colors side by side — the same drag-to-compare interaction as the site’s general-purpose before/after slider, just built into this view for CMYK specifically.
  5. Use Prev/Next (or type a page number) to move through the document; each page’s stats update in the sidebar as you go.
  6. When you’re happy with what you’re looking at, download the current page as an image, export every page as a zipped image set or a new “preview” PDF, or pull the ink coverage numbers as a text report or CSV for the whole document.

Limitations

  • This simulates likely color shift; it is not a certified ICC soft proof and won’t exactly match your specific press, ink set, or paper. Treat it as an early warning system, not a final approval step.
  • The out-of-gamut overlay is a hue/saturation heuristic, not a true device-gamut boundary test.
  • Because colors are read back from rendered pixels, the pure-K finder can only tell you where a printed result would look like flat pure-K black — it can’t detect a genuine 100/100/100/100 “registration black” specified directly in the source file’s color data, since that specific over-inked combination can’t actually arise from the RGB-to-CMYK math this tool (or any RGB-based tool) uses. The total ink coverage check catches real over-inking regardless of how it got there, which is the more reliable signal anyway.
  • Very large or very long PDFs will take longer to process, especially at the High quality setting — try Draft quality first on big files.

Privacy

Your PDF is processed entirely in your browser using pdf.js — it’s never uploaded anywhere. The only thing saved is a local, browser-only copy (via IndexedDB) so you don’t lose your place on refresh; clearing it is one click.

FAQ

Can this actually convert my PDF to real CMYK? No — and no tool that runs entirely in a browser honestly can. Browsers only ever produce RGB output from canvas and JPEG encoding; writing a real embedded CMYK color space into a file needs a proper print-production tool (Acrobat Pro, InDesign, or a RIP). This tool simulates what the shift will look like and checks your ink levels, which is what most people actually need before sending a file to print.

What’s a safe total ink coverage limit? It depends on your printer, but 240% is the typical safe ceiling for digital/toner-based presses, and 300% for offset litho. Go over those and you risk cracking, slow drying, and show-through on some stocks — this tool flags both.

Why does my “black” text look purple or red in the channel separations? It probably isn’t literal black — screen designs often use a very dark near-black RGB value that isn’t neutral (fractionally more red or blue than the others), which the conversion math will pick up on. Check the Pure-K black finder view; genuinely neutral blacks show up cleanly there.

Should I always use rich black instead of pure K? Not for small text — pure K is usually the safer choice there, since layering multiple inks on fine type risks visible misregistration blur on press. Rich black is worth considering mainly for large solid fills, where pure K alone can look thinner or flatter than a supported mix. Use the Pure-K black finder to see how much of your page falls into that category before deciding.

Why does the out-of-gamut warning flag colors that look fine on my screen? Screens (RGB) can display a wider, more vivid color range than CMYK process inks can reproduce — that’s exactly the gap this tool is trying to surface early. A flagged color isn’t necessarily broken, but it will likely come out less vivid or slightly shifted in hue once printed; if that matters for the design, budget for a physical proof before a full print run.

Can I check a design tool’s export before I send it to a print shop? Yes — if it exports to PDF (most design tools do), you can run it through this tool the same way. If the job is going out as black-and-white only, it’s also worth running it through PDF → grayscale first to confirm how it holds up with color removed entirely, before worrying about CMYK color shift at all.