Workflow 9 min read 17 October 2026

PDF Colour Spaces: DeviceRGB, CMYK, ICC, and Lab Explained

PDF supports a rich palette of colour spaces — from device-dependent DeviceRGB and DeviceCMYK to device-independent ICC-based, Lab, and special-purpose spaces like Separation and DeviceN. This guide explains when each colour space is appropriate, how colour management affects PDF/X and PDF/A compliance, and how to avoid common colour conversion pitfalls.

Colour in PDF is not a single concept — it is a system of colour spaces, each with different device dependencies, gamut characteristics, and use cases. Getting colour spaces wrong in a PDF leads to colour shifts in print, failed PDF/X validation, and unpredictable appearance across viewing environments. This guide covers all the colour spaces defined in ISO 32000, when to use each, how colour management interacts with them, and the specific requirements of PDF/X and PDF/A for colour handling.

Device-dependent colour spaces

Device-dependent colour spaces interpret colour values relative to an assumed output device with no profile: DeviceRGB — Three-component (red, green, blue) values from 0.0 to 1.0. DeviceRGB is interpreted as the viewer's or printer's native RGB colour space, which varies by device. For screen-only documents where colour precision is not critical, DeviceRGB is convenient. For print production or colour-managed workflows, DeviceRGB is problematic because the viewer/RIP makes assumptions about what "DeviceRGB" means. DeviceCMYK — Four-component (cyan, magenta, yellow, black) values from 0.0 to 1.0. DeviceCMYK is interpreted as 100% ink values on the output device with no profile conversion. For print workflows, DeviceCMYK values are often passed straight through to the press without colour management — which is either exactly what you want (precise ink specification) or a problem (different presses have different dot gain characteristics). DeviceGray — Single-component greyscale from 0.0 (black) to 1.0 (white). No colour management implications. Used for purely greyscale content. When device spaces cause problems: - DeviceRGB content in a PDF sent to a CMYK press will be converted using whatever colour conversion the RIP applies — not under document author control. - DeviceCMYK content viewed on screen will be converted using the viewer's assumed CMYK profile — typically US Web Coated SWOP — which may not match the intended printing condition. - Mixing DeviceRGB and DeviceCMYK in the same PDF (mixed colour space) causes complexity in RIP processing and can produce unexpected results in transparency compositing.

Device-independent colour spaces

Device-independent colour spaces define colour relative to human perception (via the CIE XYZ colour model) rather than device characteristics. They require a colour management engine to convert values to device output. ICCBased — A colour space defined by an embedded ICC profile. ICCBased/RGB and ICCBased/CMYK are the device-independent equivalents of DeviceRGB/DeviceCMYK. The ICC profile defines the exact colour behaviour, enabling accurate colour management across devices. This is what you get when you use sRGB or Adobe RGB or FOGRA51 CMYK as your document colour space. Output intents in PDF/X and PDF/A are ICC profiles carried in the OutputIntents array. CalRGB and CalGray — Calibrated RGB and grey spaces defined by chromatic adaptation parameters rather than a full ICC profile. CalRGB with sRGB primaries and a D65 white point is a lightweight alternative to an embedded ICC profile for sRGB-encoded content. Rarely used directly — ICC-based spaces are preferred. Lab (CIE L*a*b*) — A perceptually uniform colour space where equal numerical distances correspond approximately to equal perceptual differences. L* is lightness (0=black, 100=white), a* is green–red axis, b* is blue–yellow axis. Lab is used in PDF for calibrated colour specification and is the connection space used internally by ICC colour management. Useful for specifying colours precisely without reference to a device. Using device-independent spaces in practice: In a document that will be colour-managed end-to-end, use ICCBased colour spaces. For PDF/X print submission, the output intent ICC profile and the image colour profiles handle the mapping. For PDF/A archiving, including ICCBased colour content with an output intent ensures the document's intended appearance is captured in the archive.

Special-purpose colour spaces

PDF also supports several special-purpose colour spaces for specific production needs: Separation colour space — Represents a single colorant (ink), identified by name. [/Separation /PANTONE-485-C /DeviceCMYK alternateFunction] defines a Pantone spot colour with a CMYK fallback for devices that don't support the spot colour. Used in commercial printing for spot colour inks (Pantone, Hexachrome) and for varnish and foil overlays. Separation spaces are critical for packaging and label printing. DeviceN colour space — A generalisation of Separation to multiple named colorants simultaneously. [/DeviceN [/Cyan /Magenta /PANTONE-485-C] /DeviceCMYK alternateFunction] allows process colours and spot colours to be specified together. Used in high-end prepress for multi-colorant output. Indexed colour space — A colour lookup table: colour values in the content stream are integers indexing into a colour table. [/Indexed /DeviceRGB 255 colourTableBytes]. Used for indexed images (GIF-style palettized images). Reduces precision but can be memory-efficient for images with few distinct colours. Pattern colour space — Used to apply patterns (tiling or shading) as paint. Tiling patterns repeat a defined cell; shading patterns apply gradient fills. Not a "colour" in the traditional sense but listed as a colour space in ISO 32000. PDF/X and spot colours — PDF/X-1a prohibits spot colours unless they have CMYK fallback values defined. PDF/X-4 allows spot colours with the expectation that the print workflow will handle spot colour separation. Always confirm with your print supplier whether spot colours are expected in the PDF or should be converted to process CMYK.

