CMYK vs RGB in PDF: Why Screen Colours Never Print the Same

A monitor and a sheet of paper produce colour by opposite methods, and almost every printing disappointment traces back to that fact. A screen is an additive system: each pixel emits red, green and blue light, and stacking all three at full strength gives white. Ink is subtractive: paper reflects the light in the room, and each layer of cyan, magenta, yellow or black absorbs part of that light so that what bounces back to your eye is what remains. One system starts from darkness and adds energy; the other starts from a white sheet and takes energy away. They can never have identical limits.

Those limits are called the gamut, the set of colours a device can actually reproduce. The two gamuts overlap generously in the middle, which is why most photographs survive the journey to paper without drama. They diverge at the edges. Saturated blues, electric greens and pure oranges are easy for glowing phosphors and very hard for four semi-transparent inks on absorbent stock. When a colour lies outside the printer's gamut, the conversion has to map it to the nearest reachable colour, and nearest usually means duller. Nothing failed; the ink simply cannot emit light.

Inside a PDF, colour is described by a colour space attached to each drawing operation. DeviceRGB, DeviceGray and DeviceCMYK are the simple device-dependent spaces, while ICCBased spaces attach a profile that tells a colour managed workflow precisely what those numbers mean. A single file can mix them freely, which is common when a design tool exports CMYK artwork containing an RGB photograph. If nobody converts deliberately, the conversion still happens, just later and with default assumptions, usually at the printer's raster image processor where you have no say in the result.

The realistic way to manage expectations is to stop judging print colour on a backlit screen. Ask your print provider which profile and stock they use, request a proof for anything colour critical, and remember that heavy solid areas behave differently from light tints. Deep blacks are a classic surprise: large fields printed with black ink alone often look washed out compared with the black you saw on screen, which is why prepress people build richer blacks from multiple inks. None of this is exotic knowledge, but it has to happen before the file goes out, not after the invoice arrives.

What this means for everyday work: treat a print run as a conversation with a printer rather than a file upload. PdfWill deliberately does not pretend to be a prepress system, so if a job needs a specific CMYK profile, that belongs in your design tool or with your printer. What it can do locally in your browser is prepare the practical cases around it, such as running grayscale when a document is destined for cheap black-and-white output, using PDF to Image when you need screen-accurate RGB previews to share, and keeping every one of those files off the internet while you work.