Why screen colour does not match the printed sheet

Why does the same file look different on screen and on paper?

A monitor is a light source: it makes colour by emitting red, green and blue light directly into your eye, and it can produce bright, saturated colours - vivid blues and greens in particular - that a printed sheet has no way to reproduce. A printed sheet makes colour by reflecting ambient light off ink laid on a substrate, usually built from cyan, magenta, yellow and black (CMYK) or named spot inks. These are two different physical processes with two different gamuts - the full range of colours each can produce - and the printed gamut is smaller and a different shape than the screen's. No amount of calibration turns one into the other; colour management exists to make the relationship between them predictable, not to erase it.

This guide is written for anyone specifying, building or buying a web-to-print editor or storefront where customers see a design on screen before it is printed, and need to understand what will and will not carry over.

What is an ICC profile, and what does it actually store?

An ICC profile is a data file that describes how one specific device - a monitor, a scanner, a printer and substrate combination - relates colour values to a standard, device-independent reference space called the Profile Connection Space (PCS). A monitor's profile says what RGB values that particular screen produces as actual colour; a printer's profile (often substrate-specific, because the same ink looks different on coated and uncoated stock) says what CMYK or spot-ink values produce as actual colour on that paper. Colour management software uses both profiles together to convert an image from how it looks on your screen to how it will look coming off that specific printer and stock, rather than applying one generic conversion to every printer.

Because a profile is tied to a specific device and substrate, a profile built for one printer and paper does not describe a different printer or a different paper accurately. A web-to-print workflow that only ever uses generic default conversion settings is accepting whatever approximation its software ships with, not a conversion tuned to its own output.

Which rendering intent should a web-to-print workflow use?

A rendering intent is the rule for what happens to colours that exist in the source image's gamut but not in the destination's smaller one - which is nearly every colourful photograph going from screen to a printed sheet. Two intents cover almost every print production case.

Perceptual intent compresses the whole image's colour range into the destination gamut, preserving the visual relationships between colours - a sky that was brighter than a nearby colour on screen is still brighter after conversion, even though both shifted. This suits photographs, where a viewer judges the image as a whole rather than any one colour value.

Relative colorimetric intent maps the source's white point to the destination's white point and reproduces in-gamut colours as accurately as possible, but clips out-of-gamut colours to the nearest reproducible value rather than compressing the whole range. This suits logos, brand colours and flat graphic elements, where getting the colours that can be matched exactly right matters more than preserving the relationship with colours that cannot be matched at all.

Saturation and absolute colorimetric intents exist for specific cases - business graphics and press-to-press proofing checks, respectively - that a general web-to-print storefront rarely needs to expose as a customer-facing choice.

What is soft proofing, and when does it help?

Soft proofing simulates a printed result on a calibrated monitor, using the destination printer and substrate's ICC profile to show approximately how the colours will shift before anything is printed. It narrows the gap between expectation and result because the designer sees a closer approximation of the printed outcome while still working on screen, rather than discovering the shift only on a physical proof.

Soft proofing has two real limits. It still shows the simulation on a monitor's own gamut, which cannot display certain printed effects - metallic or fluorescent inks, for instance - accurately at all. And it depends entirely on the monitor being properly calibrated and the destination profile being accurate for the actual printer and stock in use; a soft proof run against the wrong profile is worse than no soft proof, because it creates false confidence. For a job where exact colour matters - a brand's primary colour on a flagship product - a physical proof on the actual production stock remains the only check that resolves every variable soft proofing cannot.

How should a storefront's editor handle screen-to-print colour expectations?

A web-to-print design editor sits between a customer who sees only a screen and a press that will reproduce a physically different gamut, and the honest approach is to say so rather than imply equivalence. Three practical steps help:

1. Convert early and consistently. Apply the destination printer's ICC profile and chosen rendering intent during the design or proofing step, not only at the final output stage, so what the customer approves is closer to what will print.
2. Flag out-of-gamut colours. Warn when a chosen colour - particularly a bright RGB blue or green - falls well outside the CMYK gamut, so a customer can adjust a brand colour before committing to print rather than being surprised afterward.
3. State the limitation plainly. A line near the preview that colour may shift from screen to print, with no overstated promise of an exact match, sets the expectation the physical medium actually allows.

CMYK and spot colour in a web-to-print pipeline covers the conversion and spot-colour handling this guide assumes; print-ready PDF and prepress automation covers building the pipeline that applies profiles and intents consistently through to the output file. Where a job also needs its pages laid out for press, imposition and ganging covers that separate decision.

Live stores that already run profile-aware editors in production are catalogued on the live web-to-print stores evidence page.

Turn this into a scoped brief

If your storefront needs profile-aware conversion, out-of-gamut warnings or soft-proofing in its editor, send a project brief naming your typical product line, the substrate or substrates involved, and one file where the printed result has surprised a customer before.

Limitations

This guide describes colour management concepts generally; it does not state that identical on-screen and printed colour is achievable, because it is not. Where a technical standard is named, it describes the output specification an engagement produces to, not a credential Web2Print Solutions holds. Web2Print Solutions is the web-to-print engineering service of Netbase JSC. Delivery records cited on this site belong to Netbase JSC; where no delivered example of a capability is published, the page says so rather than implying a record. It does not cover monitor hardware calibration procedures, which are a display-technology topic on their own.