Blackmagic RAW in DaVinci Resolve: Camera RAW and Color Management

Quick answer: decide who owns the technical transform before you touch a single BRAW setting. In a Resolve Color Management project, let Resolve identify and debayer the Blackmagic RAW clip, grade in the timeline space you picked, and let the project's output transform handle the display. Don't stack another camera-normalizing CST or technical LUT on top. In a manual DaVinci YRGB project, decode BRAW to a deliberate wide-gamut/log starting point, then normalize it exactly once with a matching CST, a technical LUT or your own grade.

Both routes can give you a great image. Trouble starts when you mix pieces of them: BRAW decodes toward one color space and gamma, a CST expects another, a LUT expects a third, and RCM wraps its own input or output transform around the whole stack. The shot ends up clipped, oversaturated, oddly contrasty or impossible to balance, even though the sensor data is still sitting there.

So the useful question isn't “What's the best BRAW setting?” It's “Which stage decodes this clip, which one normalizes it, and which one gets it onto the display?”

Understand What Camera RAW Changes

Blackmagic RAW isn't ordinary video with a fixed white balance and a baked-in display look. Resolve first has to turn the sensor-derived data into image data its pipeline can work with, and Blackmagic’s manual calls raw decoding the very first image-processing operation. It happens before every Color page operation, ahead of even the Source bar in the node editor, and the Camera Raw Settings chapter of the DaVinci Resolve 21 Reference Manual spells out that order. With the 32-bit floating-point pipeline keeping that data intact, Camera RAW is mainly where you set the best starting point for the grade.

Stripped down, the pipeline looks like this:

BRAW sensor data → Camera RAW decode → Color page processing → output transform → render

That order is why Camera RAW exposure, white balance, color science, color space and gamma aren't interchangeable with ordinary node corrections. They decide which image the grade starts from. A node can rebalance and reshape that image all day, but it only ever sees it after the decode.

Blackmagic RAW also does part of the image processing in the camera. Blackmagic describes noise management, sensor profiling and edge reconstruction as part of its partial de-mosaic design, followed by a custom non-linear 12-bit encoding. The company’s Blackmagic RAW format overview explains how the files stay adjustable without carrying completely untouched sensor data.

Keep that in mind when you get to noise reduction. BRAW’s camera-side processing doesn't replace Resolve’s temporal or spatial tools when a finished shot still shows visible noise.

Choose One of Two Complete BRAW Workflows

Pick one of these two systems before you touch a clip-level control. Most BRAW headaches start when the two get mixed.

Workflow 1: Resolve Color Management owns the transform

This is the route for projects that already lean on RCM: mixed cameras, a wide-gamut timeline, or controlled SDR/HDR outputs.

1. Open Project Settings → Color Management.
2. Set the project to a Resolve Color Management workflow.
3. Choose the timeline working color space required by the project.
4. Choose the real output color space for the display or deliverable.
5. Import the BRAW media and let Resolve identify it as camera RAW.
6. Grade the shot in the managed timeline space.
7. Keep camera-normalizing CSTs and technical camera LUTs out of the clip node tree.

Under RCM, Resolve uses manufacturer-supplied colorimetry to debayer each camera RAW clip to specific primaries with linear gamma and to identify its input color space. The DaVinci Resolve 21.1 Reference Manual is plain about the side effect: the Camera RAW project settings and the Color page Camera RAW palette are disabled, because RCM now controls the debayer. You also can't override the Media Pool Input Color Space for camera RAW media the way you can for other clips.

Greyed Camera RAW controls don't mean the file is broken, then. In an RCM project they're exactly what you should expect once the color-managed pipeline owns the raw decode.

Balance the shot with normal grading controls inside the timeline space. For the bigger picture, with input, timeline and output stages included, see the Resolve Color Management and CST guide.

Workflow 2: manual DaVinci YRGB owns the transform

Take this route when you want your hands directly on the BRAW decode and prefer a node-based technical transform.

1. Set the project to manual DaVinci YRGB rather than RCM.
2. Open Project Settings → Camera RAW → Blackmagic RAW.
3. Choose the project-wide decode policy and a deliberate color science, color space and gamma.
4. On the Color page, switch an individual clip to Decode Using: Clip only when it needs a source-level override.
5. Normalize the decoded image once with a CST, a technical LUT whose expected input exactly matches the decode, or a custom normalization grade.
6. Build creative corrections around that single technical transform.

