Three years ago I graded a short documentary shot on two cameras, a URSA Mini and a client's Sony FX3, and dropped the same film emulation LUT on both. The Sony clips turned orange in the shadows within 4 minutes of grading. The URSA clips looked fine. That mismatch is the real lesson behind how to use LUTs in DaVinci Resolve: a LUT is not a filter you drop on top and forget. It's a color transform built for a specific input, and if that input doesn't match, every node downstream inherits the mistake.
This guide covers where Resolve stores LUT files, how to install and apply them correctly, why they sometimes vanish from the browser, how to blend intensity without a plugin, and where LUTs quietly break once you leave Rec 709. Correct before you grade is the whole philosophy behind the beginner color grading workflow, and it matters twice as much once a LUT enters the node tree.
Where DaVinci Resolve Stores LUT Files on Mac and Windows
DaVinci Resolve reads user-installed LUTs from the LUT folder tied to that specific install. On a normal desktop install, the folder location is predictable by operating system. On App Store or sandboxed installs, Resolve can point at a different container path instead. The safest route is Project Settings, then Color Management, then Lookup Tables, then Open LUT Folder, because that button opens the exact folder Resolve is actually reading from.
On a standard Mac install, that folder is usually /Library/Application Support/Blackmagic Design/DaVinci Resolve/LUT/. On Windows, it's usually C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\LUT. ProgramData is hidden by default on most Windows installs, so the Open LUT Folder button is still the cleaner way to get there than digging through File Explorer.
I've set this up on 11 different edit bays this year, some with Resolve installed straight from Blackmagic's site, one from the Mac App Store. Clicking Open LUT Folder still beats typing a file path from memory every time, and it works regardless of which install you're on.
How to Install a LUT in DaVinci Resolve's Color Management Settings
Once you're in the LUT folder, installing is just a copy and paste. Drag your .cube files in directly, or create a named subfolder first if you're managing more than 7 or 8 LUT packs. Camera-matching LUTs in one folder, creative looks in another, keeps the browser from turning into a junk drawer.
Back in Resolve, click Update Lists in that same Color Management panel, or right-click inside the LUT Browser on the Color page and choose Refresh. Skip this step and the files sit in the folder but never appear in the software. It's the single most common reason a freshly installed LUT doesn't show up, and it has nothing to do with the file itself.
Most tutorials tell you to drop the files into the OS folder and restart Resolve entirely. That works, but it's slower than clicking Refresh, and closing a project mid-grade to chase a missing LUT is its own kind of frustrating.
Applying a LUT to a Node in DaVinci Resolve's Color Page
LUTs in DaVinci Resolve belong on nodes, not on clips directly, at least not if you want to keep adjusting them later. On the Color page, right-click inside the Node Editor, go to Add Node, and add a Serial node. Right-click that new node, hover over 3D LUT, and pick your LUT from the list. Or open the LUT Browser in the top-left toolbar and drag your LUT straight onto the node.
You can technically apply a LUT at clip level from the thumbnail menu, but for most grading work I avoid that. A node-level LUT is easier to bypass, trim with Key Output Gain, move earlier or later in the tree, and compare against the correction before it. Clip-level LUTs can make sense for a consistent camera transform applied across many shots at once, but they get harder to adjust shot by shot once the grade gets more complex.
Once the LUT sits on its own node, everything else in this guide, blending, node order, troubleshooting, gets easier to control. The nodes explained guide covers serial, parallel, and layer node behavior in more depth than this section needs.
Technical LUT vs Creative LUT in DaVinci Resolve
A technical LUT solves a color management problem. It converts a known input, such as a specific log camera profile, into a normal working or delivery space like Rec 709. A creative LUT solves a look problem. It adds contrast, color bias, film emulation, or a stylized palette after the image is already in a usable state.
Using a creative LUT as if it were a technical conversion LUT is where beginner grades fall apart. The footage may look more contrasty right away, but the white balance, exposure, and color space underneath are still wrong. On the documentary I mentioned earlier, that's exactly what happened with the Sony FX3 clips: the LUT was doing creative work on footage that still needed a technical conversion first.
Where to Place the LUT Node in a DaVinci Resolve Node Tree
Ask 5 colorists where a LUT node should sit and you'll get 5 different node trees back. Some put a technical log-to-Rec709 LUT first, before any correction, because that's what the LUT expects as input. Others put creative LUTs last, after primary and secondary work, so the look sits on top of a corrected image instead of a raw one.
Here's the part most tutorials skip. Resolve's own documentation describes a LUT applied to a node as imposing its transform after that node's own color and contrast adjustments. That means if a LUT clips your highlights too hard, you don't need a separate node to fix it. You can pull down that same node's contrast or gain, and the LUT reacts to the corrected image rather than the raw one. Colorists have argued over the "right" node order on Blackmagic's own forum for years without landing on one answer.
There isn't a universally correct position for a LUT node. That's the actual takeaway, not a disappointing dodge. Corrective LUTs tend to go early, creative ones tend to go late, and the reason behind the choice matters more than the rule itself.
Best Node Order for LUTs in DaVinci Resolve
For most beginner grades, keep the LUT on its own node and pick one of these orders as a starting point:
- Technical LUT workflow: input correction or CST, then the technical LUT, then primary correction, then secondary corrections, then the creative look.
- Creative LUT workflow: primary correction, then contrast and saturation, then skin or subject fixes, then the creative LUT, then a final trim.
- Wide gamut workflow: working color space, then a CST into the LUT's expected color space, then the LUT, then a CST back to the working color space, then a final trim.
The important part isn't memorizing one universal node tree. It's feeding the LUT the kind of image it was built to receive.
Fixing LUTs That Won't Show Up in DaVinci Resolve
Most missing LUT problems come from forgetting to refresh the browser after copying files in. Right-click inside the LUT panel and hit Refresh, or hit Update Lists from Color Management. Check that first, always.
If refreshing doesn't fix it, check the file extension. Resolve reads .cube natively, along with 1D formats like .mga and .m3d, and .cube is the safest cross-editor format to work with. Files from other systems, such as .look or older vendor-specific LUT formats, may need conversion before Resolve lists or applies them correctly. Also confirm you copied files into the correct OS path. Mac and Windows use different folder structures, and a shared drive mounted at the wrong path won't correct itself.
One wrinkle that catches people out: if you installed the free version of Resolve through the Mac App Store rather than Blackmagic's own site, Apple's sandboxing rules can put your LUT folder in a different, app-contained location than the standard path listed above. It's worth checking Resolve's own Color Management panel for the actual folder location on that install rather than assuming the standard Library path applies.
Blending LUT Intensity with DaVinci Resolve's Key Output Gain
A LUT applied at full strength almost always looks too heavy, especially on footage shot in mixed lighting. Resolve doesn't have a dedicated opacity slider for LUTs, but the workaround is built in. Select the node carrying your LUT, open the Key tab, and find Key Output. Lower the Gain value there and the LUT blends toward the underlying image instead of fully replacing it. Push it back up and the look intensifies. This is the closest thing Resolve has to LUT opacity for a node. It doesn't change the LUT file itself; it changes how strongly that node's output mixes back into the image.
I dial most film emulation LUTs down to somewhere around .34 to .4 gain. Anything above .55 tends to read too aggressive on skin tones, at least on the cameras I shoot with regularly.
One caveat worth knowing before you rely on this daily: for Resolve's own built-in film-look LUTs, which expect Cineon log input rather than a normalized image, lowering Key Output Gain doesn't behave as a clean opacity blend on its own. Colorists on Blackmagic's forum found you need to group the Color Space Transform node and the LUT into a compound node first for the gain slider to trim the look correctly, rather than just fading a prior adjustment. For everyday creative LUTs built for Rec 709 input, the simple version works fine.
DaVinci Resolve LUTs and Wide Gamut Color Management
This is where most LUT problems that look like bugs are actually color science doing exactly what it's built to do. A LUT built for Rec 709 input, including several of Resolve's own bundled film-look LUTs, expects footage already normalized to that space. Apply it directly inside a timeline set to DaVinci Wide Gamut, and the result can look blown out or oddly desaturated, because the LUT reads wide-gamut values as if they were already Rec 709.
The fix is a Color Space Transform node on each side of the LUT: one before it, converting your working space down to what the LUT expects, and one after, converting the result back up to your wide gamut timeline. Colorists troubleshooting this exact issue on Blackmagic's forum confirmed the overblown look disappears once both CST nodes are in place, though the resulting saturation can still read a touch flatter than the same LUT run on a native Rec 709 timeline.
If a project delivers to Rec 709 anyway and leans on stock film LUTs, some colorists skip DaVinci Wide Gamut for that project entirely rather than manage CST nodes around every LUT. It's not the textbook answer, but for a short turnaround job, it's the practical one.
One check before you add anything: if the project is already running DaVinci YRGB Color Managed, look at whether Resolve is handling the input and output transform for you before you stack extra CST nodes on top. Doubling a transform that's already happening automatically causes the same kind of broken image as missing one entirely.
Fixing Banding When You Stack LUTs in DaVinci Resolve
Stack more than one LUT on a demanding source, heavily compressed 8-bit footage especially, and you may start seeing banding in gradients that wasn't visible in the original file. One documented case on Blackmagic's forum showed severe banding in Resolve using the same stacked LUTs that produced a clean image in After Effects on identical footage.
Before assuming your footage is the problem, check Color Management and look at 3D Lookup Table Interpolation. Switching it from the default to Tetrahedral resolved the issue for the colorist in that thread, and it costs nothing to try since it's a single dropdown. It's not an officially documented fix for every case, but it's the first thing worth checking before you start denoising or re-encoding source files that were never actually broken.
Creating a Custom LUT in DaVinci Resolve
Once you've built a grade you want to reuse, right-click the clip's thumbnail in the Color page and select Generate LUT. Choose 17-point for something light, meant for on-set monitoring rather than final grading, 65-point for maximum detail on raw or log footage, or 33-point, which most colorists treat as the standard middle ground for general use.
This entire workflow, installing, applying, blending, and generating your own LUTs, works in the free version of DaVinci Resolve. None of the core LUT tools sit behind the Studio paywall. If you're still deciding which version fits your workflow, the free vs Studio breakdown covers where the real gaps actually are, and LUT support isn't one of them. The same LUT logic now extends to stills too, since the Resolve 21 Photo page uses the identical LUT browser and node structure.
One exception worth knowing: third-party tools like Nobe LutBake, which export a LUT with a single hotkey straight from the grading interface, do require Resolve Studio specifically because they hook into Resolve's external scripting API. That's a limitation of the plugin's own connection method, not of Resolve's native Generate LUT feature.
DaVinci Resolve LUT Questions Editors Ask
Are LUTs free to use in DaVinci Resolve?
Yes. Installing, applying, blending, and generating your own LUTs from a grade are all available in the free version. Resolve ships with a set of built-in film-look and technical LUTs at no cost, and third-party .cube files install the same way regardless of which version you're running.
Can I use LUTs made for Premiere Pro in DaVinci Resolve?
Most of the time, yes. The .cube format is the industry standard and reads natively across Resolve, Premiere Pro, Final Cut, and most other editors. LUTs saved in Premiere's proprietary .look format need converting first, since Resolve doesn't read that extension directly.
Should a LUT go on a single clip's node or the whole timeline?
It depends on the project. A technical LUT can go on a group node or a shared clip setup when every shot uses the same camera profile and exposure approach. On a mixed-camera timeline, apply technical LUTs per camera group or per clip instead of blindly across the whole timeline, since one camera's conversion can break another camera's footage. Creative look LUTs are usually safer applied per clip, per scene, or on a controlled group or timeline node once the footage underneath has already been normalized.
What's the difference between a 1D and 3D LUT in DaVinci Resolve?
A 1D LUT maps a single input value to a single output value, useful for basic adjustments like contrast or individual channel levels. A 3D LUT works across red, green, and blue simultaneously, which is what lets it shift hue and saturation together instead of brightness alone. Resolve supports both, though almost every cinematic or film-emulation LUT you'll download is 3D.
Why does my LUT look wrong in DaVinci Resolve?
Usually because the LUT is being fed the wrong input. A Rec 709 creative LUT applied to log footage, RAW footage, or a DaVinci Wide Gamut timeline can look blown out, washed out, oversaturated, or oddly flat. Normalize the footage first with color management, a Color Space Transform, or the correct technical LUT before the creative LUT goes on.
How do I reduce LUT strength in DaVinci Resolve?
Put the LUT on its own node, open the Key tab, and lower Key Output Gain. This works like LUT opacity for most everyday creative LUTs, though some of Resolve's own built-in film-look LUT workflows need the CST and LUT nodes grouped into a compound node first before the blend behaves the same way.
Should I use a LUT or a Color Space Transform in DaVinci Resolve?
Use a Color Space Transform, or Resolve's color management, for controlled color space conversion. Use a technical LUT only when it matches your exact camera and profile. Save creative LUTs for later in the node tree, after exposure, white balance, and contrast are already corrected.
This guide is part of the Color Grading hub: nodes, scopes, LUTs, and color management, in the order worth learning them. Once the grade is locked, export normally; the export settings guide covers Deliver page settings for the final render.
Related guides
- Color Grading in DaVinci Resolve: the hub: where LUTs fit in the full grading path.
- How to Color Grade in DaVinci Resolve: Beginner Tutorial: the correction-first workflow to run before any LUT.
- DaVinci Resolve Nodes Explained: the node tree logic behind LUT placement.
