Product images / PRACTICAL ANSWER
Why do two cameras produce different colors for the same product under identical lights?
Two cameras can render the same product differently because their sensors, color filters, camera profiles and processing defaults are not identical. Matching the white-balance number does not guarantee matching color. Capture a common reference under unchanged lighting, compare neutral rendering first, then evaluate the product's colored surfaces using camera-appropriate profiles.
Identify the camera-dependent part of the workflow
Different camera models can record different responses to the same scene. RAW processing software interprets those responses using camera-specific information and profiles.
Adobe's Camera Raw documentation explains that different camera formats require different interpretation. Its supported-camera list also distinguishes availability of camera-matching profiles by model.
A shared Kelvin value does not make two cameras spectrally identical. Nor does selecting a similarly named picture style guarantee identical rendered colors.
Start by checking whether the two files are genuine RAW captures or already processed JPEGs. In-camera JPEG rendering may include different tone curves, saturation, contrast and color processing before the files reach the editor.
Create a common capture reference
Use the same physical product and stable lighting. Photograph a suitable color chart with each camera, following the target manufacturer's placement and illumination instructions.
- Record each camera model and the actual file format.
- Keep the lighting arrangement unchanged between captures.
- Position the chart under the product's representative illumination.
- Use appropriate exposure for each camera without clipping important patches.
- Preserve both original files and process them in the same documented software environment.
Matching shutter speed, aperture and ISO numerically is not itself proof of equal recorded brightness or color. Compare the actual exposures and neutral reference.
If the product moves between cameras, preserve its orientation and lighting geometry. A glossy surface can change reflected color with camera angle, which would introduce another variable.
Compare profiles before editing individual colors
Apply an appropriate neutral white balance to each RAW file. Then inspect the active camera profile and RAW defaults.
Adobe Camera Raw supports camera-specific RAW defaults, and camera-matching profiles are available only for supported models. A profile that exists for one body may not exist for another.
Compare neutral patches first. If they disagree, investigate white balance, exposure or processing defaults. If neutrals agree but colored patches differ, compare the selected camera profiles and their rendering behavior.
A chart-based correction may help create a more consistent workflow, but it must be supported by the chosen profiling software. Do not transfer a profile built for one camera body to another without verifying compatibility and intended use.
Illustrative diagnosis: two cameras and a green bottle
Hypothetical editorial example; no cameras or software were tested. Camera A and Camera B photograph the same matte green bottle under one controlled studio source.
Both cameras use a nominal white-balance setting of 5000 K. The initial rendered files show different greens: A appears close to the approved reference, while B appears more yellow.
Both RAW files are processed with neutral chart sampling. Their gray patches now appear similar, but the bottle remains different.
The editor discovers that Camera A uses a camera-specific profile while Camera B uses a different default rendering profile. In the illustrative comparison, selecting an appropriate supported profile for B reduces the green mismatch without changing the physical setup.
The completed diagnosis is inconsistent RAW color interpretation between camera bodies, not evidence that the bottle changed color. The correction is recorded per camera rather than applied as a universal green adjustment.
Maintain separate camera records
Keep the camera identity, RAW profile, white-balance method, target reference and processing version with each capture set.
If one camera remains inconsistent after controlled profiling, do not force a visually arbitrary correction merely to make two files match. Check the actual product against its approved reference and document any unresolved difference.
CartVisual does not match camera sensor responses automatically. Provide a consistent, reviewed source image for the product. Generated outputs should be compared against that source rather than used to decide which camera was accurate.
Record your own observations
The filled rows are illustrative examples. Use the blank row for your own files and observations.
| Capture | Camera | RAW profile | Neutral patches | Green bottle | Decision |
|---|---|---|---|---|---|
| A1 | Camera A | Camera-specific | Neutral | Matches illustrative reference | Baseline |
| B1 | Camera B | Different default | Neutral after WB | Too yellow | Investigate profile |
| B2 | Camera B | Appropriate supported profile | Neutral | Closer to reference | Document camera-specific correction |
| Your capture |
What the references establish
- Adobe — Introduction to Camera Raw: Documents camera-dependent RAW formats and interpretation.
- Adobe — Cameras supported by Camera Raw: Official camera support table identifying camera-matching profile availability. Availability is model- and software-version-dependent.
- Adobe — Set up raw defaults in Adobe Camera Raw: Documents camera-model-specific RAW defaults, including distinctions by camera identity.
- Datacolor — How does the SpyderCHECKR apply a change to my images?: Explains chart-based corrections for a particular camera and lens combination. Does not guarantee identical rendering across cameras.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Adobe — Introduction to Camera Raw · Review date not separately recorded
- Adobe — Cameras supported by Camera Raw · Review date not separately recorded
- Adobe — Set up raw defaults in Adobe Camera Raw · Review date not separately recorded
- Datacolor — How does the SpyderCHECKR apply a change to my images? · Review date not separately recorded
Frequently asked questions
Should I set both cameras to the same Kelvin value?
That may provide a starting point, but it does not guarantee identical neutral or material-color rendering.
Can I copy one camera's RAW profile to another?
Only if the profiling system explicitly supports that use. Camera-specific profiles should not be assumed interchangeable.
What if the gray chart matches but the product does not?
Investigate profile rendering, spectral response and product reflections rather than repeatedly adjusting white balance.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in CartVisual.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Create account and open this workspace Check pricing and creditsStart with free concept and copy planning after sign-in. Image and video generation require available credits; review the quote before starting.
Already have an account? Open the workspace.