Free tool · nothing is uploaded
LUT strength mixer
Turn a LUT down to 40% — or push it past 100% — and bake the result into the file, so the strength travels with it instead of living in your project.
Drop a .cube LUT here
Nothing is uploaded — the LUT is read and rewritten on your own device.
Opacity lives in the project. Strength lives in the file.
Almost every grading application lets you dial back a LUT — node opacity in DaVinci Resolve, effect opacity in Premiere, the mix slider in Final Cut. All of them store that number in the project, not in the .cube. The LUT on disk is unchanged, so the moment it leaves that timeline the reduction is gone.
That matters more than it sounds. A LUT loaded onto a camera monitor, into OBS for a stream, onto a phone app, or handed to a colleague has no opacity control in the chain at all. If the look needs to be gentler in those places, the only way to get it is to write the gentler version down.
What 50% actually means
A 3D LUT is a table: for this input colour, output that one. Every entry is a pair of points in colour space, and the LUT is the instruction to move from the first to the second. Strength is simply how far along that line you stop.
At 0% nothing moves and the table becomes the identity transform. At 100% every colour lands exactly where the LUT specified. At 50% each one travels half the distance — which is not the same as fading the graded image over the original, though the two agree closely for most looks, and differ where the LUT does something non-monotonic.
Dialling a LUT back in each application
If the look only has to be gentler in one timeline, do it here — it is faster than rewriting the file:
DaVinci Resolve
Apply the LUT on its own node, then drag Key → Key Output → Gain down. Node opacity, not the LUT.
Premiere Pro
Lumetri Color → Creative → Look, then the Intensity slider directly beneath it.
Final Cut Pro
Custom LUT effect → Mix.
Photoshop
Colour Lookup adjustment layer, then the layer's own opacity.
OBS, camera monitors, phone apps
No mix control exists. This is the case the tool is for — the reduction has to be baked into the file.
The full walkthrough for Resolve, including where the LUT folder lives and why Update Lists matters, is in the DaVinci Resolve guide.
After you have the gentler version
- Check what changed — put both versions through the viewer and compare the neutral-axis curves. A reduced LUT should be the same shape, flatter.
- Resize it for the destination — camera monitors and hardware LUT boxes usually cap at 17³.
- Turn it into a Lightroom preset — a look at 50% is often far easier for a preset to follow than the same look at full strength.
Frequently asked questions
Why not just lower the node opacity in Resolve?
Do, if the LUT only ever runs in that project. Opacity is a property of the node, not the file, so it does not travel: send the LUT to a collaborator, load it into OBS, or push it to a camera monitor and you get it back at full strength. Baking the reduction into the file makes the weaker version the LUT itself.
How is the strength calculated?
Each of the LUT's entries is moved along the straight line between where that colour started and where the LUT sends it. At 0% every entry sits at its input value, which is the identity transform; at 100% it sits exactly where the LUT put it. 40% means each colour travels 40% of that distance. This is the same interpolation a grading application performs at playback, done once and written down.
Does reducing strength lose quality?
No, and it often gains some. The output grid is the same size as the input, and blending toward the identity moves values closer together rather than further apart, so quantisation error shrinks rather than grows. A 50% LUT is a smoother transform than the original.
What does going above 100% do?
It extrapolates: colours continue past where the LUT put them, along the same line. This is genuinely useful for a look that is too timid, but it is not what the author designed, and channels clamp at 0 and 1 rather than wrapping. In practice that means highlights and saturated colours flatten first. The preview is the check.
Can I do this to a .3dl or a Lightroom preset?
Convert first. The 3DL ↔ CUBE tool brings an Autodesk .3dl across, and CUBE to XMP goes the other way to a Lightroom preset. A preset does not need this tool at all — its sliders are already editable.
Is my LUT uploaded?
No. The file is read with the browser's File API, the blend runs on your CPU and the preview renders on your own GPU. Nothing is transmitted.
How do I adjust LUT strength in DaVinci Resolve?
Put the LUT on its own serial node, then open the Key tab and pull Key Output → Gain down: at 0.4 you get the LUT at roughly 40%. Resolve has no LUT opacity slider as such, which is why the node-level workaround is the standard answer. It only affects that node in that project, so if the reduced look needs to leave Resolve, bake it into the file here instead.
Where is the LUT intensity slider in Premiere Pro?
Lumetri Color → Creative → Look. Pick the LUT in the dropdown and the Intensity slider sits directly underneath it, 0 to 100. Premiere's Basic Correction tab also has an Input LUT slot, but that one has no intensity control at all — it is meant for technical log conversions rather than looks.
Is this LUT strength tool free?
Yes — no account, no watermark, no export cap. The blend runs in your browser rather than on a server, so there is no cost to pass on.
A LUT tells you nothing about how it was built.
That is the trade you accept when you bake one: thirty-five thousand answers and no record of the question. The Studio works the other way round — give it a photograph and its recipe and it shows the edit as a sequence of decisions, each one rendered on its own.