Fix color shifts after export in a digital archive

An image looks right in your editing app, but the exported copy looks dull, too warm, or oversaturated. In a digital archive, that difference can affect a single image or a whole batch. The key is to find out whether the file’s pixels changed, its color profile was lost or misread, or only the viewing app is showing it differently.

Keep the original untouched while you test. The Image Converter can convert image formats in your browser, but a format conversion alone does not confirm that a color profile is correct.

Check one image before changing the archive

Make a working copy. Duplicate one original image and its exported version. Keep both copies together and do not overwrite the archive master.
Compare them in the same viewer. Open the original and export in the same color-managed image application, at the same zoom and display settings. Avoid judging one in a browser and the other in an editing app.
Check the profile information. Look at each file’s metadata or color-management details. Note whether an ICC profile is embedded, and whether the source and export use the same color space, such as sRGB or Display P3.
Check the export settings. In the application that made the export, find its color profile or color conversion options. Confirm whether it converts to a target profile or merely assigns a profile to the existing pixel values.
Test a separate format copy if needed. If the profile looks correct but you suspect a format change, convert a duplicate with the Image Converter. Compare that output in the same viewer. Test one file before converting a batch.

A profile describes how image values should appear as colors. Assigning a profile changes how those values are interpreted. Converting to a profile changes the values so the appearance should remain similar in a color-managed viewer. Confusing the two can make an image look very different.

What the color shift tells you

The export looks different in one app only

The file may be fine, while the app handles color profiles differently. Check the same original and export in another color-managed viewer before editing or replacing anything. If the difference follows one app, check that app’s color management and display profile settings.

The export looks different in every viewer

The export may have different pixel values, a missing profile, or an incorrect profile assignment. Compare the profile metadata and return to the export settings. Do not try to correct the entire archive by eye until you know whether the file was converted or simply tagged incorrectly.

The image looks washed out or too saturated

This often happens when a viewer ignores an embedded profile or interprets the pixel values using the wrong one. A wide-gamut source, such as Display P3, can look oversaturated when its values are treated as sRGB. Check that the profile is embedded and that the viewer supports color management.

The shift appears after changing the file format

The conversion step may have altered color information, or the new file may not carry the profile as expected. Check the output file’s profile and compare it with the source. Some formats and export workflows also change transparency or use lossy compression, so examine edges and fine color detail as well as the overall appearance.

How to fix the export

Preserve the original master. Keep an unmodified source and export to a new file. For archive records, note the source filename, export format, date, and profile used so you can repeat the process later.
Use a deliberate target profile. If the image is intended for general web viewing, sRGB is commonly supported. If your archive requires another profile, follow its specification instead. Convert to the intended profile during export, rather than assigning a different profile without a clear reason.
Keep profile embedding enabled. If the export application offers an option to embed or include the color profile, enable it when the archive workflow expects profile information. Reopen the exported copy and verify the profile is present.
Separate color conversion from format conversion. First make and check a profile-correct copy in the application that manages color. Then convert the file format only if required. The browser-based Image Converter is useful for format changes, but do not treat conversion as proof that the archive’s color profile requirements are met.
Check the display profile before judging. On Windows 11, open Settings › System › Display › Color profile. On macOS, open System Settings › Displays and check the selected color profile. These settings affect how your screen displays color, not the pixel values stored in the image.
Repeat a verified export on a small sample. Once one image looks right and its metadata matches your archive requirements, export a small group and inspect the results before processing the full collection. The Image Converter can handle up to 50 images at a time, but batch size does not replace a profile check.

Keep the archive workflow repeatable

For long-term storage, use the format and profile rules required by your institution or archive. Do not assume that a larger file or a particular extension automatically makes an image more faithful. A TIFF, PNG, or JPEG can each be produced with different settings, and a JPEG export can discard detail through lossy compression.

Record which application and settings produced each derivative. Keep the source file separate, retain its original metadata, and make a note whenever you convert color spaces or formats. That record makes it easier to distinguish an intentional derivative from an accidental color change.

The Image Converter processes files in your browser, and the files you open stay on your device.