How to Use a LUT in Lightroom
Lightroom has no LUT panel. There is no slot to drop a .cube into, and searching the interface for one is a common way to lose twenty minutes.
That does not mean a LUT is unusable in Lightroom. There are two routes, they work differently, and the right one depends on whether you want the look fixed or editable.
Route one: install it as a profile
Lightroom Classic and Camera Raw can wrap a LUT inside a *profile*, which then appears in the Profile browser at the top of the Develop panel alongside Adobe Color and the camera-matching profiles.
This is done with Adobe's free DNG Profile Editor, or by building a profile that references the LUT. The result behaves like any other profile: it sits at the very start of the pipeline, before your sliders, and it has an amount slider so you can dial it back.
The advantage is that it is genuinely native — no round trip, no export. The limitation is that a profile is opaque. You cannot open it to see what it does, and you cannot adjust the grade inside it; you can only adjust around it.
Route two: convert the LUT into a preset
The alternative is to turn the LUT into develop settings — an .xmp preset — so that every value lands in the panels where you can see and change it.
This is an approximation, and it is important to be straight about why. A 33-point LUT holds 35,937 independent colour triplets. A Lightroom recipe holds roughly sixty parameters with fixed meanings. Most LUTs are simply not expressible in that smaller space, so the conversion recovers what it can and leaves a residual.
What it recovers is more useful than that makes it sound. The LUT's response along its neutral axis *is* a tone curve, extracted rather than guessed. Its per-channel ramps are the red, green and blue curves. The colour cast it puts on greys is split toning. For film emulations and most creative looks — which are mostly a curve plus a cast — the result is close.
What it cannot recover is per-hue remapping beyond an eight-band mixer, gamut compression, and anything with hard clipping behaviour. Log-to-Rec.709 conversion LUTs convert badly for exactly this reason: almost everything they do lives in the dimensions a preset has no words for.
Which to choose
Use a profile when you want the LUT applied faithfully and you are happy to treat it as a starting point rather than a thing to edit. Technical transforms and looks you trust belong here.
Convert to a preset when you want to learn the look, adapt it per photograph, or take one part of it and discard the rest. A preset is documentation in a way a LUT never is — it tells you the look was built from +18 contrast and a specific curve, which is knowledge you keep.
There is a third option people overlook: use both. Convert once to see what the LUT is actually doing, then decide whether the profile route is what you want.
- ·Profile — faithful, has an amount slider, opaque, applied before your edits
- ·Preset — approximate, fully editable, teaches you the look, applied as edits
- ·Neither is 'correct'; they answer different questions
What a conversion honestly costs
Any tool claiming a perfect LUT-to-preset conversion is overselling. The useful question is not whether there is error but how much, on your specific LUT.
RawCut's converter answers that by rendering the same frame twice — once through the original LUT and once through the generated preset — and putting them either side of a comparison slider, with the mean neutral-axis error reported as a number. Under about 2 in 0–255 units is excellent. Above 6 means the LUT is doing colour work a preset cannot follow, and the profile route is the better choice for that file.
Showing the residual rather than hiding it is the only defensible way to ship an approximation, and it also tells you something useful about the LUT itself.
Frequently asked questions
Does Lightroom support .cube files at all?
Indirectly. There is no LUT slot in the Develop module, but Lightroom Classic and Camera Raw can use a LUT that has been wrapped inside a profile, and profiles appear in the Profile browser with an amount slider. Lightroom CC and the mobile apps read the same profiles once they sync.
Can I convert a .cube to an .xmp preset?
Yes, with the understanding that it is an approximation. Tone curves come across exactly — they are extracted from the LUT's own response rather than fitted — while saturation and split toning are estimated. RawCut's CUBE to XMP tool does this in the browser and shows a side-by-side comparison of what the approximation cost.
Why does my LUT look wrong when I apply it in Lightroom?
Usually input mismatch. A LUT authored for Rec.709 video applied to a RAW file that Lightroom has already rendered with its own profile is being fed different numbers than it expects. Setting the profile to Adobe Standard before applying, and checking the LUT on a normally exposed frame, isolates this quickly.
Which LUTs convert to presets well?
Anything that is essentially a tone curve plus a colour cast — film emulations, contrast looks, teal-and-orange grades. These often round-trip almost exactly. Conversion LUTs and heavily hue-targeted creative grades convert poorly, because the bulk of what they do is outside the preset's vocabulary.
Where do I put an .xmp preset once I have one?
On Windows, %APPDATA%\Adobe\CameraRaw\Settings; on macOS, ~/Library/Application Support/Adobe/CameraRaw/Settings. Restart Lightroom and it appears under User Presets. In Lightroom CC you can import it directly from the presets panel.
Drop a .cube into RawCut's converter for an editable Lightroom preset — with a live comparison showing exactly what the approximation could not carry.
Turn a LUT into a preset