Check ICC profiles when colors change after image conversion

Understand what an ICC profile contributes

RGB numbers do not fully define an appearance without a color interpretation. An ICC profile describes how the stored values relate to colors, allowing color-managed software to translate them for a display or another working space. Identical numeric values can therefore look different when interpreted as sRGB or as a wider-gamut space. If a format conversion changes or loses that interpretation, the output may appear dull, oversaturated, or shifted even when many pixel values seem familiar.

Not every image carries an embedded profile, and not every viewer handles profiles in the same way. Some applications apply color management, while another environment may make an assumption about untagged data. That is why a visual match in one preview is not a complete test. Inspect whether the source and output have profiles, identify them when possible, and note the applications used for comparison before deciding where the difference began.

• Check whether both source and output contain an embedded profile.
• Record the profile name and the application used for viewing.
• Separate stored RGB values from the color space that interprets them.

Separate assigning, converting, preserving, and removing

Copying an embedded profile to the output, converting pixel values into a target space, assigning a different profile, and removing the profile are not interchangeable actions. If a wide-gamut image loses its profile while the RGB numbers remain unchanged, another program may interpret those numbers as sRGB and show a different color. Merely deleting the profile does not calculate new sRGB values, so stripping a tag should not be described as accurate conversion to sRGB.

When a delivery workflow requires sRGB, use software that recognizes the source profile and performs a color-space conversion to the intended target, then embeds the appropriate result profile when the workflow supports it. Choose rendering and export settings according to the application's documented behavior and the job's needs. If an online converter does not explain its profile handling, test it with a representative image before trusting it with brand colors, product photography, or a large batch.

• Do not confuse profile deletion with conversion to sRGB.
• Use a color-managed application when an explicit target space is required.
• Test undocumented conversion behavior on a disposable copy.

Check profile and compression behavior in PNG and WebP

PNG and WebP can carry color-related information, but support in a format does not guarantee that every tool preserves or transforms it as expected. Review the converter's documentation for embedded-profile behavior. If it offers no clear statement, inspect the source and result with a profile-aware utility and compare them visually. Also confirm pixel dimensions and transparency so an unrelated resize or compositing change is not mistaken for a color-space problem.

Compression can create a different class of visible change, particularly near color edges and smooth gradients. To isolate the cause, begin with one high-quality file and change as few variables as possible. Compare a PNG-to-WebP result at an appropriate quality setting and, when testing the reverse path, remember that converting a lossy output back to PNG will preserve existing compression effects rather than undo them. Examine profile state, compression artifacts, and transparent edges as separate items.

• Review documented profile behavior for the exact conversion path.
• Hold dimensions and viewing conditions constant during comparison.
• Evaluate color interpretation and compression artifacts separately.

Build a controlled visual comparison

Do not compare the source in an editor with the output in an unrelated browser and attribute every difference to the file. Open both in the same color-managed application, on the same display, at the same zoom, and against the same background. Compare neutral grays, skin tones, saturated brand colors, and smooth gradients. If transparency is involved, place both files over an identical background because edge blending can change the perceived color.

Next, test the output in the environment where it will actually be delivered. A website, social platform, print application, or mobile app may process or display the asset differently. Keep display conditions stable where practical: night mode, automatic color temperature, HDR modes, and extreme display presets can all interfere with judgment. When color tolerance is strict, use a managed workflow and objective measurement or a suitable proof rather than approving solely by casual visual memory.

• Compare both files in the same managed viewer first.
• Use the same zoom, background, display, and lighting conditions.
• Then inspect the uploaded or placed result in its real destination.

Keep a master and record the approved output

After conversion, inspect the output's profile, dimensions, transparency, and key colors alongside the source. Use image areas that reveal errors quickly: neutral backgrounds, skin, corporate colors, shadows, and gradients. Reopen the downloaded file rather than relying on a web preview, then place it in the real page or application. If the destination modifies uploads, inspect the delivered version as well as the local export.

Preserve a master file with its known profile and enough quality for future exports. Record the target color space, conversion path, and intended use for the approved derivative. If only an untagged or repeatedly converted copy remains, reliable print or cross-platform work becomes harder later. When a mismatch persists, stop cycling through formats and trace the profile at each step from source to converter, editor, upload service, and viewer.

For a batch workflow, include at least one neutral image and one highly saturated image in the sample set. A converter may appear acceptable on muted content while revealing a profile mistake on strong colors. Recheck after any tool or export-setting change, because a previously approved sample describes that tested path rather than every future conversion.

• Use neutral and highly saturated reference areas during inspection.
• Preserve the profiled master separately from delivery derivatives.
• Document the target space and destination for the approved file.