Keep the embedded ICC profile with the original image. For sRGB previews, convert the pixels before removing the source profile.
The danger point is the upload step that removes an ICC profile while leaving the image’s pixels unchanged. Keep the profile with the original; when creating an sRGB preview, convert the pixels using the source profile before replacing or removing that profile.
An embedded ICC profile describes how to interpret the color values in an exported image. It gives a color-managed application the context it needs to display those values.
The phrase “camera profile” can cause confusion because it can refer to different parts of a photographic workflow. A RAW processing profile helps determine how sensor data becomes a rendered photograph. An ICC profile embedded in a rendered image describes the color space of that resulting image.
The International Color Consortium explains that when a camera exports an image with an embedded profile, its firmware renders the image into a standard color space, such as sRGB or Adobe RGB (1998), and embeds the corresponding profile.
That distinction matters at upload. A JPEG exported by a camera may carry an Adobe RGB profile. The useful information for interpreting that JPEG is the profile describing its rendered pixels. Keeping it does not preserve every decision available in the camera’s RAW file.
I separate those questions when evaluating an upload workflow: can the rendered photograph retain its intended appearance, and can the original capture still be developed differently? An embedded ICC profile addresses the first question. RAW preservation belongs to the second.
Stripping an ICC profile can leave an image’s color values without the information needed to interpret them correctly. The file may still open successfully, which makes this failure easy to overlook.
“Metadata” is a broad label. Capture dates, location information, copyright fields and color profiles serve different purposes. An ingest rule that removes everything under that label can discard color interpretation along with information that an operator intended to remove for privacy.
For web display, there is a specific consequence. The W3C CSS Color specification states that, for compatibility, untagged images must be treated as being in the sRGB color space unless otherwise specified.
Suppose the pixels were encoded in Adobe RGB and their profile disappears. A browser following that default treats the untagged image as sRGB. The numeric values remain, while their interpretation changes. Colors can shift because the same values describe different colors in different spaces.
An sRGB image whose profile is removed has a different starting point: its pixel values already correspond to the browser’s default interpretation. That distinction is why “remove all profiles” is an unreliable universal ingest policy.
The practical concern is the preview approval step. A photograph can upload, generate a thumbnail and appear in a gallery while its color has changed. Successful file handling alone does not establish faithful rendering.
Converting to sRGB means translating pixel values from their source color space into sRGB. Deleting a profile only removes the description attached to those values.
A conversion needs a known source interpretation. A color-managed processor reads the embedded profile, calculates destination values and produces an image described by the destination color space. Its output can then carry an sRGB profile.
Assigning a profile is another operation again. Assignment tells software how to interpret existing values without translating them. It is useful when the correct interpretation is known, but attaching sRGB to an Adobe RGB image does not perform an Adobe RGB-to-sRGB conversion.
These operations deserve separate names in an upload specification:
| Operation | Changes pixel values? | Effect on color interpretation |
|---|---|---|
| Preserve the embedded profile | No | Retains the supplied interpretation |
| Remove the embedded profile | No | Leaves interpretation to a default or other information |
| Assign a different profile | No | Gives existing values a different interpretation |
| Convert to sRGB | Yes, where required by the conversion | Translates values into the destination color space |
A conversion also has limits. Colors outside the destination gamut cannot all retain their original appearance. The conversion’s rendering choices determine how those colors fit into the destination. Keeping an original alongside a delivery derivative preserves the source for a later export with different requirements.
An Atlas upload check should establish the treatment of the original file and each generated derivative separately. A browser preview cannot answer every question about the stored original.
For a library workflow involving Atlas Photo, I would make the acceptance criteria specific to the files being evaluated. “Keeps color” leaves too much room for interpretation. “The downloaded original retains its embedded ICC profile” is something an operator can inspect.
The same precision belongs in the preview requirement. A thumbnail might retain the source profile, or its pixels might be converted into a delivery color space. Either approach needs the file’s values and its declared interpretation to agree.
An original download, a gallery preview and a thumbnail are separate outputs. Checking one does not establish the behavior of the others. A thumbnail generator can have different settings from the process serving a larger preview.
This also separates preservation from appearance. A profile inspection establishes whether the profile is present and identifies it. A visual comparison establishes whether a rendered output matches a reference closely enough for its intended use. Each check answers a different question.
Check color handling by comparing uploaded outputs with known source files and reference exports made before upload. The reference provides a baseline that does not depend on the upload processor.
Use a photograph with both saturated colors and subtle neutral areas. Strong colors can reveal gamut differences; neutral surfaces and skin tones can make smaller shifts easier to notice. Keep viewing conditions consistent so that a display change does not become an extra variable.
A repeatable check follows these steps:
For an additional diagnostic, make a copy of the Adobe RGB export and remove its profile without converting its pixels. Label it clearly in your working folder. Comparing that copy with the tagged source helps distinguish a missing-profile problem from an intentional conversion.
A useful acceptance record contains the source profile, output profile and observed appearance for each file. It ties a visible change to a specific stage in the upload path.
An untagged image’s intended profile generally cannot be established from its pixel values alone. A filename, export preset or preserved source may supply the missing context, but appearance by itself leaves room for guesswork.
If a known Adobe RGB export lost its profile without a pixel conversion, assigning that known profile can restore the interpretation. If the pixels were already converted to sRGB, assigning Adobe RGB would introduce a new mismatch. The processing history matters.
Start with a tagged Adobe RGB photograph and its independently converted sRGB reference. Upload both, download the available outputs, and record the profile attached to each file before judging the gallery preview.
Keep your team's photos in one place. Upload your shoots, find any photo by describing it, and export it in the right size. The free plan has 5 GB and 100 photos, no card needed. Start free