Colour management in PDF workflows

Colour management in a PDF workflow involves three stages: Source profile — Each image or coloured element in the PDF has an associated colour space. For ICCBased spaces, the embedded profile is the source. For device spaces (DeviceRGB/DeviceCMYK), the rendering application assumes a default source profile (typically sRGB for DeviceRGB, and a press standard for DeviceCMYK). Connection space — The colour management system converts from source profile to the profile connection space (PCS, which is CIE XYZ or Lab) as an intermediate step. Destination profile — The output intent or the output device profile defines where colours land in the final output. For a PDF being printed on a specific press, the press characterisation data (e.g., FOGRA51 for European coated offset) is the destination profile. Common problems: - Colour shift between screen and print: Usually caused by DeviceRGB screen images being sent to a CMYK press without controlled conversion. Fix: use ICCBased sRGB images with a PDF/X output intent to the target printing condition. - Saturated colours printing muddy: Out-of-gamut colours being gamut-mapped without care. Check the rendering intent (Perceptual, Relative Colorimetric, Saturation, Absolute Colorimetric) in the PDF's transfer function or in the RIP's colour settings. - PDF/X validation failure: Content using device spaces without an output intent. Fix: embed an output intent matching your target printing condition, and use ICCBased or device spaces consistently.

Frequently asked questions

Should I use sRGB or Adobe RGB for images in a PDF?

For most PDF workflows, sRGB is the practical choice: it is the standard for web content, screen display, and many consumer devices, and it is widely understood by PDF viewers and printing systems. Adobe RGB has a wider gamut (particularly in the green–cyan range) and is preferred by photographers and print professionals who want to preserve maximum colour information through an ICC-managed print workflow. If your PDF is going to a colour-managed print workflow that can handle Adobe RGB, use Adobe RGB — you retain more of the image's tonal range. If your PDF is primarily for screen viewing or you are unsure of the destination, sRGB is safer. Always embed the ICC profile (use ICCBased colour space) rather than leaving images as untagged DeviceRGB — the profile makes the colour intent explicit.

What is the difference between DeviceCMYK and an ICC-based CMYK colour space?

DeviceCMYK tells the output device to use the ink values directly, with no colour management interpretation — the device handles the conversion from ink percentages to actual colour on the substrate using its own internal characterisation. An ICC-based CMYK space (ICCBased with a CMYK ICC profile) specifies the CMYK values relative to a named printing condition described by the ICC profile. Colour management can then convert to any other device accurately. For print production work, ICC-based CMYK with an appropriate output intent (e.g., FOGRA51 for European coated printing) gives controlled, predictable results across different output devices. DeviceCMYK is appropriate when you explicitly want pass-through of ink values to the press with no managed conversion, and your press and the document were characterised together.

What colour spaces are required for PDF/X compliance?

PDF/X requirements for colour spaces vary by version. PDF/X-1a: all colour must be DeviceCMYK, DeviceGray, or a named spot colour with CMYK alternate. No RGB, no ICCBased — this is a CMYK-only standard for offset print. PDF/X-3 and PDF/X-4: allow device-independent ICCBased colour spaces as well as device-dependent CMYK and grey, but require an output intent ICC profile to define how DeviceCMYK (if used) should be interpreted. PDF/X-4 additionally allows RGB images with ICC profiles and live transparency. For all PDF/X variants, an /OutputIntents array entry with the appropriate /S (GTS_PDFX) and an embedded /DestOutputProfile ICC profile is mandatory if the document contains CMYK or spot colour content.

How do I check what colour spaces a PDF uses?

Several tools can audit colour spaces in a PDF: (1) Adobe Acrobat Pro: Print Production > Output Preview shows the colour spaces of all objects on each page; you can toggle visibility by colour space type to identify mixed-space content. The Ink Manager shows all colorants. (2) Acrobat Pro Preflight: run a PDF/X or PDF/A preflight profile — it reports colour space violations. (3) Ghostscript's gs -dBATCH -dNOPAUSE -sDEVICE=pdfinfo can extract some colour information. (4) pdfimages (part of Poppler): lists all images in a PDF with their colour space and encoding. (5) For programmatic auditing across large document libraries, PyMuPDF's page.get_images() returns colour space information for each image object.

Try it yourself

Everything in this article can be done directly in the free PDFTheGuide editor — no account required.

Edit PDF Add image to PDF Compress PDF Open editor