RAW conversion presets for product photography

Walk into any high-volume product studio and you will find the same pattern. Three thousand presets, named "FINAL_v3", "FINAL_v3_use_this", and "Anna's good one." Six photographers, each with their own folder. A retoucher who starts the day by rebuilding base settings on every file because nothing applied at ingest is trustworthy. Presets are not the problem. The lack of a single, owned, versioned preset library is.

This article is about the boring infrastructure that makes RAW conversion presets actually work in a product studio: how to organize them by product family rather than by photographer, what to lock them to, what to keep out of them, and how to test a new one before it touches production files.

TL;DR

Build presets per product family, not per photographer. One studio, one library.
A baseline preset is only valid against a specific lighting recipe, a specific ICC profile, and a calibrated monitor. Drift in any one breaks it.
A baseline contains exposure, contrast, sharpening, noise reduction, highlight/shadow recovery - and no creative look.
Capture One styles, Lightroom presets, DNG profiles, and DCP profiles do different jobs at different layers of the stack. Use the right one.
Version the library with semver, keep a change log, and name an owner. Test every change against a frozen reference set before rollout.

Why per-product-family beats per-photographer

A per-photographer preset library is a personal tool that scales to one person and breaks the moment a colleague opens the file. The retoucher cannot trust the starting point. The art director cannot trust the proof. A new photographer brings a new folder. Within a year you have presets named after people who left.

A per-product-family library inverts the dependency. The unit is the shoot configuration: ghost-mannequin tops on white, hanging knits on grey, leather goods on dark, jewelry on acrylic, footwear on white. Each family has one baseline preset. Every photographer working that family applies the same preset on tether. Every retoucher opens files that already share exposure, contrast, sharpening, and noise reduction - so their work starts at the same place every time.

The test is simple. If two photographers shoot the same product family on the same set on the same day, the raw files should look identical at ingest. If they don't, the library is per-photographer in disguise.

This matters more as volume goes up. At 200 SKUs a week the variance averages out and nobody notices. At 2,000 SKUs a week, every degree of drift between photographers becomes a retouching tax measured in hours per day. The photographer's role page covers this in the broader context of throughput; the preset library is the operational expression of it.

What each tool actually does

People talk about "presets" as if it were one thing. In product photography you are working with at least four distinct artifacts, and they apply at different layers.

DCP profiles (DNG Color Profiles) describe how raw sensor data maps to color. They are camera-specific, illuminant-aware (typically dual-illuminant for D65 / StdA), and they are what Adobe Camera Raw and Lightroom load as "Camera Profile." Adobe's DNG Profile Editor is the tool that produces them. A DCP made from a ColorChecker shot under your studio's lighting is the foundation everything else sits on. Build it once per camera body × lighting recipe pair, validate it, and freeze it.

Capture One ICC profiles are Capture One's equivalent - a per-camera, per-illuminant color characterization. Capture One Pro ships with one or more profiles per supported body and lets you build custom profiles via its color editor and ColorChecker workflow. The Capture One color management documentation is the canonical reference. As with DCP: build it once per body × lighting, validate it, freeze it.

Capture One styles are a stack of slider settings - exposure, contrast, levels, curves, clarity, sharpening, noise reduction - that get applied on top of the ICC profile. This is where your baseline preset lives in Capture One.

Lightroom presets are the same idea on the Adobe side: a stack of slider values applied on top of the camera profile. This is where your baseline preset lives in Lightroom or Camera Raw.

The hierarchy that holds in practice:

Camera profile (DCP or Capture One ICC) - defines color. Per body × lighting. Rebuild rarely.
Baseline preset (style or LR preset) - defines the technical starting point. Per product family. Versioned monthly or quarterly.
Looks - never bundled with the baseline. See below.

Confusing the layers is how studios end up with "presets that work on my body but not on Tom's." Color belongs in the profile. Tone, sharpening, and noise belong in the preset. Keep them separate.

The minimum content of a baseline preset

A product baseline preset should contain exactly the settings that make a raw file ready for retouching. No mood, no style, no creative bias.

Exposure - set against the gray card or 18% reference under the locked lighting recipe. Typically a small offset, not zero, because the camera's metering isn't your studio's reference.
Contrast - neutral or slightly compressed. The retoucher adds contrast intentionally; the preset should not pre-decide it.
Highlight and shadow recovery - modest. Pull highlights enough to keep specular detail on metal and glass; lift shadows enough to read texture on dark fabrics. Aggressive recovery is a creative decision and belongs in a per-shot adjustment, not the baseline.
Sharpening - capture sharpening only, tuned for the body and lens combination. In Lightroom: typical radius 0.8–1.2, amount 30–50, detail 25, masking 30–60. In Capture One: diameter 0.7–1.0, amount 100–140, threshold 1–2. Output sharpening is a separate stage that happens at export.
Noise reduction - luminance NR low (10–15 in LR; 30–50 in C1) at base ISO. Color NR moderate (25 in LR; default in C1). At higher ISOs the values change - but a packshot studio shooting at base ISO under controlled strobes shouldn't need much.
Lens corrections - vignetting and CA correction enabled.
White balance - set from the white-balance reference shot under the locked lighting recipe. Same Kelvin and tint values for every file in that family.

That is the entire baseline. Notice what is not in it: tone curves, split toning, vibrance, saturation pushes, HSL adjustments, calibration sliders. Those are looks, and looks belong elsewhere.

The three locks: profile, lighting, monitor

