Image colour review
Colour profiles, palette checks, and safer image exports
An image’s colour values need a context to be interpreted consistently. A palette tool can identify sampled colours; it cannot guarantee that every browser, printer, or upload pipeline will reproduce them in the same way.
On this page

RGB numbers are not a complete colour promise
A pixel described as red, green, and blue values is still interpreted through a colour space, display, application, and sometimes an embedded profile. Two viewers can show a noticeably different result while reading the same file honestly. This is especially visible in saturated artwork, gradients, and brand colours.
The practical goal for an upload asset is usually consistency, not theoretical perfection. Use a destination-friendly export, preserve a source copy, and inspect the final rendered result on the type of display or preview that matters to the work.
Worked example: a palette is evidence, not a brand approval
Imagine a design that needs a dark teal accent. A palette inspection may report a dominant sample close to #176B64 from the source. That is a useful reproducible observation: it tells a reviewer where the tool sampled and what it found.
It does not establish that the destination’s stylesheet, store listing, printer, accessibility contrast treatment, or transformed thumbnail will preserve that same appearance. Record the sample, compare the exported file visually, and use the brand owner’s current specification when one exists.
| Observation | Useful conclusion | Not established |
|---|---|---|
| Palette sample | A sampled pixel or cluster has a reported value. | Universal visual match on every display. |
| Embedded profile present | The file carries profile information readable by the tool. | That a receiving service preserves the profile. |
| Visual side-by-side review | The reviewed displays show a visible difference or match. | Print or third-party rendering quality everywhere. |
Export choices can change more than bytes
A conversion may flatten transparency, reduce palette precision, omit an embedded profile, or apply a browser and codec-specific colour path. Those changes can be appropriate for a strict delivery format, but they should be visible in the workflow rather than presented as a neutral compression step.
For an illustration with clean flat areas, PNG can preserve hard edges and transparency but may remain large. For a photograph, JPEG may reduce bytes effectively while introducing artefacts. The file type choice follows image content and destination requirements, not a universal ranking.
Keep a defensible review trail
When colour matters, keep the original, the named export, the chosen format, output dimensions, and a short note about the display or preview used for review. That record makes a later discrepancy explainable without claiming a guarantee that cannot be made.
If a destination changes the colour after upload, it may be applying its own processing, format conversion, or display context. Check its current documentation and preview rather than repeatedly editing the source on speculation.
Use a local tool