A wide-gamut/log decode leaves you room to grade. The exact labels you'll see depend on the BRAW metadata, the color-science choice and your Resolve version, so I'd trust a rule over a copied dropdown recipe: whatever input your CST or LUT names has to match the color space and gamma Camera RAW actually produces.

With a CST, copy those decode choices into Input Color Space and Input Gamma, then transform to whatever working or display space the node tree really uses. With a LUT, check its documented input first. A LUT built for one Blackmagic Film generation isn't a generic “make BRAW normal” button.

The DaVinci Resolve LUT guide explains the difference between a technical transform and a creative look. Keep those two jobs apart and BRAW troubleshooting gets much easier.

Avoid the Double-Transform Trap

A double transform means the same camera-to-working-space or camera-to-display conversion happens twice.

The usual suspects:

• RCM already maps BRAW into the timeline space, then a node applies a camera-to-Rec.709 CST;
• Camera RAW decodes to a display-oriented gamma, then a technical LUT expects a log input;
• Camera RAW decodes to one Blackmagic color space and gamma while a CST is configured for another;
• a sidecar or embedded BRAW LUT is applied during decode, then a similar LUT is added again in the node tree;
• a timeline/output transform is added to a project that already has an RCM output transform.

You see the symptoms in the image, but the fix is structural. Switch off technical LUTs and CSTs for a moment, confirm the project's color-management mode, and work out who actually owns the BRAW decode. Then rebuild one transform chain: source, timeline, output.

Don't paper over a wrong transform by pulling saturation, gain and contrast in opposite directions. You might rescue one shot that way, but gamut mapping, highlight behavior and every other BRAW clip stay inconsistent.

Set Project-Level BRAW Defaults First

Choices that most of your BRAW clips share belong in the project settings. The Camera RAW panel applies one decode policy across the project, with Camera Metadata as the default, and in a manual YRGB workflow Decode Using: Clip opens up individual controls for a selected clip.

Each decode policy has its own job:

• Camera Metadata starts from choices recorded with the clip.
• Project applies the project’s BRAW settings consistently.
• Clip allows a selected shot to depart from the project default.
• a Blackmagic RAW default option returns to the format’s standard decode behavior rather than a custom project look.

Start broad, override narrowly. If twenty clips from the same setup need the same color science and decode starting point, one project default is far easier to audit than twenty unrelated clip settings. Drop to clip level only when a shot needs its own white balance, exposure move or recovery decision. One trap: a clip's camera raw settings travel with its grade when you copy it, so when you ripple grades across a scene, use Copy Grade: Preserve Camera Raw Settings in the Gallery's contextual menu so each clip keeps its own decode.

That keeps source prep apart from the creative grade. The core Resolve color grading workflow picks up from there: balance, contrast, saturation and shot matching once the image is inside the Color page pipeline.

Choose Color Science, Color Space and Gamma Deliberately

These three menus are linked, but each one answers a different question.

Color Science

The Color Science setting picks which generation of Blackmagic camera color science decodes the clip. Camera Metadata follows whatever the camera was set to when it recorded; Gen 4, the original version, and Gen 5 are the explicit alternatives.

Blackmagic describes Gen 5 as a newer, more film-like curve built for better skin tones and a stronger response to high-contrast, highly saturated color. That makes it a sensible starting point for a lot of manual workflows, but not a reason to flip every project blindly. Existing grades, LUT assumptions, shots you've already matched and delivery continuity are all good reasons to keep the recorded or established generation.

Treat a color-science change as a pipeline decision, and recheck the technical transform and the grade afterward. It's not a small cosmetic tweak.

Color Space

The color space sets the primaries of the decoded image. The wide-gamut Blackmagic Design option leaves the most room for later correction. Rec.709, Rec.2020, P3 and the specialty XYZ options serve different display or exchange needs, and the manual is clear that you don't have to pick Rec.709 just because the final video will be SDR.

