Why does a product image change color after export?

Locate the first changed stage

Open the reference photograph and approved candidate in the same color-managed editor. Then open the exported file there. If the export changes while the master does not, inspect the export settings. If only the storefront looks different, investigate its delivered rendition and the viewing device. Avoid comparing a phone in night mode with a desktop in daylight and calling the difference a generation defect.

For an illustrative teal bottle, record whether the cap, label and background all shift together. A global shift suggests a delivery problem; a cap that becomes blue while the background stays consistent may instead indicate a local edit or generation error. This clue guides investigation but does not establish the cause by itself.

Keep a color handoff record

Adobe recommends sRGB for web-focused output. Convert deliberately in your editor rather than randomly assigning a profile to reinterpret existing numbers. Keep the original master so that later exports do not depend on an already compressed file.

For a known-profile Photoshop master, work on a copy and use Edit > Convert to Profile to make the sRGB delivery version; preview it before saving, then reopen the saved file in the same managed editor. Adobe distinguishes conversion from assignment: assignment reinterprets existing values, while conversion transforms them for another color space. If the source is untagged and its intended profile is unknown, request the creator’s export record instead of guessing a profile until the bottle looks pleasing.

Use three separate identifiers: master revision M, local web export E and the browser-delivered image D. Compare M/E first, then E/D under the same viewing conditions; write “D not yet retrieved” when only a screenshot is available. A matching filename is insufficient proof that the store is serving E. Keep the old export for comparison until the replacement is verified. Metadata review records delivery properties; it cannot reconstruct an unknown original profile or establish the physical merchandise shade.

Check the delivered version

Inspect the exact image shown by the storefront, including variant selection and zoom. Compare a neutral region and the identifying product color. Do not compensate for one uncalibrated screen by making the source unnaturally saturated for everyone else. Record the device conditions when an objection cannot be reproduced.

Approve a practical boundary

The release note should identify the approved web export and remaining display variation. CartVisual generation is not physical color calibration or automated ICC repair. If the merchandise shade itself changed, return to the real variant reference and the variant proofing workflow. If the file is correct but the storefront shows an older version, use the replacement verification guide.

A worked export investigation

Suppose the approved teal bottle looks correct in the master, green in a delivery copy and green in the store. Start with that delivery copy, not the store theme. Record the master profile and the export conversion, then produce a new named test from the original master. If the editor shows the corrected copy consistently but one phone still differs, document that viewing condition. Do not submit a new paid generation simply to compensate for that phone. The useful deliverable is a verified export path and an explicit remaining display limitation.