Editor › Learn › Assign vs Convert Profile: The Difference That Ruins Files
What is the difference between assigning a profile and converting to a profile?
Assign changes the INTERPRETATION of your pixel numbers without touching them — the file's appearance changes because the same numbers now mean different colours. Convert changes the NUMBERS through a colour transformation so the appearance stays as consistent as the gamuts allow. Assign is for repairing files whose profile is missing or wrong; convert is for moving a correct file into a different space. Confusing the two is one of the most common colour-management mistakes in production.
One picture of the difference
Why both operations must exist
Pixel numbers have no fixed meaning — a profile supplies it. Two situations therefore arise in real work. First: the numbers are RIGHT but the label is wrong or missing (a scan saved without a profile, a file stripped by a web pipeline). The fix is to assign the profile that matches how the numbers were produced; appearance snaps to correct without altering a single value. Second: the numbers are right AND correctly labelled, but the destination needs a different space (web delivery in sRGB, press delivery in a CMYK condition). The fix is to convert: compute new numbers whose appearance in the destination matches the source as closely as the gamuts allow.
The classic failure, step by step
A designer receives an unlabelled file that "looks too saturated". They CONVERT it to sRGB — but the software, seeing no profile, assumes the numbers were already sRGB, so the conversion is a no-op and the file still looks wrong. The actual problem was interpretation: the numbers were Adobe RGB. The repair is ASSIGN Adobe RGB (appearance corrects instantly), THEN convert to sRGB for delivery. Assign to repair meaning, convert to change destination — in that order, at most once each.
Rules that prevent the damage
- Never assign a profile to a file that already has the correct one — that is how right files become wrong.
- Assigning is non-destructive to the data (numbers untouched), but SAVING with the wrong assignment poisons the file for everyone downstream.
- Converting is data-destructive by design: values are recomputed and out-of-gamut colours are remapped. Convert once, at the end, and keep the master.
- If an unlabelled file looks right when interpreted as sRGB, it almost certainly is — assign sRGB and move on.
Straight comparison
| Assign profile | Convert to profile | |
|---|---|---|
| Pixel numbers | unchanged | recomputed |
| Appearance | changes (new meaning) | preserved (gamut permitting) |
| Purpose | repair wrong/missing interpretation | move to a delivery/print space |
| Lossy? | no (until saved with wrong label) | yes — one-way in practice |
| Typical moment | on intake of suspect files | at the end, per destination |
Questions
- Which one does Image ▸ Mode ▸ CMYK do?
- Convert. It computes new CMYK values through the chosen profile and intent so the appearance survives the mode change.
- A print house asked me to "assign FOGRA39" — is that wrong?
- If your file is already correctly labelled RGB, yes — they almost certainly mean CONVERT to FOGRA39. Assigning a CMYK profile to RGB numbers is not even meaningful. Ask; wording is loose in the field.
- How do I tell whether an unlabelled file is sRGB or Adobe RGB?
- Try both interpretations and judge skin tones and saturated colours: misread Adobe RGB looks dull as sRGB; misread sRGB looks oversaturated as Adobe RGB. Cross-check against any sibling file whose provenance you trust.