PresetForge vs camera profiles and film simulations
A lot of people looking for a preset actually want a profile. The two live in different places in the pipeline and behave very differently because of it.
Where camera profiles and film simulations wins
- A profile is the base rendering, so it does not fight your exposure and white balance decisions.
- Camera-matching profiles reproduce your manufacturer's own rendering — Fujifilm film simulations included — with no tuning at all.
- Profiles apply before the Basic panel, so every slider behaves normally on top of them.
- They are free, already installed, and specific to your camera's colour science.
- A profile cannot double-apply the way a preset can on an already-rendered JPEG.
Where measuring wins
- A preset reproduces a specific edit, which a profile cannot — a profile has no knowledge of what you did afterwards.
- Measured from your own before-and-after pair, so it captures decisions no manufacturer made.
- Every parameter visible and adjustable, rather than a fixed rendering you cannot inspect.
- Exports to .cube, so the same look reaches video work. Profiles do not leave the Adobe pipeline.
Set the profile first — it is the foundation. Then use a preset for what you did on top of it.
Where each one sits
When Lightroom opens a raw file, the sensor data is nearly linear and looks nothing like a photograph. The profile is what turns it into one: it defines the base colour rendering and tone response. Everything in the Develop panel — exposure, contrast, curves, colour mixer — happens on top of that.
A preset is a saved set of those Develop panel values. It is downstream. Change the profile and every preset built on the old one now produces something different, because the input to the whole chain changed.
When a profile is what you actually wanted
If the thing you want is "my raws should look like my camera's JPEGs", that is a profile question, not a preset question. Open the Profile Browser — the four-square icon next to the Profile dropdown at the top of the Basic panel — and look under Camera Matching. For Fujifilm raws, the film simulations appear here; for other manufacturers you get their standard, vivid, portrait and landscape renderings.
These are free, already on your machine, and tuned specifically to your camera's colour science. A great many people who buy a preset pack would have been happier with a camera-matching profile and a small curve adjustment.
What a profile cannot do
A profile has no idea what you did after it. If your look involves crushing the blacks, splitting the tones and pulling the greens toward yellow, no profile contains that — those are Develop decisions, and reproducing them is what a preset is for.
Profiles also cannot be measured from a pair of images the way a preset can. Building a real .dcp profile requires photographing a colour target under controlled light and running profiling software; it is a calibration exercise, not a grading one.
Using them together
The sane workflow is layered. Pick the profile that gets the base rendering closest to what you want. Then measure or build a preset for the grading decisions on top. Then adjust exposure and white balance per photo, because those belong to the frame and not to the look.
If you are extracting a preset from a before-and-after pair, make sure the "before" file is opened with the profile you intend to use in production. Measure against Adobe Color and then work in Camera Vivid, and the preset will be measuring a transform that starts somewhere you never actually start. More on this class of mistake in why your preset looks different on someone else's photo.