What is an ICC profile?

An ICC profile is a binary file that describes how a device or color space reproduces color. It contains a fixed 128-byte header, a tag table, and tagged data such as white-point XYZ values and per-channel tone curves used for color management.

Which tags are decoded?

The tool decodes text tags (desc, cprt) including text, desc, and mluc types; XYZ tags (wtpt, bkpt, rXYZ, gXYZ, bXYZ, lumi) as floating-point tristimulus values; and tone-reproduction curves (rTRC, gTRC, bTRC) including single-gamma curv types. Other tags are listed with their data type, offset, and size.

How are XYZ values represented?

ICC XYZ numbers are stored as s15Fixed16 (signed 16.16 fixed point). The tool converts each to a regular decimal by dividing the 32-bit integer by 65536, so the white-point and primaries appear as readable floats.

Why does it check for acsp?

Every valid ICC profile contains the ASCII signature acsp at byte offset 36. The tool checks for it before parsing so it can give a clear error instead of producing garbage from a non-profile file.

Is my profile uploaded?

No. Reading and decoding happen entirely in your browser using the FileReader API. The profile binary never leaves your device.

ICC Profile to JSON Converter

The ICC Profile to JSON Converter opens the binary internals of an ICC or ICM color profile and turns them into clean, readable JSON. It is useful for color engineers, print and photography workflows, and anyone debugging color management who needs to see exactly what a profile claims about a device.

How it works

An ICC profile follows the ICC.1 specification with a rigid binary layout, which makes it fully parseable in the browser:

Header (bytes 0–127). Fixed-position fields including profile size, CMM type, version, device class, color space, profile connection space (PCS), creation date, the acsp signature, platform, manufacturer, model, and rendering intent. Multi-byte numbers are big-endian.
Tag table (from byte 128). A 4-byte count followed by 12-byte entries — each a 4-character signature, a byte offset, and a size pointing into the tag data.
Tag data. The tool decodes the common tag types it finds.

Decoded tag types

Text — text, desc (textDescription), and mluc (multiLocalizedUnicode, UTF-16BE) are read as strings, used for the profile description and copyright.
XYZ — stored as s15Fixed16 fixed-point and converted to decimals by dividing by 65536, giving the white point, black point, and RGB primaries.
Curves — curv tone-reproduction curves report a single gamma value or a point count; para parametric curves are flagged by type.

Tags the tool doesn’t specifically decode are still listed with their data type, offset, and size so nothing is hidden.

Notes and tips

The decoder validates the acsp signature at byte 36 before doing any work, so a non-profile file produces a clear error rather than nonsense. Because parsing is purely structural and runs locally, it is fast and safe for proprietary or custom-built profiles. Use the JSON output to document a profile, diff two profiles, or feed profile metadata into your own color-management tooling.