DaVinci Resolve Canon R5 C-Log3 Import Settings, Explained

What Color Space Transform settings does C-Log3 footage need?

This is the core answer, and it's worth writing down once so you're not hunting through a forum thread mid-edit.

For footage recorded internally to the R5's card, add a Color Space Transform to your first node and set:

1. Input Color Space: Canon Cinema Gamut
2. Input Gamma: Canon Log 3
3. Output Color Space: DaVinci Wide Gamut
4. Output Gamma: DaVinci Intermediate

That takes your flat Log source into Resolve's own working space, where your actual grading happens. On your last node, before your final output, reverse it:

1. Input Color Space: DaVinci Wide Gamut
2. Input Gamma: DaVinci Intermediate
3. Output Color Space: Rec.709 (or Rec.2100 if you're delivering HDR)
4. Output Gamma: Rec.709 (or ST 2084 / HLG for HDR)

This pairing, one Color Space Transform converting in and one converting back out, is the entire mechanism. It's the same "in, grade, out" pattern documented by Shootlab's walkthrough of grading Canon C-Log footage in Resolve, which recommends the identical Cinema Gamut and Canon Log 3 input pairing followed by DaVinci Wide Gamut as the intermediate stop. Two Color Space Transforms, one at the front of your node tree and one at the back, is all the plumbing this workflow needs.

The HDR branch of that output step deserves its own note. If you're delivering Rec.2100 with an HLG or ST 2084 (PQ) Output Gamma instead of Rec.709, the input side of that same node stays exactly the same, DaVinci Wide Gamut and DaVinci Intermediate. Only the output half changes, and it's worth confirming your Project Settings Timeline Color Space and your monitoring setup are actually configured for HDR before you commit to that path; grading toward Rec.2100 on an SDR reference monitor is a common way to end up with a delivery that looks wrong everywhere except your own room.

Resolve Color Management or a manual Color Space Transform node, which one?

Both get you to the same place. Which one fits depends on how much of your project is R5 footage versus a mix of cameras.

Resolve Color Management, set under Project Settings, Color Management, with Color Science set to DaVinci YRGB Color Managed, lets you assign Canon Cinema Gamut and Canon Log 3 as a clip's input color space directly through Clip Attributes or the Camera RAW tab, and Resolve applies the conversion automatically without you touching a node on every clip. That's the faster setup for a project built almost entirely from R5 footage shot the same way.

A manual Color Space Transform node, the setup detailed above, gives you more control per clip or per group, which matters the moment you're mixing R5 footage with a different camera in the same timeline. You can normalize each camera's native color space independently before applying one shared creative grade across all of them. Our guide to color matching different cameras in DaVinci Resolve covers that multi-camera normalization step in more depth if your project isn't R5-only.

To actually set up Resolve Color Management on an R5 project, open Project Settings, the gear icon in the bottom right or Shift+9, and go to the Color Management panel. Set Color Science to DaVinci YRGB Color Managed, set your Timeline Color Space to DaVinci Wide Gamut / Intermediate, and set Output Color Space to Rec.709 or your actual HDR target. From there, select your R5 clips in the Media Pool, right-click, and open Clip Attributes, or use the Camera RAW palette in the Color page's Inspector for RAW and RAW Light clips specifically. Assign Input Color Space as Canon Cinema Gamut and Input Gamma as Canon Log 3 there, once per clip, and Resolve applies it to every node downstream without a Color Space Transform effect anywhere in your tree.

That one-time per-clip tag is the entire advantage over the manual node approach. Batch-select a hundred R5 clips shot the same way and RCM converts all of them at once, where a manual Color Space Transform node has to be copied or applied per clip or per node group individually. The tradeoff is the one in the table below: change one clip's actual color space, an HDMI-recorded outlier mixed into an otherwise-internal shoot, for instance, and you're back to overriding it clip by clip anyway, which is exactly where a manual node's flexibility starts to pay off again.

Should you use Canon's official LUTs instead of a Color Space Transform?

You can, and for some workflows it's genuinely simpler, but it's not a drop-in replacement for everything the two-node Color Space Transform setup does.

Canon publishes a free LUT package for every camera that shoots Canon Log, including Cinema Gamut plus Canon Log 3 on the R5. The relevant file is named CinemaGamut_CanonLog3-to-BT709_WideDR_65_FF_Ver.2.0.cube, and you'll find it under the Software & Drivers tab on your camera's page at Canon's regional support site, in a folder labeled the Canon Log look-up table, according to Pocket Macro's rundown of the R5's Log LUTs. It's a standard .cube file, the same format Resolve, Premiere, and most other NLEs already read natively.

Drop that LUT onto a node as a single conversion and you'll get a usable Rec.709 image fast: no Input Color Space menu, no Output Gamma dropdown, done. That speed is exactly why editors reach for it on same-day turnarounds, run-and-gun documentary work, or dailies nobody's going to grade further. Our guide to installing LUTs in DaVinci Resolve covers the mechanics of getting .cube files into your Resolve LUT folder if you haven't done that before.

Where it breaks down is exactly the HDMI scenario covered next. Canon's Cinema Gamut LUT bakes in an assumption about which input color space it's converting from, and it doesn't know or care whether your clip actually came from Cinema Gamut or from an HDMI-recorded Rec.2020 source. Feed it the wrong one and you get the same mismatch a manual Color Space Transform would throw if you picked the wrong Input Color Space, except a LUT gives you no menu to catch the mistake in before it's baked into your grade.

A one-step LUT and a two-node Color Space Transform solve the same math, but only the Color Space Transform gives you a separate control for each half of the conversion when a clip needs a non-default input. If your whole project is internal recordings from one R5, either approach lands you in the same place. If you're mixing internal and HDMI-recorded sources, or expect to push the grade further than a single pass, the manual node setup is the safer default.

Why does HDMI-recorded C-Log3 footage look different from internal recording?

This is the single most common cause of "I did everything right and it still looks wrong" on R5 footage, and it has nothing to do with your Color Space Transform math.

The R5 and R6 have a hardware limitation on their HDMI output that Canon doesn't spell out clearly in its own marketing. Rodrigo Polo, who has published Log-to-Rec.709 conversion LUTs and detailed color science breakdowns for both Canon and Apple cameras, documented it directly: "the EOS R5 and R6 are unable to output C-Log 3 with Cinema Gamut through HDMI, even after setting Cinema Gamut as color space on the camera, HDMI will always output Rec/BT.2020," he wrote after testing the discrepancy between internal and external recordings.

That means a clip recorded internally to your card, tagged Cinema Gamut, and a clip recorded at the exact same moment to an external recorder like an Atomos Ninja V, tagged Rec.2020, come from the identical sensor and identical exposure, but need two different Color Space Transform inputs to match. Apply Cinema Gamut to your HDMI-recorded footage anyway, and Polo's own testing found you can compare a clip recorded internally with Cinema Gamut and externally with Rec/BT.2020 and they look the same, "even after applying Canon's own technical LUTs," once each source gets its correct input tag, but not before.

Worth separating clearly: an Atomos Ninja V recording C-Log3 video over HDMI is a different pipeline than a Ninja V recording ProRes RAW from the same port. Polo's earlier writeup on the R5, C-Log 3, and the Ninja V covers the standard video path, the Rec.2020 mismatch above. ProRes RAW output is a distinct RAW recording mode with its own debayer step in Resolve, closer in spirit to the internal RAW workflow covered later in this guide than to a Color Space Transform question. If your Ninja V footage opens as a .mov that Resolve treats through its RAW palette rather than a standard clip, you're in the RAW path, not the Rec.2020-versus-Cinema-Gamut path, and the fix is different.

A Canon R5 clip recorded to an external monitor over standard HDMI video needs Rec.2020 as its Color Space Transform input, not Cinema Gamut, regardless of what the camera's own menu says you selected. Miss this one setting and internal and external footage of the same scene, shot seconds apart, will grade to visibly different color no matter how carefully you match everything else.

What ISO should you shoot C-Log3 at for these settings to work correctly?

The Color Space Transform math assumes you exposed the footage the way the gamma curve was designed for, and getting that wrong upstream isn't something Resolve can fully fix downstream.

Per Canon's own product manual, "Canon Log 3 offers a dynamic range of approx. 1600% at ISO 800 or higher," and setting ISO below that narrows the dynamic range the curve is built to capture. That's a full stop higher than plain Canon Log, which reaches its stated dynamic range at ISO 400. DPReview's own breakdown of the format frames it plainly: when C-Log3 is engaged, the base ISO rating jumps to 800, specifically to give the camera one stop less exposure so it can hold onto more highlight detail.

The R5 Mark II carries the same floor forward for both of its Log options. Canon's own Custom Picture Setting guide for the EOS R1 and EOS R5 Mark II lists "1600%" dynamic range at "base ISO 800" for Canon Log 2 and Canon Log 3 alike, and adds that "shooting with Canon Log 2/Canon Log 3 is possible even at a lower ISO setting, however, the dynamic range will be narrower, so caution is necessary." Whichever Log curve you're shooting on whichever R5, ISO 800 is the floor the color science was actually built around.

Exposing C-Log3 below ISO 800 doesn't just make footage darker, it throws away the extra highlight headroom that's the entire reason to shoot C-Log3 instead of a standard picture profile. If your R5 footage still clips highlights or crushes shadows after a correct Color Space Transform, check your original ISO before you spend more time on the color node. A curve that never got the exposure it was designed for won't grade like one that did.

Does noise get worse at higher ISO, and how do you fix it in Resolve?

Every stop of ISO you add above C-Log3's ISO 800 baseline buys you correct exposure at the cost of more visible noise once you stretch that flat Log image out into a normal-contrast grade, and the Color Space Transform itself does nothing to reduce it.

DaVinci Resolve's noise reduction tools, both Temporal and the DaVinci Neural Engine-driven Spatial and UltraNR modes, are Studio-exclusive. Blackmagic's own Studio product page lists temporal and AI spatial noise reduction tools among the features that separate Studio from the free version, alongside the wider Neural Engine feature set. If you're already on Studio for the 10-bit 4:2:2 decoding reasons covered below, you already have access to these tools. If you're not, denoising a noisy high-ISO C-Log3 clip inside Resolve itself isn't something the free version offers.

Node placement matters more than which specific noise reduction mode you pick. Apply Noise Reduction on a node before your Color Space Transform converts the clip out of Log, while the image is still flat and the noise pattern is closer to what the sensor actually recorded, rather than after you've already pushed contrast and saturation back in through the grade. Denoising after a heavy grade means fighting noise that's already been amplified by every contrast and saturation move downstream of it, asking far more of the same tool for a worse result.

Our dedicated guide to DaVinci Resolve's video noise reduction settings covers the specific Temporal, Spatial, and UltraNR parameters, motion estimation range, and the tradeoffs between denoising strength and softened detail in more depth than fits here.

C-Log3's noise floor is a shooting-day problem first and a Resolve problem second. Staying at or near ISO 800, rather than pushing several stops over it just because the dynamic range technically allows it, keeps you out of the noise reduction workflow altogether on most shoots.

C-Log vs C-Log3 vs C-Log2, which one should you actually shoot?

If you're still deciding what to shoot, or trying to figure out why an older archive of R5 footage behaves differently from a recent shoot, the three Log options aren't interchangeable, and picking the wrong one for your workflow costs you time in the grade.

Plain Canon Log, the original option on the R5 before firmware 1.3.0, is the least forgiving of the three. It's more prone to clogged shadow detail and its LUTs don't line up as cleanly with Canon's Cinema EOS line. C-Log3 fixes both problems: Canon's own documentation notes it "offers a dynamic range of approx. 1600% at ISO 800 or higher" against C-Log's roughly 800% at ISO 400, effectively doubling stated dynamic range while also matching Cinema EOS LUT behavior more closely.

C-Log2, available only on the R5 Mark II, pushes further still, targeting the widest possible dynamic range for a heavy VFX or color-intensive pipeline, at the cost of needing more careful exposure and noise management to use well. It's the option built for a colorist doing serious work, not the default for someone who wants footage that behaves predictably straight into a fast grade.

C-Log3 is the format Canon itself points hybrid shooters toward, and it's the one this entire settings reference is built around because it's the one most R5 footage actually arrives in. If you're choosing what to shoot for the first time, start there rather than plain C-Log or, unless you specifically need C-Log2's extra range, the Mark II's newer option.

Is there an ACES workflow for Canon R5 C-Log3 footage in DaVinci Resolve?

Yes, though it takes more setup than the DaVinci Wide Gamut path this guide is built around, and it's worth it mainly if you're already delivering through an ACES pipeline for other reasons.

Blackmagic Design is an official member of the Academy Color Encoding System project, and DaVinci Resolve supports it as a full alternative to DaVinci YRGB Color Managed, with input transforms built in for most major camera brands. Switch Color Science in Project Settings to ACEScct or ACEScc, and Resolve treats your working space, your scopes, and your grading tools according to the ACES standard end to end, from a per-clip Input Device Transform to a final Output Device Transform matched to your delivery target.

The catch for R5 shooters specifically is that Resolve's built-in ACES camera list leans heavily on Canon's Cinema EOS line, cameras like the C300 and C500, which ship with Academy-published Input Device Transforms. A hybrid stills-and-video body like the R5 isn't guaranteed the same first-party coverage. Colorists working through this exact gap on the Blackmagic Design and ACEScentral forums have found that the practical fix is applying a manual Input Device Transform as a clip DCTL in the Media Pool, ahead of Resolve's own ACES transform chain, a workaround discussed directly on the Blackmagic forum, rather than relying on Cinema Gamut and Canon Log 3 showing up as a stock preset the way they do in DaVinci YRGB Color Managed's Camera RAW tab.

ACES is worth setting up for R5 footage when you're intercutting with true Cinema EOS or other ACES-native cameras on the same project, or when your delivery pipeline downstream already expects ACES natively. For a single-camera R5 project heading to a standard Rec.709 or HDR10 delivery, the DaVinci Wide Gamut intermediate covered throughout this guide gets you there with far less setup, and it's the path most working colorists actually use for this specific camera.

Does DaVinci Resolve import Canon R5 RAW or RAW Light footage?

Yes, and this is worth separating clearly from the C-Log3 workflow above, because RAW and Log are handled completely differently once they land in your Media Pool.

DaVinci Resolve decodes the R5's internal RAW and RAW Light files natively, with automatic frame rate recognition and no plugin required. Right-click a RAW clip and open the Camera RAW panel to adjust decode settings, white balance, exposure, and ISO after the fact, the same latitude RAW footage from any camera gives you. There's a naming trap worth knowing before you go looking for documentation, though: per Newsshooter's coverage of the R5 Mark II, the Mark II's RAW Light is "the same RAW found in the 1DX Mark III," not the Cinema RAW Light codec Canon's C-series cinema cameras use, despite sharing almost the same name. The original R5's RAW Light, introduced in firmware 1.3.0 alongside C-Log3, is the same proprietary format, not the Cinema EOS one either.

That distinction matters practically because tutorials and LUTs built for genuine Cinema RAW Light from a C70 or C300 don't map cleanly onto an R5's RAW Light files, even though a quick search makes them look like the same thing. If you're trying to apply a Cinema EOS RAW workflow to R5 footage and it isn't behaving the way a tutorial promised, that naming overlap is very likely why.

"RAW Light" on a Canon R5 and "Cinema RAW Light" on a Canon C-series camera are different codecs that happen to share three words in their name. Confirm which one you're actually holding before you troubleshoot a RAW workflow, the same way you'd confirm C-Log versus C-Log3 before troubleshooting a color problem.

If your R5 RAW or RAW Light files won't open at all rather than just looking unfamiliar, that's a separate failure mode from anything above. Our DaVinci Resolve Unsupported File Format guide and our Blackmagic RAW won't import guide cover the general codec, decoder version, and GPU causes behind an outright import failure, which apply across RAW formats generally, not just Blackmagic's own.

Why won't some Canon R5 clips import into DaVinci Resolve at all?

If your C-Log3 clip shows up as "Media Offline" or won't even generate a thumbnail, that's a different failure mode than a wrong-looking grade, and it usually traces back to one specific gap in the free version.

The R5's standard H.264/H.265 video modes record Canon Log and Canon Log 3 as 10-bit 4:2:2 files, per Canon's own product manual. DaVinci Resolve's free version has real limits decoding that exact combination. It handles common 8-bit and 10-bit 4:2:0 H.265 footage fine, but 10-bit files with 4:2:2 chroma subsampling, which is precisely what the R5 records in its Log modes, routinely show up as offline in the free version rather than decoding, a pattern flagged directly on Canon's own community forum and across multiple editors' troubleshooting writeups. Puget Systems' breakdown of Resolve's hardware decoding support confirms the split runs along Studio versus free lines: "The Studio version of DaVinci Resolve has long been able to utilize hardware decoding of H.264 and H.265 (HEVC) media."

Windows adds a second, unrelated wrinkle on top of that. Microsoft doesn't ship HEVC decoding natively with Windows, so even Resolve Studio needs the separate "HEVC Video Extensions" package from the Microsoft Store installed at the OS level before H.265 files, R5 footage included, will decode at all, a gap that Filmmaking Elements' guide to fixing HEVC media offline errors walks through directly. Mac users don't hit this particular wall, since macOS has included HEVC decoding since Sierra, but they still hit the free-versus-Studio 4:2:2 limitation described above.

You have three real options if a C-Log3 clip won't come online:

1. Upgrade to Studio. This is the direct fix and the one Canon's own community forum and most editors land on, since it removes the 4:2:2 decode limit and (on Windows) still requires you to confirm the Microsoft HEVC extension is installed.
2. Transcode before you import. Convert the offending clips to an intraframe codec like ProRes or DNxHR outside Resolve first, using whatever converter you already have, then bring the transcoded files in instead of the originals.
3. Generate proxy or optimized media from inside the free version, though this path is inconsistent specifically for 10-bit 4:2:2 sources on Free, since Resolve still has to decode the original once to build the proxy, which is exactly the step failing. It tends to work more reliably once you're already on Studio.

Our dedicated DaVinci Resolve Media Offline guide covers the broader set of causes behind that specific error message, everything from moved files to missing render caches, if the fix above doesn't fully resolve your case.

A Canon R5 clip that won't come online in Resolve isn't a color science problem and no Color Space Transform setting fixes it, it's a 10-bit 4:2:2 H.265 decode limitation specific to the free version. Confirm which version of Resolve you're running before you spend time troubleshooting a Color Space Transform on a clip that hasn't actually decoded yet.

Do you need proxies to edit 8K RAW or C-Log3 footage smoothly?

Often, yes, and the reason is different depending on whether you're cutting RAW or Log footage.

The R5's internal RAW and RAW Light files record at up to 8192 x 4320, per Canon's own video performance specs, and every RAW frame has to be debayered before Resolve can even display it, a real-time computational cost that has nothing to do with file size or codec efficiency. A heavily compressed 10-bit 4:2:2 C-Log3 H.265 file is smaller on disk but leans on long-GOP decoding instead, which is its own kind of expensive on a laptop GPU. Both situations respond to the same fix: build lower-resolution stand-ins before you start cutting.

DaVinci Resolve gives you two related tools for this, Proxy Media and Optimized Media, and the choice matters for an 8K project specifically. Right-click a clip or a bin in the Media Pool and choose Generate Optimized Media to have Resolve transcode a full local copy in the background at a resolution and codec you set in Project Settings, Master Settings, Optimized Media and Render Cache. For 8K sources, Pixflow's proxy workflow guide recommends leaving Proxy Media Resolution on "Choose Automatically," which "sizes proxies proportional to your timeline resolution," turning an 8K clip into a quarter-resolution proxy on a 4K timeline automatically, and forcing it down further to eighth resolution manually if playback still stutters on a lower-powered machine.

Codec choice follows your platform. On a Mac, ProRes, typically ProRes 422 or ProRes 422 LT, is the standard proxy codec. On Windows, DNxHR fills the same role, with DNxHR LB for the smallest files and DNxHR HQX when you have the storage to spare, per Beginners Approach's breakdown of Resolve's proxy resolution and codec options. Our full guide to proxy media setup for a slow laptop walks through the exact Project Settings panel and a decision tree for which resolution tier fits your specific hardware, and our ProRes vs DNxHR comparison breaks down when to pick one over the other beyond just your OS.

Proxies fix playback performance, not color. Building optimized media from an R5 clip doesn't change or skip the Color Space Transform step covered earlier in this guide; Resolve automatically relinks to your full-resolution originals for the final render regardless of what you cut with, so your Cinema Gamut or Rec.2020 input tagging still applies exactly the same way it would without proxies in the pipeline.

Do you need DaVinci Resolve Studio for any of this?

No, not for the core C-Log3 workflow this page covers. The Color Space Transform effect, Resolve Color Management's automatic tagging, and native RAW/RAW Light decoding all work in the free version of DaVinci Resolve, with no functional restriction on the color math itself.

Per Blackmagic's own free version product page, the free tier covers professional color grading tools without a Studio license. Where Studio genuinely enters the picture is a delivery target that needs Dolby Vision metadata authoring or HDR10+ analysis and export, both listed on Blackmagic's Studio product page as Studio-exclusive; workflows that lean on Studio-only tools like Noise Reduction and the DaVinci Neural Engine for heavy RAW grading, covered above; or footage that simply won't decode in the free version to begin with, the 10-bit 4:2:2 H.265 limitation covered above as well.

Getting Canon R5 C-Log3 footage to grade correctly is a color management problem, and color management is not a feature Blackmagic gates behind the Studio license. Don't let a general free-versus-Studio comparison talk you into buying $295 of software just to make your R5 footage look right, unless you've actually hit one of the specific decode or noise reduction walls above. Our full DaVinci Resolve Studio price breakdown covers exactly what the license does and doesn't change if you're weighing it for other reasons, like HDR delivery or noise reduction on a noisy high-ISO shoot.

A step-by-step example: taking one C-Log3 clip from flat to Rec.709

Here's the full sequence in order, from a fresh R5 clip in the Media Pool to a delivered Rec.709 grade, with every step from earlier in this guide placed where it actually happens in a real node tree.

1. Confirm the source. Right-click the clip, check Clip Attributes, and confirm it's C-Log3, shot at ISO 800 or above, and note whether it was recorded internally or over HDMI. This is the single check that determines your Input Color Space two steps from now.
2. Build optimized media if the clip is stuttering on scrub. If it's a 10-bit 4:2:2 H.265 file playing back roughly, generate optimized media at Quarter or Eighth Resolution before you touch color, so you're not fighting playback performance and grading decisions in the same pass.
3. Node 1, Color Space Transform in. Set Input Color Space to Canon Cinema Gamut for an internal recording (or Rec.2020 if it came in over HDMI), Input Gamma to Canon Log 3, Output Color Space to DaVinci Wide Gamut, Output Gamma to DaVinci Intermediate.
4. Node 2, Noise Reduction, if the shot needs it. If the clip was shot at a high ISO and shows visible grain once it's out of Log, add a Temporal or Spatial Noise Reduction node here, immediately after the Color Space Transform, before any contrast or saturation moves.
5. Node 3, primary correction. With the clip sitting in DaVinci Wide Gamut, set your white balance using an eyedropper on a neutral reference in frame if you have one, then bring your black point and white point in toward the edges of your waveform using the Lift and Gain wheels, watching for clipping on the scopes rather than by eye alone.
6. Node 4, creative grade. Do your actual look here: contrast shaping, color balance between shadows and highlights, any secondary qualifiers or power windows the shot needs. This is the node where R5 footage behaves like footage from any other camera; nothing about C-Log3 changes how you grade once you're in a normal working space.
7. Node 5, Color Space Transform out. Input Color Space DaVinci Wide Gamut, Input Gamma DaVinci Intermediate, Output Color Space Rec.709, Output Gamma Rec.709 or Rec.709-A.
8. Check the result against the troubleshooting table below before you call the grade final, particularly if this R5 clip is intercut with footage from a different camera or a different recording method.

Five nodes handle the entire mechanism from flat Log source to finished Rec.709 delivery, with Noise Reduction as the one optional insertion depending on how the clip was shot. Everything else, from the creative color decisions to the specific tool choices in node 4, is the same grading work you'd do on footage from any camera once it's sitting in a normal working space. A common mistake worth naming directly: adding a third or fourth Color Space Transform "just to see" what a different combination looks like, then forgetting to remove it. Two conversions per clip, one in and one out, is correct. Three is almost always a leftover from experimenting, and it's the fastest way to land in the log-on-log problem covered next.

Why does C-Log3 footage still look wrong after you've applied the Color Space Transform?

If you've followed the settings above and it's still off, work through these in order before assuming your footage is somehow bad.

First, the HDMI mismatch covered earlier. Confirm you're not applying Cinema Gamut to a clip that was actually recorded externally, or Rec.2020 to a clip recorded internally. This single swap is the most common cause of "my C-Log3 grade looks fine on some clips and wrong on others from the same shoot."

Second, log-on-log. If a clip looks oversaturated, hue-shifted, or has crushed color in a way that doesn't respond normally to your color wheels, check whether a LUT is stacked on top of a Color Space Transform doing the same conversion, or whether Resolve Color Management is set to automatic tagging while a manual node is also applying its own transform to the same clip. Rodrigo Polo's own testing of R5 C-Log workflows in Resolve found exactly this kind of layered-conversion confusion when comparing LUTs against Color Space Transforms directly, noting outright that "Canon has a poor and bad documentation" on how its own LUTs and native color management are meant to interact, which is exactly the kind of gap that leads editors to accidentally double up a conversion.

Third, timeline color space mismatch. If your project's overall Color Management is set to a working space your output node doesn't actually match, Rec.709 versus Rec.2100 being the most common version of this mistake, footage can look correct in isolation and wrong the moment it's viewed against your monitoring setup or exported.

Fourth, and easy to miss because the symptom looks like a color problem: check whether the clip actually decoded, or whether you're grading a low-resolution proxy that never got relinked to full-resolution media before export. A proxy built at Eighth Resolution can mask fine noise or banding that shows up the moment the final render relinks to the original file.

When the menus alone don't get you there fast enough

Everything in this reference is a settings problem with a settings answer, but finding the right menu on a deadline is its own kind of friction, especially the first few times you're bouncing between Project Settings, the node graph, and Clip Attributes trying to confirm exactly what a clip is before you touch its color.

TryUncle is the on-screen assistant for DaVinci Resolve on macOS. Ask in plain words, and Uncle points at the exact control on your screen. If you're on a Mac asking "why does my C-Log3 footage look grey" out loud at your screen, that's a faster route to the Color Space Transform panel than searching this page a second time mid-session. It's a paid app, currently in founder pricing, and macOS only, so it won't help a Windows editor working through Resolve's menus. Check TryUncle for current pricing before deciding if it fits your workflow.

It's worth knowing the category has other tools built on a different premise. Sottocut, PremiereCopilot, heyeddie.ai, and cutagent.ai automate parts of an edit or answer chat questions about your footage, rather than watching your live screen and pointing at controls. If your goal is automating a cut, those solve a different problem. If your goal is finding the right Color Space Transform setting faster, on-screen guidance is the more direct tool for that specific job.

What's the full settings cheat sheet at a glance?

Before the table, here's the one-line version of everything above. Use Resolve Color Management if your project is entirely R5 footage shot the same way. Switch to a manual Color Space Transform node the moment you're mixing internal and HDMI-recorded clips, or mixing cameras. Reach for Canon's official LUT only for fast, low-stakes turnarounds where you won't grade further. Consider ACES only if your delivery pipeline already runs on it. And if a clip won't come online at all, that's a decode problem, not a color space problem, and belongs in the import-failure section above, not in your node tree.

Match your recording method to the right input color space first, keep your exposure at ISO 800 or above, confirm the clip actually decoded before you blame the color, and the rest of this workflow is two Color Space Transform nodes doing exactly what they're built to do. Most R5 footage that "looks wrong" in Resolve isn't broken. It's one setting, or one missing codec extension, away from correct, and now you know which one.