HEIC color troubleshooting
Why colors can change after converting HEIC to JPG
An iPhone HEIC may use HDR rendering or a wider color gamut that one screen and app display differently from an ordinary JPG. JPEG quality controls compression, not HDR tone mapping. Compare both files under the same conditions, keep the HEIC master, and export for the destination’s actual color support.
Name the color change
The kind of color change reveals which rendering step is involved
“Different color” can mean reduced HDR brightness, a gamut change, an app-specific display issue, or ordinary JPEG artifacts. Compare the files carefully before changing export quality or adding filters.
Bright highlights look flat or washed out
An HDR-capable HEIC can show a wider brightness range in compatible Photos software and on an HDR display. A standard JPG delivery copy may be rendered for SDR, so highlights and contrast no longer have the same visual impact.
Saturated reds, greens, or blues become muted
The source may contain colors from a wider gamut than the output or destination displays. If a color profile is omitted or interpreted differently, vivid colors can shift even when fine detail remains sharp.
The JPG looks correct in one app but wrong in another
Color management differs across software and older viewers. One app may honor an embedded profile or HDR information while another assumes a standard color space, producing inconsistent brightness or saturation.
Edges and textures look blocky rather than recolored
That pattern is more likely JPEG compression. Raising output quality can reduce artifacts, but it will not restore HDR brightness or colors outside the delivery color space.
HDR and color rendering
HEIC and JPG can target different brightness and color assumptions
HEIC is a container that can carry modern image data and supporting information used for wide-gamut or HDR presentation. Apple Photos can combine the file, display capabilities, and system color management to render an appearance that a simple SDR export cannot reproduce exactly.
A browser converter decodes the image into pixels and creates a new lossy JPEG. During that path, HDR content may be tone-mapped and color information may be normalized for ordinary display. This tool does not preserve source EXIF metadata, and the receiving app can still interpret the JPG differently.
Judge the delivery copy in the environment where it will be used. An SDR JPG can be valid and useful even when it does not match the luminous HDR view in Photos; the goal is a predictable appearance on the destination, not a claim of pixel-for-pixel equivalence.
A controlled comparison
Make a controlled color comparison before choosing the export path
- 1
Keep the original HEIC as the color master
Do not overwrite or delete the source. Preserve it in Photos, iCloud, or an archive so its original image data and metadata remain available for a different export or future HDR-capable workflow.
- 2
Compare both files in the same app and display
Open the HEIC and JPG in one current, color-managed viewer on the same screen at the same brightness. Side-by-side comparisons across different apps or an HDR phone and SDR monitor mix multiple variables and can produce a false diagnosis.
- 3
Identify HDR, gamut, or compression symptoms
Look separately at highlight brightness, shadow contrast, saturated colors, gradients, and fine texture. Flat highlights suggest tone mapping; muted saturated colors suggest gamut or profile handling; blocks around edges suggest JPEG compression.
- 4
Create one browser-local JPG test
For an HEIC no larger than 50 MB, convert one representative image in the browser. Expect a lossy, metadata-free compatibility copy. Do not batch-convert the full library until the destination displays this test acceptably.
- 5
Use a color-aware export when matching matters
For client delivery, print, or color-critical work, export through trusted photo software with explicit SDR, color-space, and profile controls. Preview that output on the target system. A browser converter is intended for compatibility, not color-managed mastering.
- 6
Verify the actual receiving service
Upload the test and inspect the service’s processed preview, because social networks and CMS tools may recompress or strip profiles again. Adjust from the original and export once more if needed instead of repeatedly editing the already-lossy JPG.
Ready to test the destination?
Convert one HEIC and compare the result under the same conditions.
Color questions
HEIC to JPG color FAQ
Why does the JPG look washed out next to the HEIC on my iPhone?
The Photos view may be rendering HDR brightness or wide-gamut color that the standard JPG does not reproduce in the same way. Compare both files in the same app and check the JPG on its intended destination before judging the export.
Will a higher JPEG quality restore the original HDR look?
No. Quality mainly controls lossy compression. It can reduce blocking and texture loss, but it does not restore HDR brightness, a wider gamut, or color information lost during tone mapping.
Is a color-shifted JPG corrupt?
Usually not. If the image opens completely but brightness or saturation differs, the issue is more likely rendering, profile handling, tone mapping, or destination processing. Corruption more often causes decode failures, missing regions, or unreadable data.
Does this converter preserve the HEIC color profile and EXIF?
It is a compatibility workflow, not a color-managed archival export. It re-encodes visible pixels as a lossy JPG in the browser and does not preserve source EXIF metadata. Keep the HEIC for color-critical or metadata-dependent work.
Can I test a large HDR HEIC in the browser?
The source must be 50 MB or smaller, and high-resolution decoding can still require substantial memory. Test one file at a time in a current browser and use desktop photo software when precise HDR-to-SDR control matters.