rusty_icc: ICC Color Management Without LittleCMS
rusty_icc 0.1.1 is ICC color management in pure Rust: v2 and v4 profiles, LUT transforms and soft-proofing, within 0.03 ΔE2000 of LittleCMS.

What is rusty_icc and how close is it to LittleCMS?
rusty_icc is ICC color management in pure Rust with no dependencies. It parses and writes v2 and v4 profiles and converts RGB, CMYK, grey and Lab, landing within 0.03 ΔE2000 of LittleCMS's exact pipeline.
Every color on a screen went through a conversion first. A camera tags its photo with an ICC profile, a monitor has a profile of its own, and so does a printer. Color management is the math that maps one onto the next so red stays red. Most open-source software hands that math to LittleCMS (lcms2), a C library that parses whatever embedded profile it receives. rusty_icc does the same work in Rust, with forbid(unsafe_code), no C and no dependencies of any kind.
It reached crates.io on 20 November 2026 under Apache-2.0. Profiles in v2 and v4 are parsed and written, matrix-shaper and LUT transforms cover RGB, CMYK, grey and Lab, and results land within 0.03 ΔE2000 of LittleCMS's exact pipeline. The code is in the monorepo under crates/rusty_icc. For the public summary, see the Remade with Rust card; MATA's own notes sit on its landing page.
Trust is a family photo that looks right without a cloud service deciding what right means. Security is a profile parser that cannot be steered past its own tables. Incentive is a color engine with no dependency tree to audit.
Why a Color Profile Is Untrusted Input
An ICC profile is a binary file with a header, a tag table, curves and lookup tables, defined by the International Color Consortium. Profiles ride inside JPEGs, PNGs, TIFFs and PDFs, so any picture from a stranger can carry one. A color engine reads the tag offsets, curve lengths and table dimensions that file declares. In C, a profile that lies about a table size becomes an out-of-bounds read inside code that only meant to fix the colors.
The NIST Secure Software Development Framework asks for memory-safe languages exactly where software parses outside input. Here that parser has no unsafe blocks and pulls in no other crates, so the whole path from profile bytes to converted pixels is one crate a reviewer can read end to end.
The EFF has long argued that software handling personal files should be software people can inspect and run themselves. A photo library is personal, and its color engine should be too.
What rusty_icc Converts
The job has three parts: read the profiles, build a transform between them, and push pixels through it. All three are covered, plus the proofing tools print workflows expect. A photo viewer needs the first two to show a camera's colors correctly on a laptop. A print dialog needs everything, because paper, ink and screen each carry a profile, and the user wants to see the print before spending the paper.
v2 and v4 Profiles, Read and Written
Older photos and scanners embed ICC v2 profiles, while current software writes v4. Both versions parse and serialize here, so a program can pull the profile out of a file, inspect it, and write a new one without a second library. Writing matters for tools that tag their own output, such as an export dialog embedding sRGB.
Matrix-Shaper and LUT Transforms
Simple display profiles describe color with three curves and a matrix, the matrix-shaper model. Printer and creative profiles use lookup tables instead. Both kinds run here: matrix-shaper transforms, and LUT transforms with lut8, lut16, mAB and mBA tables. The covered spaces are RGB, CMYK, grey and Lab, spanning screens, printers, black-and-white scans and the device-independent space between them.
Intents, Black Point and Soft-Proofing
When a color will not fit the target device, the rendering intent decides what gives. All four intents are implemented, along with black-point compensation, which keeps shadows from crushing when one profile's darkest black differs from the other's. Soft-proofing previews on screen how a picture will print, and gamut checks flag colors a printer cannot reach.
How Close It Lands to LittleCMS
A replacement color engine has to be measured against the one it replaces: color error first, speed second.
Within 0.03 ΔE2000
ΔE2000 is the standard formula for how different two colors look to a person. The crate stays within 0.03 of LittleCMS's exact pipeline, far below the difference of about 1 that is commonly treated as just noticeable. A program can move engines without its users seeing a shift.
Where It Wins and Where LittleCMS Leads
Against its own first release, 0.1.1 cut clock time by 1% to 37% depending on the transform. Against LittleCMS it is 1.40× faster on 16-bit matrix-shaper transforms and 1.14× faster on Lab to sRGB in float. LittleCMS still leads on 8-bit paths. Its fixed-point arithmetic would change the output if copied, so the Rust engine keeps its accuracy instead. The speed field note has the instruction counts.
Pinning rusty_icc With Its Siblings
cargo add rusty_icc adds it to a project. Released the same day were rusty_tiff, whose decoder exposes a TIFF's ICC tag, and rusty_image for the small formats. Photos on a Home Computer, the ones you stopped renting from a cloud, are where this engine earns its keep. rusty_png and rusty_jpeg and the rest of the family are listed on MATA's Remade with Rust page.
FAQ
Short answers already in this article.
Which ICC profile versions does rusty_icc read and write?
rusty_icc parses and writes both ICC v2 and v4 profiles, so it handles the older profiles still embedded in many photos and the newer ones current software writes.
Which color transforms does rusty_icc support?
Matrix-shaper transforms and LUT transforms using lut8, lut16, mAB and mBA tables, for RGB, CMYK, grey and Lab. On top of those it offers four rendering intents, black-point compensation, soft-proofing and gamut checks.
Is rusty_icc faster than LittleCMS?
On some paths. rusty_icc is 1.40 times faster on 16-bit matrix-shaper transforms and 1.14 times faster on Lab to sRGB in float. LittleCMS still leads on 8-bit paths, because copying its fixed-point arithmetic would change rusty_icc's output.
Does rusty_icc pull in any other crates?
No. rusty_icc has no dependencies, uses no C and no unsafe code, and is published under Apache-2.0 as version 0.1.1 on crates.io.
What does soft-proofing in rusty_icc let a program do?
Soft-proofing simulates on screen how an image will look on another device, such as a printer, using that device's ICC profile. With gamut checks, rusty_icc can flag colors the target cannot reproduce.

