Why your presets look different on every camera

You buy a preset pack. It looks great on the creator's sample images. You apply it to your own photos and something's off — the skin tones are too warm, the greens are muddy, the shadows have a colour cast that wasn't there before.

You're not doing anything wrong. The problem is that every camera sensor sees colour differently, and conventional presets don't account for that.

Every sensor has an opinion about colour

A camera sensor is covered in millions of tiny photosites, each filtered through red, green, or blue microlenses. The exact spectral response of those filters — how much of each wavelength they let through — varies by manufacturer and even by model.

A Canon sensor and a Sony sensor, pointed at the same scene under the same light, will record measurably different raw values for the same colour. The reds are a bit different. The greens are a bit different. It's subtle, but it's real.

When you open those raw files in Lightroom, Adobe applies a default profile to interpret the raw data. That profile is camera-specific — Adobe maintains one for every supported camera body. This gets you to a reasonable starting point, but it doesn't eliminate the differences between sensors. It just gets each camera into the same ballpark.

Presets assume every camera starts at the same place

A Lightroom preset is a list of slider values. "Set exposure to +0.3, contrast to +15, orange hue to +5." These values are absolute — they don't adapt to the image or the camera that captured it.

If a preset was built on a Fuji raw file and you apply it to a Canon raw file, the starting colours are different. "Orange hue +5" means one thing when the underlying orange is slightly warm (Fuji) and something else when it's slightly cool (Canon). Multiply that across every colour channel, every slider, and the differences add up.

This is why the same preset can make skin tones glow on one camera and look flat or muddy on another. It's not the preset's fault — it just wasn't built for your sensor.

The problem compounds with film emulations

Film emulation presets are especially sensitive to this. Real film stocks have precise colour responses — Portra's warm skin tones, Ektar's saturated reds, CineStill's blue cast under daylight. When a preset tries to recreate these on top of an unknown sensor starting point, the result can drift significantly from the intended look.

Portrait photographers notice this most. Skin sits in a narrow band of the colour spectrum. A small shift that's invisible on a blue sky becomes very obvious on a face.

What camera-specific profiles do differently

Instead of applying the same adjustments to every camera, camera-specific profiles account for how each sensor interprets colour before applying the creative look. The correction and the look are combined into a single profile, so there's no extra step for the photographer.

The result is that "Portra 400 on a Canon R5" and "Portra 400 on a Sony A7 IV" produce the same colour output, even though the underlying sensors disagree about what the scene looked like.

This is particularly important for photographers who shoot with multiple bodies, or who switch systems and want their editing to stay consistent. It's also important for anyone following a tutorial or recipe — if the creator shot on a different camera, a camera-aware profile will get you closer to what they intended.

What to look for

If you're evaluating preset or profile packs, ask whether they account for camera differences. Most don't — they're built on one camera and sold as universal. That works well enough for subtle looks, but the more a preset pushes colour, the more sensor differences show up.

For critical work — portraits, weddings, editorial — camera-specific profiles are worth the investment. The difference is most visible in skin tones and in scenes with mixed warm and cool tones, where sensor disagreements are largest.