--- title: "RGB vs CMYK: Which Color Mode Should You Use?" description: "A screen adds light; a press subtracts ink. Those two sentences explain why a vivid green returns as olive, what each mode is for, and why CMYK resists screen judgement." canonical: "https://freeaigeneration.com/en/guides/rgb-vs-cmyk-which-color-mode-should-you-use/" robots: "noindex" lang: "en" --- # RGB vs CMYK: Which Color Mode Should You Use? A screen makes colour by adding light. A press makes colour by subtracting ink. Almost everything that confuses people about RGB vs CMYK follows from those two sentences, including the reason a vivid green on your monitor can come back from the printer looking like olive. The screen is not lying. It is showing you a colour that exists in light. The press has a different set of raw materials, and some of what you see simply has no ink equivalent. ## Additive light, subtracted ink RGB is three channels of light — red, green and blue. Full values on all three make white, zero makes black, and everything else is a mix. That is how an LCD or an OLED panel works. CMYK is four inks — cyan, magenta, yellow and black. Each ink removes part of the white paper's reflection. Cyan over yellow makes green because the inks are filtering what bounces back. The reason black gets its own plate is density: the three chromatic inks overprinted make a muddy dark brown, not a solid black, so K carries the text and the shadows. The practical consequence is asymmetry. A light source reaches saturated hues at high intensity; inks are limited by pigment chemistry and by how much ink paper will absorb. ## The count that misleads Eight bits per channel gives RGB 256 × 256 × 256 = 16,777,216 combinations. Give CMYK four channels and the arithmetic looks generous: 256 × 256 × 256 × 256 = 4,294,967,296. That number is the most common trap in the subject. More combinations do not mean more colours. CMYK's four axes describe how much of four specific inks lands on paper, so a vast number of those combinations map to small, overlapping steps inside a smaller reachable volume. RGB can describe colours that no ink combination reaches at all — saturated greens, oranges and electric blues are the usual casualties. The size arithmetic is simpler. Eight-bit RGB is 3 bytes per pixel and CMYK is 4, which matters for memory rather than quality. A4 at 300 ppi is 2,480 × 3,508 px, or 8,699,840 pixels: 26.1 MB as RGB and 34.8 MB as CMYK before any compression. ## What each mode is actually for For anything on screen, sRGB (standardised as IEC 61966-2-1) is the working space to assume. It is what browsers and phone cameras expect, and using the wrong profile shifts every colour in the file at once — a quietly wrong result rather than an obvious failure. For commercial printing, CMYK is the mode the printer's workflow expects, converted through the profile they name. Spot colours sit outside that model. They are premixed inks printed in addition to CMYK, used when a brand colour has to be exact or when a fluorescent or metallic effect is wanted. The PDF standards make the difference visible. PDF/X-1a flattens to CMYK, while PDF/X-4 keeps ICC colour and live transparency. Which one a printer wants is a question about their press and their prepress software, not about your taste. ## Where these browser editors sit Both of the editors involved here work on screen data. A browser canvas is 8-bit RGBA, so compositing, blending and previewing all happen in RGB, whatever the final destination. That sets a clear boundary. The [Photo Editor](/en/tools/photo-editor/) bundles a CMYK ICC profile, but a bundled profile is not CMYK output, and no CMYK, 16-bit or ICC output claim is supported for it. The [Page Layout Editor](/en/tools/page-layout-editor/) has no colour-managed output evidence either. Converting to CMYK is a job for the printer's prepress stage or for an application built to do it, and it should happen once, late, with the profile the printer supplies. ## A CMYK file cannot be judged on screen Two things follow from using an RGB display to look at print colour. The first is that the screen must convert CMYK back into light to show it at all, so what you see is a simulation built on an assumed profile and an uncalibrated panel in most cases. The second is that the conversion itself is not reversible. Once tones have been squeezed into the ink gamut, converting back does not restore what was lost; it produces a new approximation that looks close and is not the same file. Soft proofing exists for this reason in print-oriented software, and it is a proxy rather than a guarantee. If colour accuracy matters for a brand or a product shot, the proof from the printer is the artefact to approve. ## Which mode to choose If the destination is a screen, stay in RGB and set sRGB as the profile. If the destination is a press, ask the printer for the CMYK profile and the PDF standard before you start, not after the file is finished. If a job goes both ways, treat those as two exports from one source rather than one file asked to do both. Choosing is the easy part. The hard part is accepting that a colour you can see on a monitor may be a colour you cannot print, and dealing with that during design rather than in a proof email. The handoff sequence itself is covered in [preparing a print-ready PDF](/en/guides/how-to-prepare-a-print-ready-pdf/), and [DPI versus PPI](/en/guides/dpi-vs-ppi-whats-the-difference/) covers the other half of the same print arithmetic. More material sits in the [guides hub](/en/guides/).