ICC Profile Inspector
Drop an .icc or .icm file onto the page to read its description, device class, color space, PCS, version, creation date, default rendering intent, white point and copyright. Parsing happens entirely in your browser; the file is never uploaded.
Updated 2026-08-12 · Method version v1.0.0
How to Use
- Click Choose ICC profile (.icc/.icm) to load the file you want to check
- The file is parsed only in your browser and never uploaded, safe even for confidential color files
- Once parsed, read Description, Device class and Color space top to bottom to identify the profile
- Compare White point (XYZ) and Default rendering intent against what your printer actually specifies
Method & Assumptions
The printer sends over a color profile whose filename says coated. Is it actually an output-class profile, v2 or v4, and may it be forwarded to a partner? All of that is written inside the file; there is just no everyday tool to read it.
The inspector parses the 128-byte header and tag table per the ICC.1 specification: device class (display, output, input, DeviceLink), data color space and PCS, spec version, creation date, default rendering intent, and the media white point (wtpt tag).
The description (desc) and copyright (cprt) tags are read from both the legacy text encoding and the modern multilingual mluc encoding. In practice, many profiles that look broken are just a different generation of encoding, and read fine once parsed accordingly.
Parsing happens entirely in the browser; the file is never uploaded and touches no server. That is more than a privacy nicety: most standard press-condition profiles carry license terms restricting redistribution, and local parsing means inspecting a file never moves it off your machine.
Three prepress uses come up constantly: confirming a printer-supplied profile is CMYK output class rather than a display profile, reading the cprt terms before forwarding, and comparing creation dates of two same-named profiles to catch generation gaps. Same-name-different-generation is a real hazard: coated-stock characterizations in the FOGRA39 lineage and the FOGRA51 lineage describe different paper generations and measurement conditions, and are not interchangeable.
The inspector reads metadata; it does not compute gamut. To explore gamut and soft proofing, load the same profile into the ICC mode of our RGB-CMYK converter. And whether a profile still matches the current state of the press is something only fresh measurement at the printer can establish, beyond what any inspector sees.
Use Cases
- Handoff debugging: the client file embeds a profile with the same name as the shop's but a different date; both are inspected and the version and date fields settle which is which
- License check: before a profile is forwarded to a partner shop, the cprt terms are read to confirm redistribution is allowed
- Procurement sanity: a downloaded 'print' profile turns out to be Display class on inspection, a monitor characterization, and gets discarded
- Pre-handoff check: confirming the profile about to be embedded in the PDF is CMYK output class, not an accidentally selected sRGB display profile
- Encoding debugging: an older profile shows no description text in newer software; inspection confirms the desc tag uses the legacy text encoding and the file itself is fine
- During handover documentation, the outgoing prepress operator reads every profile used on past jobs and logs its version and creation date into the SOP for the successor to verify
FAQ
- Is the file uploaded to a server?
- No. Parsing runs in code inside your browser; the file never leaves your machine and touches no server. That matters for license-restricted press profiles: inspecting one here does not constitute redistribution.
- What does device class mean?
- Output (printer/press) describes a print condition, Display a monitor, Input a scanner or camera, and DeviceLink a direct conversion between two specific devices. Print simulation and conversion need an Output-class profile.
- Why isn't the white point 1.0?
- Output profiles usually store the media white point, meaning paper white, with Y commonly 0.8–0.95. Paper itself is not a perfect white, so the measured white point sits below 1.0; that is a property, not an error. Display profiles are the ones near standard D65.
- What is the difference between v2 and v4 profiles?
- The v4 spec defines perceptual intent and interpolation more rigorously, but v2 remains the print-industry mainstream with the widest compatibility. Most workflows mix them without trouble; what matters is agreeing one profile across design, prepress and the pressroom, not chasing the newer version.
- What is the difference between FOGRA39 and FOGRA51?
- They are coated-stock characterization datasets from different generations: FOGRA39 is the long-established one, tied to older paper and measurement conditions; FOGRA51 reflects modern papers with optical brighteners and the M1 measurement mode. Mixing them within one job introduces a systematic cast, so standardize on whichever your printer specifies.
- Can I see the gamut?
- This inspector reads metadata, not gamut. To explore gamut, load the profile into the ICC mode of our RGB-CMYK converter for soft proofing and gamut checks; the two tools are meant to be used together.
- If a file has an ICC profile embedded, is color management done?
- No. Embedding only declares the file's color space; downstream software and the printer's RIP may honor, ignore or override that declaration. Color management is an agreement across the whole chain, so confirm with your printer how they handle embedded profiles before handoff.
Limitations & Disclaimer
- Read-only: the tool does not modify files or validate the measurement quality behind a profile
- LUT contents and gamut volume are out of scope
- Very old or non-standard profiles may have missing or unreadable fields
- Results reflect what the file declares about itself; they cannot confirm the profile still matches the current state of the press
Need a Professional Check
What the tools give you is a digital reference. Before a production run, having an industry consultant review your proofs, specs and files costs far less than reprinting a bad batch
Related Articles
Why Screen Colors Never Print Right: A Senior Consultant's Hands-on Guide to ICC Color Management
A perfect design on screen turns dark and muddy in print. This is the single most common pain point I see in the industry. Once you understand gamut differences and ICC settings, you can block 90% of reprint disasters before sending files to press. This guide takes you from color fundamentals to soft proofing, building a precise color matching workflow
Can AI Screen Color Calibration Replace Soft Proofing? A Remote Print Color Management Test for Designers
Many designers think that using Photoshop's Neural Filters or browser color management means what looks right on screen is ready to print. This misconception drives enormous reprinting costs every year. Drawing from remote workflows I've consulted on, this article clarifies what AI color tools can and can't do, and what a truly reliable soft proofing workflow actually looks like
Why Does Bright Green on Screen Look Dull in Print? CMYK vs. RGB Explained Simply
The exact same image looks vibrant on screen, but comes out a shade darker, with muddy greens and flat magentas in print. Almost every beginner designer stumbles into this trap. Based on my years on the production line and working with clients, I'll walk you through color theory, file setup, and soft proofing tricks so you know exactly how to avoid it