In a manual node-based workflow, keep the decode wide enough to grade and let one planned transform deal with the destination. In RCM, leave this stage to the managed pipeline.

Gamma

Gamma decides how tonal values are encoded after the raw decode. Blackmagic Design Film, the log option, is built for grading and looks flat until you normalize it; the manual says outright that it isn't a viewable image on its own. Blackmagic Design Video and Extended Video give you a more display-ready start, and Extended Video compresses highlights to keep more detail in the visible range. Either one changes what the next transform should expect. Whichever you choose, the manual notes that image data clipped on output is still preserved inside Resolve's pipeline.

Flat doesn't mean broken, and contrasty doesn't mean correct. Judge the gamma together with the CST, LUT or color-management path that comes after it.

Use Clip-Level RAW Controls for Source Corrections

In manual YRGB, set Decode Using: Clip when one BRAW shot needs source-level treatment. That makes the Camera RAW palette editable, and your changes override the project-wide settings for that clip: white balance, color temperature, tint, exposure, saturation, contrast, rolloff and recovery options, depending on the decode mode and metadata. Every parameter you change turns amber, so you can see exactly what you've touched, and the Use Changes button ripples only those amber parameters to other clips you've selected.

A BRAW clip’s RAW controls also live under Inspector → Image on the Media, Cut and Edit pages. The diagram below shows the logic: most clips follow the project decode, while one shot carries its own white balance and exposure.

Save these controls for corrections that belong to the source decode:

• correct a clearly wrong recorded white balance before building secondary color work;
• make a restrained exposure adjustment when the raw starting point needs to move;
• enable Highlight Recovery only when clipped sensor highlights contain useful recoverable detail;
• enable gamut compression when highly saturated LEDs, neon or similar narrow-band sources break at the gamut boundary;
• check whether a decode LUT is being applied from sidecar or embedded metadata.

Highlight Recovery isn't a universal quality switch. It pulls in extra highlight sensor data that the standard decoding matrix usually clips, and Blackmagic warns that the recovered detail can carry unusual color artifacts. Check bright practicals, specular highlights, colored LEDs and skin near clipping before you leave it on.

The same goes for a Camera RAW exposure change: it doesn't replace shaping the whole grade. Use it to set the source starting point, then handle scene balance and creative intent in the node tree. If you can't decide between two decodes, make a second grade version. Each version keeps its own Camera RAW adjustments, so you can compare both on the same clip.

Check Sidecar and Embedded Metadata

BRAW can carry metadata inside the clip and in a .sidecar file saved next to it. When a sidecar is present, it always wins over the embedded metadata during decode; without one, Resolve falls back on what's embedded in the .braw file. The sidecar is human-readable JSON, and the manual documents Update Sidecar as the button that writes your Camera RAW changes to it. It only works once Decode Using is set to Clip on the Color page.

That's often why a clip opens with a look or decode choice you didn't expect. Before you rebuild the grade, look in the media folder for sidecars and check Apply LUT and LUT source in the BRAW controls. The LUT source menu picks between the sidecar's color metadata and the metadata embedded in the clip.

Treat a sidecar update as a shared source decision. As the manual puts it, the media on disk then reflects your change in any other BRAW-compatible application, and another Resolve project reading the same files can pick it up too. For a team handoff, move the BRAW clip and its intended sidecar together, and write down whether the look should come from metadata or from the project’s own transform chain.

Improve Playback Without Losing the Final Decode

When your system can't debayer full quality in real time, drop BRAW decode quality to Half, Quarter or Eighth resolution. That's a performance setting for decode resolution; it has nothing to do with the project’s creative color pipeline.

For the final render, turn on Force debayer res to highest quality in the Deliver page Render Settings. Resolve then renders raw media at its highest available decode quality even if you graded at a lower setting, which, as the manual jokes, saves you from forgetting to switch it back at 3am. There's also Use GPU for Blackmagic RAW decode in the Decode Options panel of the System preferences, which hands BRAW decoding to the GPU.

If the timeline still crawls after you lower raw decode quality, the bottleneck probably sits further down the pipeline: temporal noise reduction, optical-flow effects, Fusion work or heavy grades. Use the site’s playback and cache guides for those stages; changing the BRAW color transform won't buy you speed.

