CMYK vs. RGB:
Why They Don’t Match.

Two different ways of making a color

RGB is additive color: a screen is a grid of red, green and blue lights, off by default, and every color you see is those three lights adding up. Stack red, green and blue at full intensity and you get white, because you are adding more light. CMYK is subtractive: cyan, magenta, yellow and black inks sit on white paper and absorb (subtract) some of the light hitting them, and you see whatever wavelengths bounce back. Stack all four inks and you approach black, because you are removing light rather than adding it.

Why RGB looks brighter

A backlit screen is a light source; a printed sheet is not — it depends entirely on ambient light reflecting off it. And the two systems simply cannot reach the same colors: RGB’s gamut, especially in saturated blues, greens and neon tones, is wider than what four process inks on paper can physically reproduce. That bright screen blue or neon green in your file is very likely a color no combination of cyan, magenta, yellow and black ink can print. There is no setting that fixes this — it is a hard limit of what reflected ink can do compared to emitted light.

What happens when a file converts

When an RGB file converts to CMYK — whether you do it deliberately in your design software or it happens automatically on the way to a press — every color is mapped through a color profile to the nearest color CMYK can actually produce. Colors already inside the CMYK gamut barely move. Colors outside it get pulled, or clipped, to the closest reproducible equivalent, and that shift is one-directional: converting back to RGB afterward does not recover what was lost. Building a file in CMYK from the start, rather than converting at the last minute, gives you an accurate preview of the shift instead of a surprise at proof stage.

Paper is not neutral white, either

The stock itself has its own tint, texture and brightness, all of which shift how ink sits on it and how the eye reads the resulting color. The same CMYK values print visibly differently on a bright white coated sheet versus a warmer uncoated one.

What a proof actually settles

A soft proof — the PDF on your screen — is useful for checking everything objectively right or wrong: text, layout, image placement, page order. It is not a color proof, because you are looking at a backlit, additive display that no printed sheet can match, however carefully the monitor is calibrated. A hard-copy proof, printed on the actual (or a representative) stock and viewed under consistent light, is what actually shows how the CMYK conversion and that specific paper will render together. See what to check on a print proof for how to read one, and prepress for how a file gets to that stage in the first place.

What this means for a file headed to press

• Build or convert to CMYK before you finalize a file, not after.
• Do not judge final color from a monitor, even a good one.
• Name any color that has to hold exactly by its Pantone number, so it prints as a spot ink rather than a CMYK approximation — see spot color vs. process color.
• If a color is genuinely critical, ask for a hard-copy proof rather than approving from a screen. The same conversion happens whether a job runs digital or offset — the gamut limit is a property of ink on paper, not of any one press.