PicaJet
Search Build shortlist

Reference Formats

ICC Profile

An ICC profile is a standardized data file that describes the color characteristics of a device, document, or color space, allowing color-managed software to translate colors accurately between them.

Extension

.icc

Full name

International Color Consortium Profile

Introduced

1993 (ICC founded); the ICC profile format specification followed shortly after and is now standardized as ISO 15076-1

Vendor

International Color Consortium

What is inside the container

The file contains a header describing the profile class (input, output, display, or device link) and connection space, followed by a set of tagged data elements such as tone reproduction curves and color transform tables (matrix/TRC or lookup-table based) that map device color values to a device-independent profile connection space (PCS). Profiles can be embedded directly inside image files (TIFF, JPEG, PSD, PDF) or kept as standalone .icc/.icm files referenced by an application's color settings.

How to open it

Mac ColorSync Utility (view/inspect installed and embedded profiles)
Windows Windows Color Management control panel
Windows/Mac Adobe Photoshop / Bridge (assign, convert, and embed profiles)
Windows/Mac/Linux ArgyllCMS (open-source profiling and inspection tools)

For archives

Embed the ICC profile directly inside master image files rather than only keeping it as a separately referenced file, since an image without its profile embedded becomes ambiguous the moment it moves outside its original color-managed environment. Track whether a profile is ICC v2 or v4, as the two versions are not always interpreted identically across applications. For device or press profiles used repeatedly across a production workflow, catalog them as reusable reference assets tied to the specific device, paper, or output condition they were built for.

The International Color Consortium was formed in 1993 by eight companies — Adobe, Agfa, Apple, Kodak, Microsoft, Silicon Graphics, Sun Microsystems, and Taligent — to build a vendor-neutral, cross-platform color management architecture, replacing the incompatible proprietary color systems each company had been running separately. The result was the ICC profile specification, which has since been published as the international standard ISO 15076-1. The consortium has continued developing the format, including a version 4 revision and the newer iccMAX architecture that adds spectral color support.

  • Input — describes a capture device such as a scanner or camera
  • Display — describes a monitor’s color characteristics
  • Output — describes a printer, press, or other output device and substrate
  • DeviceLink — a direct transform between two specific devices, bypassing the profile connection space

ICC profiles are foundational infrastructure for any DAM handling print, photography, or design assets, because they are what make a color-managed pipeline possible at all — they let a DAM’s preview generator, a designer’s monitor, and a commercial printer agree on what a given set of numeric color values is supposed to look like. The most common DAM-level mistake is treating profile embedding as optional: an sRGB or Adobe RGB image without its profile embedded will usually still display reasonably, but a CMYK asset without an embedded output profile is functionally ambiguous, since the same ink percentages can represent very different colors depending on the press condition assumed.

A second recurring issue is profile version mismatch: ICC v2 and v4 profiles are not always rendered identically by every application, which can cause visible color shifts when an asset moves between tools that default to different profile versions. DAM systems that manage device or press profiles as reusable assets — rather than leaving them buried inside individual image files — should record the exact device, substrate, or output condition each profile targets, since a profile with no context is not reliably reusable.

Frequently asked

Who founded the International Color Consortium and when?

The ICC was formed in 1993 by eight companies — Adobe, Agfa, Apple, Kodak, Microsoft, Silicon Graphics, Sun Microsystems, and Taligent — to build a vendor-neutral color management standard.

Should ICC profiles be embedded in images or kept as separate files in a DAM?

Embedding is the safer practice for master assets, since an image that travels outside the DAM without its embedded profile becomes ambiguous about what its color values are meant to represent.

What's the difference between ICC v2 and v4 profiles?

Both follow the same core ICC architecture, but v4 refined the transform and rendering-intent handling; the two versions are not always interpreted identically across applications, which can cause subtle color differences.

Is an ICC profile the same as a color space like sRGB?

Not exactly. sRGB is a defined color space, and the sRGB ICC profile is the specific file that encodes that color space's characteristics so color-managed software can use it; the profile is the machine-readable description, not the abstract space itself.

Why would a DAM catalog device or press ICC profiles as their own reusable assets?

Because a single output profile, such as one built for a specific printer and paper combination, gets reused across many production jobs, and cataloging it separately with its target device metadata makes it discoverable rather than buried inside past project files.

What happens if a CMYK image is missing its ICC profile?

The color becomes ambiguous, since raw CMYK ink percentages do not define an actual color without a profile specifying the ink set and press condition they were designed for; different applications will render it differently.

Is the ICC profile format an open standard?

Yes, it has been published as ISO 15076-1, an international standard, following its original development by the vendor-neutral International Color Consortium.

Do all image file formats support embedded ICC profiles?

Most production formats do, including TIFF, JPEG, PSD, and PDF, though the mechanism for storing the profile tag differs by format, which is one reason DAM ingest pipelines need format-specific handling to reliably read and preserve them.

Sources