A baseline preset is not a portable file. It is a dependent artifact, valid only in the conditions it was built for. Three of those conditions matter.

The ICC or DCP profile the preset was tuned against. If you swap to a different camera profile - including Adobe's new "Adobe Color" releases - every slider in the preset now means something slightly different, because the color it sits on top of has shifted. A preset that targets a custom DCP from your ColorChecker pass is not interchangeable with one targeting Adobe Standard. Document the profile in the preset's name or change log.

The lighting recipe. If the strobes, modifiers, and ratios change, your white reference, your shadow density, and your specular behavior all change - and the preset's exposure, recovery, and noise values are no longer correct. This is why presets and lighting recipes have to be versioned together. The lighting recipe library covers the recipe side; the preset library is the matching downstream artifact. A new recipe means a new preset version, full stop.

A calibrated monitor. The preset was tuned against what the operator saw on a calibrated display at D65, around 120 cd/m². On an uncalibrated laptop, the same preset will look "too contrasty" or "too flat" - and a photographer adjusting it on tether is now silently rebuilding the preset against a wrong reference. Tether stations and retouching displays must be calibrated on a fixed cadence. The color-managed retouching pipeline goes deeper on calibration cadence and ICC discipline.

If any of the three drifts, the preset stops being correct. The fix is not to retune the preset every time. The fix is to lock the conditions and rebuild the preset when conditions genuinely change.

Looks vs baselines - never bundle them

This is the single most common preset-library mistake. A photographer builds a baseline that is "almost right" and then quietly slides in a tone curve and a slight orange-shift in HSL because that is how the brand likes its leather goods to look. Six months later, a new brand comes in, the preset is reused, and every shot reads warm and contrasty in a way the brief did not ask for.

A baseline is technical. A look is creative. Keep them in separate files, applied in separate steps:

Baseline preset → at ingest, automatically, the same on every file in the family.
Look (a separate style or preset) → applied per job, owned by the lead retoucher or art director, never blended into the baseline.

In Capture One this is straightforward - apply a style on ingest, then a different style for the look. In Lightroom, layer two presets in a defined order. In both, keep the baseline library and the looks library in separate folders so it is impossible to confuse them.

Per-fabric and per-material exceptions

Most product families share a baseline cleanly. A few materials don't, and forcing them into the family baseline is worse than building a small exception:

Chrome and polished metal - specular highlights need less highlight recovery, more careful exposure, and minimal clarity. A "metal" exception preset overrides only those settings.
Velvet and dark wool - shadow recovery turned down, noise reduction luminance slightly higher because shadow noise reads more on absorbing fabrics.
White-on-white - exposure offset pushed slightly hot, contrast neutral, highlight recovery modest. The risk is clipping detail on white seams.
Dark-on-dark (black on black, navy on charcoal) - exposure normal, but a small lift in shadows to keep separation; sharpening masking pushed up to avoid amplifying shadow noise.

Treat these as modifier presets stacked on top of the family baseline, not as standalone presets. That way the baseline remains the source of truth and the exceptions are documented as overrides.

Versioning, ownership, and the change log

A preset library that nobody owns will rot inside six months. The discipline that holds:

Semver naming. tops-white-1.2.0 means major 1, minor 2, patch 0. Major changes when the lighting recipe or ICC profile changes. Minor changes when the preset is intentionally retuned. Patch for small fixes.
A change log per preset. What changed, why, who approved, against which reference set it was tested. A short markdown file in the preset folder is enough.
One owner. Senior retoucher or color lead - not a photographer, not the producer. Color and tone decisions are craft decisions; the owner has the authority to refuse changes that are not justified.
A frozen reference set. Twenty to fifty raw files per product family, captured under the canonical lighting recipe, that every new preset version is tested against before rollout.

The reference set is the test that prevents drift. When tops-white-1.2.0 is proposed, you batch-apply it to the reference set, eyeball the deltas against 1.1.0, confirm the change is the change you intended, and only then publish. If the diffs include things you didn't mean to change, the preset is wrong.

How to test a new preset before rolling it out

A repeatable test loop, before any new version touches production:

Apply the candidate to the frozen reference set, in batch, in a parallel session.
Compare side-by-side with the previous version on a calibrated display. Watch for unintended shifts in white balance, shadow density, and highlight rolloff.
Sample-retouch three to five files through the full pipeline. The point is to catch knock-on effects in retouching that a side-by-side preview won't reveal.
Validate against the ColorChecker reference workflow. A neutral patch should still be neutral; the standard color patches should sit within Delta E 2.
Get sign-off from the owner, log the change, and bump the version.

Skipping any step is how a "small fix" becomes a week of unexplained reshoot requests. Doing all five takes an hour for a typical preset change. That hour is the cheapest insurance the studio can buy.

What good looks like

A product studio with a working RAW preset library has, in practice:

One library, one owner, one change log.
Presets named by product family, versioned with semver, applied automatically at tether ingest.
A camera profile (DCP or Capture One ICC) per body × lighting recipe, validated against a ColorChecker, frozen.
Baselines that contain exposure, contrast, sharpening, noise reduction, recovery - and nothing creative.
Looks kept in a separate library, layered on top per job.
A frozen reference set that every new version is tested against.

If even half of those are missing, the library is doing less work than the team thinks it is, and the retouching queue is paying for it. If you want a second pair of eyes on what your library is actually delivering - what it locks to, where it drifts, what to consolidate - we will walk through it with you and give you a concrete remediation list.