The usual cause is a mismatch between the photo’s embedded color profile, the way an application interprets that profile, and the display used for viewing. Converting a photo changes its color values to preserve its appearance in a new color space; assigning a profile only changes how existing values are interpreted. Make one properly converted sRGB copy, view it in two color-managed viewers, and compare the same file on more than one device before deciding where the mismatch occurs.
Conversion Is Not Assignment
A color profile describes how numeric pixel values should appear. If a wide-gamut photo is converted to sRGB, the editor recalculates the values so the image can be represented in sRGB as consistently as possible. The profile tag then identifies those values as sRGB.
Assigning sRGB to the same wide-gamut values does something different: it tells software to interpret the existing numbers as sRGB. The image may become noticeably more saturated, duller, or shifted because the numbers were not recalculated. This is why changing a profile label can appear to “fix” one viewer while damaging the intended color elsewhere.
Decision checkpoint: if the editor offers both “convert” and “assign,” choose conversion when the goal is to prepare a copy for general web viewing. Use assignment only when you have confirmed that the pixels already belong to that profile.
Build One Controlled Comparison
For a fictional planning example, imagine a coral postcard prepared for an online shop. In the editor, the coral looks balanced, but on one phone it appears intensely orange while a laptop browser looks closer to the original. The goal is not to prove which screen is correct. The goal is to identify whether the file, viewer, or device is responsible.
- Duplicate the working image and keep the original untouched.
- Convert the duplicate to sRGB using the editor’s current color-management controls, then save a new copy with the profile embedded.
- Open that exact copy in two different viewers, preferably one known to manage embedded profiles and one ordinary browser view.
- Compare the editor, both viewers, and the phone without changing brightness, night mode, vivid display mode, or viewing conditions during the comparison.
Record observable checks: Is the embedded profile still present? Does the sRGB copy look similar in the editor and the color-managed viewer? Does the shift appear only on the phone? These checks separate file interpretation from display behavior.
Read the Pattern of the Shift
If the editor and a color-managed viewer agree but the browser differs, the browser or its operating environment may be interpreting the file differently. If both viewers agree but one device looks different, the device display, brightness, viewing mode, or calibration is the stronger suspect. If the editor changes after conversion while the original did not, compare the two files side by side and confirm that the conversion, rather than assignment, was used.
Decision checkpoint: if only one device shows the change, do not keep altering the image to match that device. First test the same sRGB copy on another screen.
For web delivery, use the converted sRGB copy as the working candidate, but inspect important brand colors, skin tones, and shadow detail in the final viewer you expect customers to use. Do not assume every browser or display renders color identically.
Acceptance Test Before Publishing
The fictional coral postcard passes the planning check when the file is clearly identified as an sRGB copy, the editor and at least one color-managed viewer show broadly consistent color, and the phone-only difference has been documented as a display-specific observation rather than “corrected” by damaging the file.
A final check should include the file’s profile information, a visual comparison at the same zoom, and a quick review of saturated areas. If exact color matters, use a controlled external workflow for display calibration and final production checks; Imagild Skills can help with image creation and editing, while external editors remain useful for profile inspection and conversion.
Should I always assign sRGB for web images?
No. Assigning sRGB can misinterpret existing pixel values. Convert the image when you need to move it into the sRGB color space.
Why does the same file look different on two phones?
Displays can differ in gamut, brightness, calibration, viewing modes, and ambient light. A file can be handled consistently while the screens still look different.
Is a browser preview enough to judge exact color?
No. Use the browser as one practical viewing check, not as an absolute color reference. For exact work, include profile inspection and controlled external review.