Proxies can hide Camera RAW changes

Proxy media is ordinary rendered video, not RAW sensor-derived media, and it's rendered with whatever Camera RAW settings were active when it was generated. The manual even suggests generating several proxies per clip when you want to compare different raw settings. So if Resolve is showing a proxy, changes in the BRAW Camera RAW palette can look as if they do nothing. Optimized media behaves differently: any camera raw change discards it, and you'll need to generate it again.

When RAW controls move but the Viewer doesn't respond:

1. check whether proxy playback is enabled;
2. switch back to the native BRAW clip;
3. confirm the controls affect the native image;
4. grade and render from native media when the final result depends on RAW adjustments.

Don't confuse this with greyed-out controls under RCM. A proxy hides the effect of a control that works; RCM legitimately switches the raw controls off because the managed pipeline owns the decode.

Put Noise Reduction After the Decode Decision

BRAW’s partial in-camera processing includes noise management, yet visible noise can still need work in Resolve. Get the decode and transform chain straight first, then judge noise in the working image through the viewing transform you'll actually deliver with.

Heavy noise reduction before the color pipeline is confirmed wastes processing time and can hide transform mistakes. Put it after aggressive sharpening, texture and contrast, and the noise gets harder to separate from real detail.

A manual node order that works:

BRAW decode → source balance → noise reduction when needed → working-space grade → creative look → output transform

In an RCM project, the input and output stages sit outside the usual camera-normalizing node chain:

RCM input/debayer → source balance → noise reduction when needed → timeline-space grade → creative look → RCM output

Use the DaVinci Resolve noise reduction guide for temporal and spatial settings, artifact control and Free-versus-Studio limits.

Troubleshoot BRAW Settings by Symptom

Camera RAW controls are greyed out

Check Project Settings → Color Management. If the project runs RCM, Resolve 21.1 disables the Camera RAW project controls and the Color page palette because RCM owns camera RAW debayering. That's expected behavior, not proof that the file is damaged.

Camera RAW controls move but the image does not change

Turn off proxy playback and view the native BRAW. Make sure the selected timeline clip is the BRAW source and not a rendered replacement. Optimized media isn't the culprit here, since a camera raw change discards it.

The image becomes too contrasty or saturated after a LUT

Disable the LUT and look at the image going into it. Confirm the input color space and gamma the LUT expects, then compare them with the Camera RAW decode. While you're there, check for a sidecar or embedded LUT and an active RCM output transform.

A CST produces clipped or strange color

Match CST Input Color Space and Input Gamma to the BRAW decode you actually set. If the project uses RCM, remove any camera-normalizing CST unless that node has a different, clearly defined job.

One clip needs different exposure or white balance

In manual YRGB, set that shot to Decode Using: Clip and adjust it in Camera RAW. Don't move the project-wide default for one outlier.

Highlight Recovery creates colored edges or patches

Turn it off and compare the native highlight. Recovery can bring back extra detail along with color artifacts, so keep it only where the recovered information looks cleaner than the clipped version.

Resolve does not recognize the file as expected

Make sure the media is the original .braw file and not a proxy or transcode. Then check the file and your system against the Resolve supported codecs and formats guide and Blackmagic’s current support information.

Final BRAW Settings Check

Before you grade or render, check the whole path, not one dropdown:

• the project is intentionally RCM or manual DaVinci YRGB;
• only one stage owns the camera-to-working-space transform;
• only one stage owns the output transform;
• manual Camera RAW color space and gamma match the CST or technical LUT input;
• RCM clips do not carry an unnecessary camera-normalizing CST or technical LUT;
• clip overrides are limited to shots that actually need them;
• sidecar and embedded LUT metadata are understood;
• Highlight Recovery is checked for color artifacts;
• proxies are disabled when judging RAW changes;
• final delivery forces the intended debayer quality and uses native media;
• noise reduction is judged after the decode and viewing transform are correct.

The best BRAW setup is a coherent chain, not a magic preset. Either let RCM manage the raw input and output, or take manual control of the decode and add one matching normalization. Once it's clear who owns what, exposure, white balance, highlight recovery and the creative grade become deliberate choices, not repairs for a transform conflict you can't see.

Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.