Short answer
Most often because one app is not colour-managing on a wide-gamut screen, or because night mode, true tone or brightness settings differ; less often because the file lacks a colour profile or the panels themselves differ. Start by asking whether the difference is between two screens or between two apps on one screen — the answer points to different causes.
1. One app is not colour-managing on a wide-gamut screen
Test: Open the same image in the system photo viewer and in the suspect app on the same screen, side by side. If the suspect app is noticeably more saturated, it is sending sRGB numbers unconverted.
Wide-gamut phones and laptops need software to shrink sRGB colour into their larger range; unmanaged apps skip this and every red and green looks louder.
2. Brightness, night mode or 'true tone' settings differ
Test: Turn off night mode, true tone and adaptive colour on both devices, set both to a similar brightness, and compare again.
These features move the white point warmer or cooler through the day, which shifts every colour on screen with it.
3. The file has no embedded colour profile, or the wrong one
Test: Export a copy with an sRGB profile embedded and compare it with the original on both screens. If the tagged copy agrees better, the file's tag was missing or unusual.
Untagged images are assumed to be sRGB by most browsers; an Adobe RGB or P3 image without its tag is displayed with the wrong meaning.
4. Panel differences: OLED versus LCD, viewing angle, age
Test: Compare dark greys and near-blacks at a straight-on angle, then tilt the laptop screen. Shifts that appear only in dark tones or at an angle are panel behaviour.
LCDs lift near-blacks and change with angle; OLEDs hold dark colours but can tint whites. Old backlights also yellow or dim.
Causes are ordered by how often Colourwise expects each to be the explanation — an editorial judgement, so test them all.
Open the same image in two apps on the same screen before comparing devices. If the apps disagree, the screen is not the problem: one of them is handling colour differently, and the fault will follow that app to every device. If the apps agree but two screens disagree, move on to the display settings and then to the hardware. This split matters because the fixes are different in kind — an export setting or an app choice on one side, a settings menu or a calibration on the other — and because calibrating a display does nothing for an app that ignores the calibration. The digital-colour topic on why the same HEX looks different explains the underlying mechanisms; this page is the order in which to test them.
Browsers and operating systems differ in how thoroughly they convert colour for the display. Safari and Chromium-based browsers treat untagged images as sRGB and convert them for the monitor; Firefox has long offered full management of untagged content only as a setting rather than by default. On Windows, automatic colour management for ordinary SDR displays arrived only recently and depends on the display having a proper profile, so many desktop apps still do their own management or none. The telltale sign is saturation: an unmanaged app on a wide-gamut screen shows sRGB colours too vivid. The fix is to view in a managed app, enable the browser's management setting where it exists, or use the monitor's sRGB mode for web work.
Night shift, night light, true tone, adaptive colour and eye-comfort modes all warm or cool the whole display, sometimes on a schedule or in response to ambient light, and they are on by default on many phones and laptops. Two otherwise identical devices can therefore disagree by the time of day. Brightness matters too: a screen at full brightness makes every colour look lighter and more saturated than one turned down. Before comparing, switch these features off on both devices and set a similar brightness. If the difference largely disappears, you have found it, and you can decide whether to leave the features off while doing colour work.
OLED phones and LCD laptops also differ most in the dark tones and off-axis: compare near-blacks head-on before blaming the file.
A hardware colorimeter measures your display and builds a profile so that colour-managed apps can show colour correctly on it. It is the right tool for anyone whose own screen must be trustworthy, and it removes panel-to-panel variation between your devices. It does not change what your clients, readers or customers see on their uncalibrated phones, and it does nothing for apps that ignore profiles. For communicating a colour to someone else, the reliable routes are an embedded profile in every exported image, a CSS colour that names its colour space, and — when the colour really matters — a physical reference or a measured value sent alongside the HEX.
Why: The app is not colour-managing on a wide-gamut display
Fix: View and approve colours in a managed app, or switch the monitor to its sRGB mode
Why: A night-light feature is scheduled on
Fix: Turn it off while making colour decisions, or do them in daytime
Why: Calibration only corrects your display
Fix: Embed profiles in exports and send a physical or measured reference for critical colours
Each statement is labelled by kind — established fact, a standard’s requirement, observed market data, a convention, or Colourwise’s own interpretation or analysis — with the strength of the evidence behind it.
FactModerate evidence
WebKit colour-matches images on iOS and macOS and treats images without an embedded profile as sRGB so that they match CSS colours.
Source: Improving Color on the Web (WebKit blog, 1 July 2016)
FactModerate evidence
Firefox's bug to enable full colour management of untagged content by default was still open on 29 September 2026.
Caveat: Browser behaviour changes between releases; check the current version's settings.
Source: Mozilla bug 455077: Enable full color management by default (gfx.color_management.mode = 1)
FactStrong evidence
From Windows 11 version 22H2, SDR displays receive automatic system colour management only if provisioned with a suitable ICC profile; otherwise applications must manage colour themselves.
Source: Use DirectX with Advanced Color on high/standard dynamic range displays
FactStrong evidence
OLED panels have a true black state while conventional LCDs leak backlight, and perceived contrast under room lighting depends on ambient contrast as well as dark-room contrast.
Colourwise interpretationModerate evidence
Comparing the same file in two apps on one screen is the quickest way to separate software colour handling from display differences.
Based on: Colourwise reading of how ICC colour management works: a conversion happens in software per app, so disagreement on one display isolates the app.
Reviewed 29 September 2026. Colourwise summarises its sources in its own words and does not reproduce standards text or proprietary colour data. Spotted an error? Tell us.