For print projects, converting CMYK to RGB produces an uncalibrated screen preview of an ink recipe, not a press-proof target: the browser CMYK to RGB tool turns four device-CMYK percentages into an 8-bit red, green, and blue approximation, a six-digit hex value, and a swatch, using the W3C naive device-CMYK fallback. That fallback treats cyan, magenta, yellow, and black each as a value between zero and one, computes each display channel as 1 − min(1, colorInk × (1 − black) + black), scales the result to 0–255, and rounds to an integer with half-even tie rounding. Because the calculation ignores the press, paper stock, ink set, dot gain, rendering intent, and embedded ICC profile that shape real print output, the screen RGB is best read as a quick approximation for mockups, palette comparisons, and stakeholder previews. Anyone sending files to a press still needs to keep the original CMYK recipe, request the printer's output profile, and run a calibrated, profile-aware workflow before signing off on color.
Why a screen preview earns a place in print work
Print files are still defined in CMYK, but the rest of a project often lives on screen. Designers send proofs to clients over email, paste swatches into chat threads, drop color chips into a website mockup, and build social tiles in sRGB. Each of those steps needs an RGB value to represent the ink recipe, and getting one from the printer on the spot is rarely practical when a deadline is close.
A print-side preview workflow bridges that gap. Before plates are burned or the PDF is uploaded to the press, you can copy the four CMYK percentages from your layout, move the sliders in the browser tool to those values, and read the corresponding RGB channels, hex code, and visual swatch. The result is enough to align expectations with a client, sanity-check a brand color that has drifted through a layout change, or build a landing page that visually echoes the printed piece.
The key habit is to treat the RGB output as a screen-only artifact. The CMYK values that produced it stay authoritative for the press file. Anything that ends up printed still gets sent as CMYK with the printer's profile attached — the RGB is a stand-in for human communication and web previews, not a substitute for color-managed production.
How to preview CMYK inks as RGB on screen
- Open the CMYK to RGB tool in your browser. No upload, login, or installation is needed — the calculation runs locally on your device.
- Set the cyan, magenta, yellow, and black sliders to match the percentages from your print file or color book. Each value runs from zero to one hundred percent.
- Read the updated 8-bit red, green, and blue channels, the six-digit hexadecimal value, and the live swatch on the page. Adjust any slider and the readouts refresh immediately.
- Copy the RGB triplet or hex code into your screen mockup, presentation, or chat thread. Save the original CMYK percentages separately so the press file is never overwritten.
- For any color that will appear in a printed piece, ask your printer for the correct output ICC profile and run a calibrated, profile-aware workflow instead of trusting the browser preview alone.
The formula the browser tool uses
The conversion follows the naive device-CMYK fallback published in the W3C CSS Color 4 specification (W3C device-CMYK naive conversion). Each ink percentage is normalized to a value between zero and one. Each display channel is then computed as one minus the smaller of one and the quantity (colorInk × (1 − black) + black). The result is multiplied by 255 and rounded to an integer using half-even tie rounding so the output matches the W3C firebrick reference case and the product's independent fixtures for primary endpoints.
Worked example with cyan 40%, magenta 90%, yellow 100%, black 10%:
- Normalize the inputs: 0.4, 0.9, 1.0, 0.1.
- Red: 1 − min(1, 0.4 × 0.9 + 0.1) = 1 − 0.46 = 0.54 → 0.54 × 255 = 137.7 → 138.
- Green: 1 − min(1, 0.9 × 0.9 + 0.1) = 1 − 0.91 = 0.09 → 0.09 × 255 = 22.95 → 23.
- Blue: 1 − min(1, 1.0 × 0.9 + 0.1) = 1 − 1.0 = 0 → 0.
The tool returns RGB (138, 23, 0), a warm burnt-orange swatch and hex #8A1700. Substituting any other recipe in the same way produces the screen RGB and hex the page displays.
Where the screen approximation breaks down
Real print output is shaped by factors the browser preview cannot see. The press's ink set, the paper's brightness and coating, dot gain on the plate, the rendering intent (perceptual, relative colorimetric, absolute colorimetric, or saturation), and the embedded ICC profile can all move a printed color noticeably away from its RGB preview. Two printers using the same recipe on uncoated versus coated stock can land on visibly different blues; the W3C naive formula returns the same number for both because it has no signal to tell them apart.
The endpoints the formula does predict behave predictably, and they are useful when you want to confirm that a recipe has been entered the right way around. The table below lists the canonical inputs the W3C specification documents, paired with the RGB and hex values the tool returns.
| CMYK input | Computed RGB | Hex | Reads as |
|---|---|---|---|
| 0 / 0 / 0 / 0 | 255 / 255 / 255 | #FFFFFF | White (paper) |
| 100 / 0 / 0 / 0 | 0 / 255 / 255 | #00FFFF | Cyan |
| 0 / 100 / 0 / 0 | 255 / 0 / 255 | #FF00FF | Magenta |
| 0 / 0 / 100 / 0 | 255 / 255 / 0 | #FFFF00 | Yellow |
| 0 / 100 / 100 / 0 | 255 / 0 / 0 | #FF0000 | Red (M + Y) |
| 0 / 0 / 0 / 100 | 0 / 0 / 0 | #000000 | Black |
Off those endpoints, the gap between the screen preview and the actual print widens. A deep navy built from 100% cyan, 100% magenta, 50% yellow, and 60% black looks one way on an sRGB monitor and quite another on a coated sheet under a 5000 K viewing booth — both readings are legitimate for their own context, but they are not the same color, and only the profile-aware workflow catches the difference before plates are made.
Putting the preview to work in a print workflow
The fastest path through the tool is copy and paste. Open your layout or color spec, copy the four CMYK percentages, set the sliders to match, and read off the RGB and hex. The browser does the arithmetic locally, so nothing is uploaded and you can iterate freely across many swatches in a sitting.
A few habits make the workflow safer for everyone on the team:
- Keep the original CMYK recipe next to any RGB you pull from the tool. The CMYK stays the source of truth for the press file; the RGB exists only for screen contexts and stakeholder communication.
- Write the hex code into a style guide, a chat message, or a Figma frame so the print color is communicable to teammates who never see the plates or the Pantone book.
- When the printed color needs to match across substrates, skip the naive preview entirely and use profile-aware software with a calibrated display. The browser tool is for quick alignment, not contract color.
- Confirm the printer's output profile before sending files, and run a physical proof on the actual stock. Paper and ink choice routinely push a CMYK recipe away from any screen value, and only a hard proof catches that gap.
For a deeper look at the print-versus-screen decision itself, the Lizely guide Should You Use CMYK or RGB for Print Projects walks through when CMYK is mandatory and when RGB is fine. Used together, that guide plus the CMYK to RGB tool cover both the strategic call and the daily previews that keep a print project aligned with everyone who reviews it on a screen.
Related reading: Color Palette Generator From a Color Name: A Workflow.