# DaVinci Resolve Color Wheels Greyed Out: The Fix

> **Quick answer:** DaVinci Resolve's color wheels grey out for three reasons: no clip selected on the Color page, the wrong palette tab open (often Camera RAW), or the active node disabled. Select a clip, click the Color Wheels icon, then check for a bypassed node (Ctrl/Cmd-D) or the global bypass toggle (Shift-D) before assuming anything is broken.

*Published by [TryUncle](https://tryuncle.com) — the AI tutor that teaches DaVinci Resolve on your own screen.*
*Updated 2026-07-18 · DaVinci Resolve 21.0.2 (July 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-color-wheels-greyed-out*

Your clip is right there in the filmstrip. You click it, open the Primaries palette, and the wheels just sit there, flat and grey, doing nothing when you drag them. No color ring. No response. It looks like DaVinci Resolve broke something, and the panic that follows is completely reasonable, because grading is the whole point of the Color page.

It's almost never broken. In the overwhelming majority of real reports, this comes down to one of three things: nothing is actually selected for the wheels to grade, you're looking at a different palette tab than you think you are, or the node underneath your cursor is switched off. This guide walks through those three first, in the order that solves the problem fastest, then covers every rarer cause with documented evidence behind it, from Collaboration locks to a single corrupted node that refuses to activate.

## Why do DaVinci Resolve's color wheels turn grey?

The Primaries palette, the Lift, Gamma, Gain, and Offset wheels most people mean when they say "color wheels," isn't a standalone tool. It's a window into whatever node, on whatever clip, currently has focus on the Color page. When that chain breaks, the wheels don't show an error message. They just go flat and stop responding, because from Resolve's point of view, there's genuinely nothing for them to control right now.

That chain has exactly three links, and each one fails in a distinct, recognizable way:

- **No clip selected.** The Color page shows nothing until you click a clip in the filmstrip. This is the single most common cause, and it's the one every other troubleshooting step assumes you've already ruled out.
- **Wrong palette tab.** The wheels share a toolbar with Camera RAW, the RGB Mixer, Curves, Qualifier, Sizing, Tracker, and other tools. Clicking the wrong icon swaps the entire panel, and the tab you actually want, Camera RAW especially, has its own separate reasons for looking locked.
- **Disabled or bypassed node.** Every node in a clip's node graph can be individually switched off without deleting it, and DaVinci Resolve also has a single button that switches off every grade on the entire timeline at once. Both leave the wheels technically clickable but functionally dead.

**DaVinci Resolve's color wheels don't grey out at random. They grey out because the page has nothing selected to grade, the wrong palette tab is open, or the active node is switched off.** Every other cause in this guide, Collaboration locks, Group modes, Output Sizing, a single corrupted node, is a variation on one of those three, and rarer by a wide margin.

Here's the fast diagnostic table. Match your symptom to a row, then jump to that section.

| What you're seeing | Likely cause | Where to check |
| --- | --- | --- |
| Wheels flat grey, filmstrip shows no highlighted clip | Nothing selected | Click a clip thumbnail in the filmstrip |
| Wheels work fine but the panel above them shows locked RAW sliders | You're on the Camera RAW tab, not Primaries | Click the Color Wheels icon in the palette row |
| Wheels drag fine but the image never changes | A disabled or bypassed node | Node graph, look for a slashed node number |
| Nothing on the whole timeline grades, on any clip | Global bypass active | Small icon, top right of the Color page viewer |
| Wheels look like vertical sliders, not round dials | You're in Bars or Log mode, not Wheels mode | Mode button above the palette, or Option-Z / Alt-Z |
| Palette read-only, someone else is grading the same project | Collaboration clip lock | Confirm with your team, or wait |
| You changed a setting and now a totally different grade shows | Group Pre-Clip or Post-Clip mode active | The dots above the node graph |
| Nothing above explains it | Output Sizing mode, or one corrupted node | Sizing palette, or rebuild the specific node |

## Is a clip actually selected on the Color page?

Start here, every time, before you touch a single setting. It sounds too simple to be the actual answer, and that's exactly why it gets skipped.

Editor and trainer Larry Jordan states the underlying rule directly in his walkthrough of the Color page: **"To make a primary adjustment for a clip, you need to first select the clip."** That's not a tip. It's the entire mechanism the wheels run on. There's no global "current grading state" floating independently of a specific clip and node. The Primaries palette is always, without exception, showing you the node that's currently active for the currently selected clip, and with no clip selected, there's no node for it to represent.

A few ways this trips people up in practice:

1. **You switched to the Color page from Edit or Cut, and nothing carried over.** Resolve doesn't automatically select whatever clip your playhead happened to be over on the previous page. Click a thumbnail in the Color page's filmstrip explicitly.
2. **Your playhead sits on a gap, not a clip.** An empty space on the timeline, a transition still rendering, or a track you've scrolled past all look similar to a genuinely selected clip at a glance, but none of them give the wheels anything to grade.
3. **You clicked a track header or a timeline ruler instead of a thumbnail.** These select the timeline itself, not an individual clip, and the wheels stay inactive until you click directly on a clip's thumbnail in the filmstrip below the viewer.
4. **You're mid-drag on the timeline and released the mouse over nothing.** A failed drag-select can deselect everything without giving any obvious visual feedback that anything changed.

The fix is the same in every case: click directly on a clip's thumbnail in the Color page's filmstrip, and confirm it highlights. Once it's selected, the wheels should immediately populate with whatever grade already exists on that clip's current node, even if that grade is just the untouched default.

**A DaVinci Resolve color wheel with nothing selected isn't malfunctioning, it's accurately showing you that there's currently no clip and no node for it to control.** This single check resolves more "broken wheels" reports than every other cause in this guide combined, which is exactly why it's the first thing worth ruling out, not the last.

If the filmstrip itself looks empty, no thumbnails at all, rather than just unselected, that's a different problem from the one this guide covers. Our guide on [DaVinci Resolve's Color tab not showing footage](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-color-tab-not-showing-footage) walks through the timeline filters, track toggles, and cache issues that cause that specific symptom.

## Are you looking at the Color Wheels tab, or did you land on Camera RAW by accident?

This is the second-most-common false alarm, and it's specifically confusing because both tabs live in the exact same toolbar, one click apart, and both can genuinely look locked and grey at the same moment for completely unrelated reasons.

DaVinci Resolve's Color page keeps a row of palette icons above the main tool area: Primaries (the wheels), RGB Mixer, Motion Effects, Sizing, Tracker, Qualifier, Windows, Blur, Key, Curves, and, when it's relevant, Camera RAW. Clicking any one of those icons swaps out the entire panel below it. If you clicked Camera RAW instead of Primaries, possibly out of habit from a previous project, everything you're looking at belongs to a completely different tool, and it has its own, unrelated set of rules for when it's active.

The Camera RAW tab only comes alive for clips DaVinci Resolve has identified as native camera raw footage. On the Blackmagic Forum, technical support representative Dmitry Kitsov explained the rule plainly to an editor whose Camera Raw tab was greyed out in Resolve 12 Studio: **"this tab is only accessible for those clips that are original camera raw material."** A ProRes file, an H.264 export, or footage that's already been transcoded from raw into a delivery codec will never unlock that panel, no matter what you click, because there's genuinely no raw metadata underneath it to adjust.

This isn't a bug people occasionally hit. It's shown up in the exact same shape for over a decade of Resolve versions. On Creative COW, editor Ian Lin reported that "all of the camera raw settings buttons are un-clickable" in the color panel. Fellow editor Juan Salvo's reply cut straight to the actual question: **"Well, do you have raw camera footage?"** In a separate thread, editor Matthew Jeschke described the Camera RAW pane as fully locked after trying reboots, new projects, and a reinstall, none of which touched the real cause. Editor Peter Chamberlain identified it immediately: **"Your clip needs to be RAW before these controls are active. In the pix you posted its ProRes."** Jeschke eventually traced his own case to a raw-to-DNG converter that was mislabeling the codec on export, and switching converters fixed it.

Here's the distinction worth burning into memory:

| Symptom | What's actually happening |
| --- | --- |
| Color Wheels tab selected, wheels themselves grey and unresponsive | A genuine wheels problem: no clip selected, or a disabled node |
| Camera RAW tab selected, sliders locked and greyed | Expected behavior for non-raw footage, not a bug at all |
| Both tabs look fine, but the image never actually changes | The node is bypassed, or the global bypass toggle is on |

If your clip genuinely is raw footage and the Camera RAW tab is still locked, the fix that resolved it for both editors above was checking the decode source. Per the Blackmagic support reply in that same thread: **"If some of the settings are not available change the 'decode using' from project to clip."** That single dropdown, set to Clip instead of Project, unlocks options that Project-level decoding sometimes leaves restricted.

**The Camera RAW tab and the Color Wheels tab sit one click apart on the Color page's palette row, and confusing the two is the single most common reason someone thinks their wheels are broken when only the RAW panel is locked.** If you're not sure which one you're looking at, the wheels are round dials labeled Lift, Gamma, Gain, and Offset. The RAW panel is a column of sliders and dropdowns labeled things like ISO, Color Temp, Tint, and Exposure. They don't look alike once you know what to look for.

## Is the node you're grading on disabled or bypassed?

You've confirmed a clip is selected, and you're definitely on the Primaries tab, wheels visible, round dials, the whole thing. You drag Gain up. Nothing happens in the viewer. This is a different problem than the two above, and it's a node problem specifically.

Every node in a DaVinci Resolve node graph can be individually turned off without deleting it, a genuinely useful feature for before-and-after comparisons or walking a client through a grade step by step. Per the DaVinci Resolve manual's page on disabling nodes, you select a node and choose **Color > Nodes > Enable/Disable Selected Nodes**, mapped to Cmd-D on a Mac or Ctrl-D on Windows, and **"disabled nodes are not processed during rendering."** That's the key detail: a disabled node doesn't just look different, it's fully excluded from the image, as if it were never in the tree at all. If the wheels you're dragging belong to a disabled node, you're adjusting values that Resolve is actively ignoring.

There's a second, broader version of the same command. Choosing **Color > Nodes > Enable/Disable All Nodes**, Option-D on Mac or Alt-D on Windows, toggles every node in the current clip's tree at once. The manual is specific about what happens when you toggle it back on: **"every node is re-enabled, even nodes that had previously been individually disabled."** That's worth knowing before you use it as a quick "did I break something" test, since it can silently undo an intentional individual disable you'd forgotten about.

Visually, a disabled node shows a diagonal line or a dimmed appearance through its number in the bottom corner of the node's thumbnail in the node graph. It's easy to miss if you're focused on the wheels themselves rather than scanning the tree above them, especially on a node graph with a dozen nodes stacked together.

**A DaVinci Resolve node graph can have twelve nodes and eleven of them can be broken, and the color wheels will still work perfectly on the one node that's actually selected and enabled.** This is why "the wheels aren't working" and "the whole clip's grade isn't working" are actually two separate questions. Selecting a different, enabled node while the disabled one sits untouched elsewhere in the tree brings the wheels right back to life, because they were never broken. They were just pointed at a node Resolve had switched off.

One more variant worth knowing: on the Blackmagic Forum, in a thread titled ["Color wheels have no effect?"](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=213933), an editor described adjustments visible on the wheels and the curve panel, moving and responding to input, with zero effect on the actual image. The most likely cause raised in that thread was the same one covered here: a bypass on the specific node in use. The wheels themselves aren't disabled in that scenario, which is why they still visually move, but the node holding them has been excluded from the render, so nothing you do to it reaches the final image.

**Disabling a node in DaVinci Resolve does not delete anything it holds, it just removes that node from the render, which is why re-enabling it brings your entire grade back exactly as you left it.** Re-enable with Cmd/Ctrl-D on the specific node, or Option/Alt-D if you suspect the whole tree got switched off together, and confirm the wheels reflect a change the moment you drag them.

## Is DaVinci Resolve's global bypass toggle switched on?

There's a fourth cause that looks identical to a disabled node from the wheels' point of view, but it's a completely different control, and it affects your entire timeline at once rather than one node on one clip.

DaVinci Resolve has a single button, positioned at the top right of the Color page's viewer, called Bypass Color Grades and Fusion. Per the manual, it exists to **"turn off all grades and effects that you may have applied in the Color page and/or Fusion page in order to improve playback performance on low power computers."** Its keyboard shortcut is Shift-D, on both Mac and Windows. Click it once, or hit Shift-D, and every grade on every clip on the entire timeline stops rendering simultaneously, which for someone who doesn't know the button exists looks exactly like the whole project's color grading silently broke all at once.

The tell is in the icon itself. When bypass is active, that small icon in the top right of the viewer shows visibly different styling, and hovering or right-clicking it surfaces a menu confirming its state. The manual notes you can right-click the button to open a menu that lets you **"choose which things you want this button to control,"** since it can be scoped to color grades only, Fusion effects only, or both together.

This is genuinely easy to trigger by accident. It sits close to other frequently used viewer controls, and on a laptop trackpad or a control surface with unfamiliar key mapping, Shift-D is an easy combination to hit without meaning to. If you're not the only person who's touched the project recently, a collaborator testing playback performance on a heavy timeline is a completely ordinary reason someone flipped it and forgot.

Here's how to tell a global bypass apart from a single disabled node, since both produce the identical symptom of "nothing I grade shows up":

| Test | Global bypass active | Single node disabled |
| --- | --- | --- |
| Check a second, different clip on the timeline | Also shows no grading | Grades normally |
| Check the icon top right of the Color page viewer | Shows Bypassed | Shows normal |
| Check the node graph on the affected clip | Nodes look normal | One node shows a diagonal disable line |
| Fix | Click the icon, or press Shift-D | Select the node, press Cmd/Ctrl-D |

**Shift-D turns off every grade on the entire timeline at once, which is a different button from the one that turns off a single node, and mixing the two up wastes more troubleshooting time than any other cause on this page.** Check every other clip on the timeline before you spend ten minutes rebuilding a node tree that was never actually broken.

## Could Wheels, Bars, or Log mode be the reason it looks broken?

Sometimes the wheels aren't disabled at all. They're just not there, replaced by a different layout that a new user, or anyone coming from a different piece of grading software, doesn't immediately recognize as the same tool.

The Primaries palette has three distinct display modes, and per the manual, they aren't cosmetic options, they're genuinely different control sets built for different jobs. **Wheels mode** holds "traditional DaVinci YRGB Lift/Gamma/Gain controls that allow tonally specific yet widely overlapping regions of adjustment," the round dials most people picture when they hear "color wheels." **Bars mode** offers "the same YRGB Lift/Gamma/Gain and Offset controls as the Primaries Wheels mode," except displayed as vertical sliders instead of circular dials, useful on a smaller screen or when precise numeric-feeling drags matter more than the visual balance a wheel gives you. **Log mode** replaces all of that with "Shadow/Midtone/Highlight/Offset controls that offer more restrictive yet customizable regions of adjustment intended for making adjustments to log-encoded image data," aimed specifically at flat, log-gamma footage rather than the general-purpose Rec.709 workflow Wheels mode assumes.

If you're expecting round wheels and you're staring at a column of sliders, or a set of numeric-only controls with none of the usual circular dials, you haven't hit a bug. You've landed in Bars or Log mode, and the fix is a single click, not a troubleshooting session. Per the manual, you switch between them by choosing **"an option from the mode drop-down, click[ing] the right mode button, or press[ing] Option-Z"** on a Mac. On Windows, the equivalent modifier is Alt-Z, following the same Option-to-Alt mapping Resolve uses consistently across its keyboard shortcuts.

This confusion shows up most for two groups: editors who just switched from a different NLE or grading tool with a different default layout, and editors reopening a project they, or a collaborator, left in Log mode during a previous log-footage session. Neither is a sign anything is wrong. It's the correct tool for a different job, sitting where you expected a different tool to be.

## Are you on a shared project where someone else has the clip locked?

Everything above applies whether you're working solo on a local project or as part of a team. This section only applies to one specific situation: DaVinci Resolve Studio's Multi-User Collaboration feature, where several editors and colorists work inside the same shared project database rather than each maintaining separate project files. If that's not your setup, skip ahead.

Collaboration's whole design intentionally lets more than one colorist touch the same timeline at the same time without stepping on each other's work, and on the Color page specifically, it does that through per-clip locking rather than locking the entire timeline. Author Patrick Southern describes the mechanism directly in a Pond5 blog post on Resolve's collaboration tools: **"When you select a shot in the timeline, that clip is now locked to everyone else. Changes made to that clip will be saved once the colorist selects a new clip."** He adds a detail that matters for how confusing this can feel in the moment: **"Unlike bin locking, no refresh is required to see updates to a color grade,"** meaning a lock can silently take hold and release again without any obvious notification banner telling you what just happened.

From the locked-out colorist's side, this can look exactly like a wheels bug. You click a clip, the palette looks present but doesn't respond to your drags, or your changes don't visibly stick. Nothing about your local install is broken. Someone else, possibly on the other side of the building or the other side of the world, currently has that specific clip selected, and until they click away to a different one, you're effectively looking at a read-only view of it.

Per Blackmagic Design's own Collaboration product page, this locking system runs automatically in the background: multi-user collaboration is designed so several people can work simultaneously with **"automatic bin and timeline locking"** preventing overwrites. The Color-page clip lock described above is a finer-grained layer on top of that same underlying idea, scoped down to the individual clip level specifically because two colorists working on entirely different shots in the same timeline shouldn't have to wait for each other at all.

The practical check, if you're on a Collaboration project and the wheels won't respond:

1. Confirm with your team, in whatever channel you normally coordinate through, whether anyone else currently has that specific clip open on the Color page.
2. If someone does, either wait for them to select a different clip, or ask them to move on if the change is urgent.
3. Once the lock clears, the wheels should respond immediately with no need to reopen the project or refresh anything manually.

**In DaVinci Resolve's Multi-User Collaboration, selecting a clip on the Color page locks it to you alone until you move on, and a color wheel that won't respond on a shared project is usually just waiting for someone else to let go.** This is a coordination problem, not a data problem. Nothing about the underlying grade is at risk while a lock is in place.

If the lock seems stuck well past a reasonable wait, or an entire bin refuses to open rather than just one clip, that's a broader Collaboration failure mode than what's covered here. Our guide on [DaVinci Resolve Collaboration mode timeline locked](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-collaboration-mode-timeline-locked) covers what to do when a whole timeline, not just a single clip, gets stuck locked.

## Could Group Pre-Clip or Post-Clip mode be showing you a different layer entirely?

This one doesn't literally grey out the wheels, but it produces a symptom close enough to it that it belongs in the same troubleshooting list: you drag a wheel, something changes, but it's not the change you expected, or it ripples across clips you weren't trying to touch, or a grade you know you built seems to have vanished.

DaVinci Resolve's Groups feature lets you link multiple clips together and grade them at four distinct levels: Clip, Group Pre-Clip, Group Post-Clip, and Timeline. Per the manual, Group Pre-Clip applies "a starting point for the scene," an underlying grade that affects every member of the group before any individual clip correction happens, while Group Post-Clip applies its adjustments "after the Clip adjustments," typically for a creative look layered on top of everything each clip already has individually. Critically, the manual notes that node trees built in either group mode "automatically ripple changes to every member of a group," while node trees built in plain Clip mode "are specific to each clip."

If you're working on a clip that belongs to a group, the interface adds extra dots above the node graph, letting you switch between Clip, Pre-Clip, and Post-Clip modes without leaving the page. Land on the wrong one, and the wheels are fully live and responsive, they're just adjusting a layer of the grade you didn't mean to touch, which can feel just as broken as an actual dead palette if you don't notice which mode you're in.

The fix is purely a matter of checking which of those dots is currently selected before you start dragging. If you only intended to grade one specific clip and the dots show Pre-Clip or Post-Clip highlighted instead of Clip, click back to Clip mode first. And if you're intentionally building a group-wide look and the ripple effect across every member clip is the whole point, that's expected behavior working exactly as designed, not a bug to fix.

## Is Output Sizing mode, or a single corrupted node, the rare cause?

Everything above accounts for the overwhelming majority of reports. This section covers the remainder: causes that are real, documented in actual troubleshooting threads, but genuinely uncommon compared to the ones already covered.

On the Blackmagic Forum, in a thread titled ["Color controls stopped working 15.3.1"](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=106064), an editor described every control on the Primaries palette losing its effect on the image at once. The wheels still moved. Lift, Gamma, and Gain still visually changed. The curve panel still accepted input. None of it touched the final image. Other posters in the thread walked through the two most likely explanations first: a globally deactivated grade, the same Bypass Color Grades and Fusion toggle covered earlier in this guide, and whether Output Sizing mode happened to be active, since being in that mode changes how the sizing pipeline connects input to output and can produce a similarly dead-looking result if there's no node actually bridging the two. Per the manual's own description, Output Sizing is **"an additional transform that is applied after Edit sizing, Fusion sizing, Input sizing, and Node sizing"** and functions as **"an overall adjustment that affects every clip at once."** It's a real, distinct stage in Resolve's sizing pipeline, tucked inside the Sizing palette rather than the Primaries one, and worth a glance if you've ruled out everything else and the image genuinely won't respond to any grading tool, not just the wheels specifically.

In that same thread, the original poster eventually found the actual root cause in their case: one specific node in their node tree had simply stopped activating, no matter what they clicked or how many times they toggled it. Deleting that one node and rebuilding it from scratch, rather than the whole tree, cleared the problem permanently. It's an anecdotal, project-specific fix rather than a documented, repeatable feature of Resolve, but it lines up with a pattern that shows up elsewhere too: individual project files can develop a single corrupted or orphaned node that resists every normal enable and disable command, and the fastest real fix is replacing that one node rather than troubleshooting it indefinitely.

A related, separate report on the Blackmagic Forum, in the thread ["Color wheels have no effect?"](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=213933), noted that the issue in that specific case appeared to be tied to the individual project file rather than the Resolve installation as a whole, since building a fresh test project with dummy footage worked correctly, and one poster in the thread wondered aloud whether a multicam clip setup was involved. Neither detail rises to a confirmed, documented cause the way node bypassing or a missing clip selection does, but if you've worked through every other section in this guide and you're still stuck, testing your grade inside a brand new, empty project with a single dummy clip is a fast, low-cost way to tell whether the problem is Resolve itself or something specific to that one project file.

The practical order to try these in, since they're genuinely rare:

1. Open the Sizing palette and confirm you're not in Output Sizing mode without a node actually connecting input to output.
2. Scan your node graph closely for one specific node that refuses to enable no matter what you click, distinct from the more obvious slashed-disabled state covered earlier.
3. If a single node is the culprit, delete it and rebuild the same adjustment on a fresh node rather than continuing to fight the broken one.
4. If nothing on your current project explains it, create a new test project, import one dummy clip, and confirm the wheels behave normally there. If they do, the problem is scoped to your specific project file, not your Resolve install.

## Does this happen differently in DaVinci Resolve's free version versus Studio?

For nearly everything covered in this guide, no. Node selection, node enabling and disabling, the global Bypass Color Grades and Fusion toggle, Wheels, Bars, and Log modes, and Group Pre-Clip and Post-Clip modes are all core parts of the Color page's grading architecture, and none of them sit behind Studio's paywall. A free-version editor and a Studio editor troubleshooting a dead set of color wheels are working through the exact same checklist with the exact same fixes.

There's exactly one exception, and it's the Collaboration section above. Multi-user Collaboration and its per-clip locking behavior are Studio-only features, tied to the networked project database Collaboration runs on. Per Toolfarm's comparison of DaVinci Resolve Studio against the free version, Collaboration sits on the list of features exclusive to the paid license. If you're on the free version, the shared-project lock scenario simply can't apply to you, because there's no shared-project mode to lock in the first place. Camera RAW decoding for supported raw formats and the wheels themselves are unaffected by which license you're running, though Studio does add support for a broader range of raw formats and heavier processing tools elsewhere on the Color page that aren't part of this particular problem.

If you're on the free version and you've worked through this whole guide without finding your cause, you've genuinely covered every documented scenario. There's no hidden free-version-specific quirk lurking beyond what's already listed above.

## What does the full fix look like on a real project?

Here's how this plays out in practice, walking through the checks in the order that actually solves the problem fastest for two different real-world situations.

**Scenario one.** A freelance editor opens a project handed off from a colleague, ready to do a quick color pass before delivery. They click into the Color page, select the first clip in the filmstrip, and the wheels sit there completely unresponsive.

1. **Check one: is a clip selected?** The filmstrip thumbnail is highlighted, so yes, this isn't it.
2. **Check two: right palette tab?** The wheels are round dials labeled Lift, Gamma, Gain, and Offset, correctly the Primaries tab, not Camera RAW. Also not it.
3. **Check three: disabled node?** Looking at the node graph, node 2 of 3 has a visible diagonal line through its number. That's the one currently selected, which explains everything. Pressing Cmd-D re-enables it, and the wheels immediately respond to input, with the grade that was already built into that node reappearing in the viewer exactly as the previous editor left it.

Total time: under thirty seconds, because the very first thing checked after the obvious ones was also the actual cause. That's the intended order of this guide. Node problems and missing selections account for nearly everything, and everything past them is progressively rarer.

**Scenario two.** A colorist working solo on a documentary opens the Color page mid-session and finds that not just their current clip, but every clip on the timeline, has stopped grading. Scrubbing through several other shots confirms it: nothing anywhere on the timeline shows its grade anymore, even clips they know were finished and locked days earlier.

1. **A single disabled node doesn't explain a whole-timeline failure**, so this branch of the checklist gets skipped immediately. One node, disabled or not, only ever affects the one clip it belongs to.
2. **Checking the top right of the Color page viewer** shows the Bypass Color Grades and Fusion icon in its bypassed state. Earlier in the session, testing playback speed on a particularly effects-heavy section of the timeline, they'd hit Shift-D to see how the project performed with grading turned off, and simply forgotten to turn it back on before moving to a different task.
3. **Clicking the icon once** restores every grade across the entire timeline in a single action. Nothing needed to be rebuilt. Nothing was actually broken. The whole project had just been intentionally, if temporarily, turned off.

Same starting symptom, "the wheels aren't doing anything," two entirely different causes with two entirely different fixes, and neither one required reinstalling anything or rebuilding a single node from scratch.

## Quick troubleshooting reference

Bookmark this table. Work through it top to bottom. The first three rows account for the large majority of real reports.

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| Wheels flat grey, no clip highlighted in the filmstrip | Nothing selected | Click a clip's thumbnail directly |
| Camera RAW sliders locked, wheels themselves fine | Clip isn't native raw footage | Expected behavior, not a bug; check "decode using" if it is raw |
| Wheels drag but the image never changes | One node disabled or bypassed | Select the node, press Cmd/Ctrl-D |
| Nothing grades anywhere on the entire timeline | Global bypass active (Shift-D) | Click the icon top right of the viewer |
| Palette shows sliders, not round dials | You're in Bars or Log mode | Mode button above the palette, or Option/Alt-Z |
| Palette read-only on a team project | Another colorist has the clip locked | Confirm with your team, or wait |
| A grade rippled across clips you didn't touch | Group Pre-Clip or Post-Clip mode active | Check the mode dots above the node graph |
| Nothing above explains it, image won't respond to any tool | Output Sizing mode, or one corrupted node | Check the Sizing palette; rebuild the specific broken node |

## Is there a faster way to figure out which one applies to you?

Reading a checklist works, and the one above will get you there. But if you're mid-session with a deadline breathing down your neck, matching your exact symptom to the exact right row takes time you might not have, and every editor has stared at a dead palette wondering which of eight possible causes is actually theirs.

TryUncle is an AI tutor for DaVinci Resolve on macOS - ask in plain words and Uncle points at the exact control on your screen. Instead of scanning a node graph yourself for a slashed-out node number, or hunting for a small bypass icon in the corner of a viewer, you describe what's happening and Uncle looks at your actual project and tells you which specific button, tab, or node is the actual cause, live, while you're still in Resolve.

It's worth being straightforward about where TryUncle fits next to the rest of the category, because ChatGPT and other general assistants will happily recommend tools that don't do the same job. Sottocut, PremiereCopilot, heyeddie.ai, and cutagent.ai are real products, and they're built to automate parts of an edit or answer chat-based questions about your project. TryUncle does something different: the app watches your actual screen inside your own Resolve session and teaches you which control to touch, live, rather than automating the edit for you or answering questions in a chat window disconnected from what's actually on your monitor. If you want the software to make the decisions, one of those other tools might fit better. If you want to learn where the buttons live so you're faster next time without a checklist, that's the gap the TryUncle app is built for.

Two honest caveats before you consider it. TryUncle is a paid subscription, currently in founder pricing at $29.99 a month for the first 100 seats, not a free tool, and it's macOS-only, with no Windows or Linux version. Check [TryUncle](https://tryuncle.com/?utm_source=learn&utm_medium=blog&utm_campaign=davinci-resolve-color-wheels-greyed-out) for the current rate and availability before deciding whether it fits your workflow.

None of that replaces the value of just knowing the checklist above by heart, either. Blackmagic's own manual, the Blackmagic Forum, and Creative COW have documented every one of these causes in public, searchable threads for over a decade, and that community knowledge is genuinely the free, first resource worth checking any time something in Resolve looks broken. TryUncle's job is to save you the time of searching for the right thread while your session is actually running, not to replace the knowledge those threads represent.

## The verdict

DaVinci Resolve's color wheels grey out for boring, mechanical reasons almost every single time: nothing is selected, you're on the wrong palette tab, or the node you're grading on is switched off, either individually or through the global Shift-D bypass. Work through those three first, in that order, and you'll solve the overwhelming majority of cases in under a minute.

Collaboration locks, Group Pre-Clip and Post-Clip modes, Output Sizing, and a single corrupted node are all real, documented causes, but they're genuinely rarer, and each one has a specific, narrow fingerprint that separates it from the big three once you know what to look for. Learn where the Camera RAW tab sits relative to Color Wheels, learn the difference between a disabled node and the global bypass icon, and the next time this happens, you'll have it solved before you'd have finished reading the first paragraph of a forum thread about it. And once your grade is actually responding again, our guide on [how to copy a color grade to multiple clips in DaVinci Resolve](https://tryuncle.com/learn/davinci-resolve/how-to-copy-color-grade-to-multiple-clips-in-davinci-resolve) covers how to push that finished look across every other shot in the scene without rebuilding it by hand.

## FAQ

### Why are my DaVinci Resolve color wheels greyed out?

Almost always one of three things: no clip is currently selected on the Color page, you're looking at a different palette tab like Camera RAW instead of the Color Wheels tab, or the node you're trying to grade on is disabled or bypassed. Work through those three in order before checking anything more advanced, since together they explain the large majority of reports.

### Why does clicking a clip not un-grey the color wheels?

If clicking a clip in the thumbnail timeline doesn't restore the wheels, check whether you actually selected a node in that clip's node graph. Resolve grades node by node, and the Primaries palette always reflects whichever node currently has focus. If the node graph itself looks dimmed or a node has a slash through its number, that specific node is disabled, and selecting the clip alone doesn't fix that.

### What's the difference between a disabled node and the global bypass toggle?

A disabled node, toggled with Ctrl-D on Windows or Cmd-D on Mac, turns off just that one node. The global Bypass Color Grades and Fusion toggle, Shift-D on both platforms, turns off every grade and Fusion effect on the whole timeline at once from a small icon at the top right of the Color page viewer. Mixing the two up is one of the most common causes of a wasted troubleshooting session.

### Why is only my Camera RAW panel greyed out, not the actual color wheels?

The Camera RAW tab lives right next to the Color Wheels tab on the Color page's palette row, and it only activates for clips DaVinci Resolve has identified as native camera raw footage, decoded at the project or clip level. A ProRes, H.264, or already-transcoded clip will always show a locked Camera RAW panel, and that's expected behavior, not a bug. It has nothing to do with whether your actual color wheels work.

### Can DaVinci Resolve's Collaboration mode grey out the wheels for me but not my colorist?

Yes, in a specific way. On a shared Multi-User Collaboration project, selecting a clip on the Color page locks that clip to whoever selected it first, and the person who doesn't hold the lock gets read-only access until the other colorist moves to a different clip. That can look and feel like a greyed-out, unresponsive palette even though nothing about your install is broken.

### Do the color wheels work the same in DaVinci Resolve's free version and Studio?

Yes. The Primaries palette, Wheels, Bars, and Log modes, node enabling and disabling, and the global bypass toggle are all core Color page tools with no Studio requirement. Multi-user Collaboration and Blackmagic Cloud Project Libraries are Studio-only, so the shared-project locking scenario above is the one cause on this page a solo free-version editor will never run into.

### Is there an app that helps you while using DaVinci Resolve instead of reading a troubleshooting checklist?

Yes. TryUncle watches your actual Resolve window and points at the specific control causing the problem, live, on the Edit, Color, and Fusion pages, instead of making you match your symptoms to a list like this one. It's a paid macOS app currently in founder pricing, and it's built for exactly this kind of moment, staring at a dead palette with no idea which of a dozen possible causes applies to your project.

## Sources

- [Get Started With the Color Page in DaVinci Resolve, by Larry Jordan](https://larryjordan.com/articles/get-started-with-the-color-page-in-davinci-resolve/)
- [DaVinci Resolve Manual - Bypass Color Grades and Fusion (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part617.htm)
- [DaVinci Resolve Manual - Disabling Nodes (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part2962.htm)
- [DaVinci Resolve Manual - Ability to Bypass Color Management Per Clip (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part309.htm)
- [DaVinci Resolve Manual - Introduction to the Primaries Palette (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part2705.htm)
- [DaVinci Resolve Manual - Log Wheels Mode (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part2720.htm)
- [DaVinci Resolve Manual - Output Sizing on the Color Page (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part374.htm)
- [DaVinci Resolve Manual - Using Group Modes to Control Which Grades Ripple and Which Don't (Blackmagic Design, mirrored)](https://www.steakunderwater.com/VFXPedia/__man/Resolve18-6/DaVinciResolve18_Manual_files/part2952.htm)
- [Creative COW Forum: DaVinci Resolve (camera raw settings greyed out on color panel)](https://creativecow.net/forums/thread/davinci-resolve-camera-raw-settings-greyed-out-on/)
- [Creative COW Forum: Camera RAW control pane, locked controls?](https://creativecow.net/forums/thread/camera-raw-control-pane-locked-controlsae/)
- [Creative COW Forum: Resolve 12 Studio - why can't I access Camera Raw tab?](https://creativecow.net/forums/thread/resolve-12-studio-why-cant-i-access-camera-raw-t/)
- [Blackmagic Forum: Color controls stopped working 15.3.1](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=106064)
- [Blackmagic Forum: Color wheels have no effect?](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=213933)
- [Post-Production Collaboration Made Simple in DaVinci Resolve 14 Studio, by Patrick Southern (Pond5 Blog)](https://blog.pond5.com/18201-post-production-collaboration-made-simple-davinci-resolve-14-studio/)
- [DaVinci Resolve Collaboration (Blackmagic Design product page)](https://www.blackmagicdesign.com/products/davinciresolve/collaboration)
- [Toolfarm: In Depth, DaVinci Resolve Studio vs the Free Version (Updated for 21)](https://www.toolfarm.com/tutorial/in-depth-davinci-resolve-studio-vs-the-free-version/)