# DaVinci Resolve Automatic Color Management vs Manual: Which Should You Use? > **Quick answer:** For most mixed-camera projects, start with DaVinci YRGB Color Managed and Automatic Color Management enabled, then verify the input and output. Choose custom color management when you need a specific timeline space, output transform, or deliberate per-camera mapping. Choose DaVinci YRGB with CST nodes when you want every transform visible and controlled in the node graph. *Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.* *Updated 2026-10-17 · DaVinci Resolve 21.1 (September 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-automatic-color-management-vs-manual* As of October 2026, DaVinci Resolve 21.1 is the current reference point for this decision. We run a 100,000+ member professional video-editing community, and color-management questions keep coming back because one checkbox can change how every clip enters a grade. TryUncle is the on-screen assistant for DaVinci Resolve on Mac and Windows. Ask in plain words and Uncle points at the exact control on your screen. ## What does automatic color management mean in DaVinci Resolve? Automatic color management means Resolve handles the project-level color transforms using its color-managed pipeline and a simplified set of processing choices. It can reduce setup work, but you still need to check whether Resolve has the right input interpretation and final output target. The name can confuse people because “automatic” is only one mode inside Resolve Color Management (RCM). It does not mean that Resolve makes creative grading choices for you, repairs incorrectly tagged media, or knows every camera file’s recording mode. It means that Resolve applies defined technical transforms in the background after you choose an overall processing mode and output. Blackmagic’s Colorist Guide for Resolve 20 describes the automatic setup as a simplified interface with SDR and HDR processing environments. It also explains that disabling Automatic Color Management exposes more processing and output choices. Resolve 21.1 is the current manual version as of September 2026; the exact labels can shift between releases, so use the current manual when a control appears in a different place. (Sources: [Blackmagic Design Colorist Guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf), [Blackmagic Design Support](https://www.blackmagicdesign.com/support).) A useful mental model is three spaces: what the source clip represents, where you do the grade, and what the deliverable must represent. In custom RCM, these are the Input Color Space, Timeline Color Space, and Output Color Space. In automatic mode, Resolve presents fewer choices, but the source-to-working-to-output logic still exists. **Automatic color management is a transform workflow, not an automatic grade.** An input transform interprets camera footage in its recorded color space and gamma. A working or timeline space is where grading operations happen. An output transform maps that result to the viewing or delivery standard. Blackmagic describes the purpose of color management as improving consistency in how camera images are decoded and displayed across formats and monitors. That consistency depends on a correct pipeline and a trustworthy display; the checkbox alone cannot guarantee either. (Source: [Blackmagic Design, DaVinci Resolve Color](https://www.blackmagicdesign.com/products/davinciresolve/color).) The “automatic” label also does not mean that a timeline automatically becomes color accurate on every computer. Viewer appearance depends on monitoring, operating-system display behavior, application settings, and the display itself. Resolve’s project output transform can be correct while a non-reference display still differs from a calibrated monitoring path. When a client reports a mismatch, separate the project pipeline from the viewing setup before regrading. # ## What “automatic” does and does not do In automatic RCM, Resolve can infer or use supported input information and maps it through the project’s processing mode toward the selected output. Some media carries useful metadata; some does not. Supported raw formats are handled differently from ordinary compressed video because raw decoding exposes camera-specific controls and metadata. Blackmagic’s Resolve 20 Colorist Guide states that supported raw formats are automatically detected and mapped through the working color space to the deliverable standard in project-level RCM or ACES. It also says input parameters affect non-raw media in those cases. That is a concrete reason not to treat every clip as though a manual input tag must be set: raw files and non-raw files have different paths. (Source: [The Colorist Guide to DaVinci Resolve 20](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf).) Automatic setup can identify a known recording profile, but it cannot reliably infer intent from every file. A Rec.709 delivery file, a log recording, a phone HDR clip, a screen recording, and an image sequence may all arrive in one timeline. If metadata is absent, misleading, or ambiguous, verify the input assignment yourself. A wrong automatic interpretation can produce a technically neat but visibly wrong image. “Manual” also has more than one meaning. Some editors use “manual color management” to mean DaVinci YRGB with Color Space Transform (CST) nodes in the grade. Others mean DaVinci YRGB Color Managed with Automatic Color Management turned off, then custom project-level input, timeline, and output choices. These are not identical implementations. The article compares all three approaches because the setup screen’s checkbox is only part of the decision. # ## Three setups people call automatic or manual | Resolve setup | Where the transforms live | What you control | Most useful when | Main risk | |---|---|---|---|---| | DaVinci YRGB Color Managed with Automatic Color Management on | Project color settings | Broad SDR or HDR processing mode and output target | A typical mixed-source project where a fast, coherent baseline matters | Assuming unknown media was identified correctly | | DaVinci YRGB Color Managed with Automatic Color Management off and custom settings | Project color settings | Input, timeline, output, tone mapping and related choices | You need a deliberate working space or output behavior with project-level management | Misconfiguring a setting that affects every clip | | DaVinci YRGB with CST nodes | Color-page node graph | Each input, working and output transform, plus node order | A node-based workflow, shot-specific transforms, or visible signal flow | Missing, duplicating, or misordering a transform | This comparison is about workflow and visibility, not quality in the abstract. Cullen Kelly’s side-by-side example in Frame.io Insider shows Resolve Color Management and CST nodes configured to produce the same image; he writes, “Which option is better is a bit of a misleading question. Neither is better. They both do fundamentally the same thing.” (Source: [Cullen Kelly, Frame.io Insider](https://blog.frame.io/2024/10/07/should-you-use-resolve-color-management-or-color-space-transforms-csts/).) The setup can differ even when the underlying conversion goal is equivalent. RCM stores transforms in project settings and applies them across the project. CST nodes make the transform chain visible at clip or group level. The choice changes how easily you review, share, troubleshoot, and adapt the pipeline, not whether one is inherently professional. ## Is DaVinci Resolve automatic color management better than manual? Automatic color management is the better starting point when it gives you the right image and output with fewer project-level decisions. Manual or custom control is better when you can name the specific transform behavior you need and can maintain it consistently. The word “better” should mean “safer for this project,” not “more cinematic.” For a beginner cutting phone footage, mirrorless log clips, and a few graphics into one SDR web delivery, automatic RCM may remove unnecessary setup decisions. For a colorist receiving a camera package with documented color spaces, matching a show LUT, and delivering multiple transforms, custom RCM or node-based CSTs can make the project easier to reason about. Resolve’s automatic mode uses a simplified processing model; custom RCM opens more choices. DaVinci YRGB is different again: it does not add project-level input and output transforms on your behalf. You can build the pipeline manually with CST nodes, camera LUTs, or other deliberate transforms. Blackmagic lists DaVinci YRGB and DaVinci YRGB Color Managed as distinct color science choices, and documents the broader color management controls in the project settings. (Sources: [Blackmagic Design Support](https://www.blackmagicdesign.com/support), [Blackmagic Design, DaVinci Resolve Color](https://www.blackmagicdesign.com/products/davinciresolve/color).) **The safest setup is the one whose input and output transforms you can explain.** A useful question is not “Do professionals use automatic?” Professionals use different workflows. Ask instead: Can I identify the color space of my sources? Do I need one delivery transform or several? Do my LUTs expect a particular signal? Will another editor understand where the transforms happen? What changes if I switch from SDR to HDR later? Those questions point to real differences in project risk. A project-level switch affects all relevant clips together, which can make a consistent change quick. It can also produce a large project-wide shift if the assumptions were wrong. Node transforms are local and visible, which helps inspect individual paths, but every clip or group needs the right chain. Neither method removes the need to verify representative shots. # ## Choose based on the project, not skill level A new editor can use custom RCM responsibly if they have a known camera profile and a target output. A working colorist can choose automatic RCM for a small edit with familiar sources. The goal is predictable image handling, not a badge of expertise. Use the following decision rule: 1. If you have ordinary SDR sources and one SDR destination, begin with automatic color management and verify the output target. 2. If you have log or wide-gamut footage from multiple cameras, confirm the input interpretation for each source family before grading. 3. If one project needs multiple delivery transforms, decide whether project-level outputs or explicit node paths make review clearer. 4. If a show LUT or supplied grade expects a named color space and gamma, build around that requirement rather than guessing. 5. If a team member must audit the signal flow, choose the setup that makes every transform easiest to locate and document. This avoids the trap of choosing manual just because a tutorial uses CST nodes. The tutorial may be demonstrating an elegant node tree for a specific camera or grading preference. It does not prove that automatic RCM is wrong for your footage. Likewise, a project preset is not proof that every clip has been identified correctly. # ## A practical default for ordinary projects For a project with mixed camera sources and a single SDR web delivery, start with Resolve Color Management and automatic mode. Set the output to the intended SDR target, bring in a few representative clips, check whether their contrast and color look plausible, and confirm any known log clips’ input spaces. Then test a render in the destination player or platform context you actually care about. This is a starting point, not a universal recipe. A social media video may be watched on phones with varied display settings. A broadcast deliverable can have formal signal requirements. A theatrical or HDR finish has different monitoring and output demands. Color management organizes the transforms; it cannot choose your delivery specification for you. The more unusual the job, the less useful a one-line default becomes. A documentary with archival footage, a phone screen recording, drone log, and an animation render needs a source inventory. An interview recorded on one camera in one format may not. In both cases, a correct output space matters, but the amount of input triage differs. ## When should I use automatic color management? Use automatic color management when you want Resolve to manage the broad technical pipeline at project level and your media fits the available processing mode. It is especially practical for a single output target, mixed supported sources, and an editor who wants the color pipeline to remain separate from the creative grade. Resolve 20’s Colorist Guide describes the Automatic Color Management controls as two simplified working environments, SDR and HDR, with explanatory text in the interface. In the guide’s setup exercise, Blackmagic chooses DaVinci YRGB Color Managed, enables Automatic Color Management, and then selects an SDR or HDR processing mode based on the footage and delivery. The current Resolve 21.1 manual should be consulted for version-specific details, but the basic decision remains: select a mode that reflects the job, then verify what happens to your media. (Source: [The Colorist Guide to DaVinci Resolve 20](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf).) Automatic mode is useful when you value a clean project structure. One place controls the general pipeline. You can grade the clips without adding a technical input and output transform node to every clip. You can also change the output target from the project settings instead of rebuilding a node chain for each deliverable, depending on the project design. # ## Good-fit projects for automatic mode Automatic mode often fits a short-form project shot on current cameras, with one standard delivery target and a small number of known source types. It can also fit a multi-camera edit when Resolve supports the raw formats and each non-raw camera profile is known or easy to assign. It is a useful teaching setup because it makes a complete pipeline available before the student has memorized every transform concept. That does not mean the student should ignore the pipeline. A fast workflow is only helpful if they can recognize the difference between a camera log image, a correctly transformed image, and an image that has been transformed twice. A good automatic setup still needs a media check. Scrub through examples from each source family, not just the first clip. Inspect the brightest highlights, saturated colors, and skin tones. Check footage shot in a different frame rate or recording mode if that mode changes the camera’s profile. A “same camera” label alone does not prove that two files share the same encoding. The route is useful when the deliverable is singular. One timeline intended for one SDR target has fewer output-management decisions than a campaign that must create SDR web, HDR streaming, and a cinema master. There are ways to create multiple outputs from a shared grade, but you need to choose and test that strategy deliberately. # ## What automatic mode will not decide for you Automatic mode does not decide whether your creative grade should be warm, neutral, contrasty, or muted. It does not choose the right exposure, fix clipped highlights, or know whether a LUT was designed for a log input or a display-referred image. Those remain creative and technical decisions. It also cannot repair bad source metadata. A mislabeled file can be processed consistently and still look wrong. If a camera operator recorded in a less common profile, used a custom setting, or transcoded the original media without preserving tags, check the camera documentation or production notes. Do not compensate for a wrong input transform by bending the grade until the image looks approximately plausible; that makes later shots harder to match. A project can have both automatic management and manual corrections. You may manually assign an input space to an individual clip, use a CST for an unusual element, or change the output target. “Automatic” is not a promise that no clip-level intervention is allowed. The practical difference is where Resolve gets its transform instructions by default and how much responsibility you accept for setting exceptions. For example, imagine footage from a supported RAW camera mixed with an H.264 log clip from another camera and a Rec.709 graphic. Resolve’s RAW decoder can expose camera-specific controls for the raw clip. The compressed log clip may need a clear input assignment. The graphic may already be display-referred. Treating all three as the same input space would be an error, even if automatic project management is enabled. ## When should I choose custom color management or manual CST nodes? Choose custom RCM when you need project-level control over input, timeline, and output spaces. Choose CST nodes when you want the transforms visible and editable in the node graph, or when a deliberate node pipeline is easier for your team to review. Custom RCM and CST nodes are both ways to control transforms. In Cullen Kelly’s Frame.io comparison, the project-level RCM setup uses a custom timeline space and selected input and output behavior; the CST setup represents the same kind of input-to-working-to-display path with nodes. Kelly demonstrates that those configurations can lead to the same displayed result, while the preferred interface depends on how the colorist wants to work. (Source: [Cullen Kelly, Frame.io Insider](https://blog.frame.io/2024/10/07/should-you-use-resolve-color-management-or-color-space-transforms-csts/).) Use custom RCM when you want a centralized project pipeline but the simplified automatic controls do not expose the specific spaces or tone-mapping choices you need. The settings stay in project settings, which can make a global handoff easier to inspect. Custom RCM is not “manual” in the sense that you are hand-converting every pixel; Resolve still applies the transforms after you define the pipeline. Use CST nodes when your grade should show the transform chain. A common structure is an input transform, creative grade nodes, then an output transform. The CST effect lets you specify an input color space and gamma and an output color space and gamma. A colorist may add tone mapping, gamut mapping, or other options depending on the workflow. Cullen Kelly’s published example uses a source-to-working CST, middle nodes for the grade, then a working-to-display CST. That article is an example, not a universal node recipe. (Source: [Cullen Kelly, Frame.io Insider](https://blog.frame.io/2024/10/07/should-you-use-resolve-color-management-or-color-space-transforms-csts/).) **Manual control earns its extra steps when those steps answer a real delivery or grading need.** # ## Why make transforms visible in nodes? A node tree can make the image’s route legible. A teammate can see where camera footage becomes a working image, where creative adjustments happen, and where the result is mapped to the display or output space. That visibility helps when a project contains different cameras, different LUT expectations, or different treatment for a particular clip. A visible pipeline also makes it easier to isolate a fault. Bypass the input transform and see whether the source is interpreted as expected. Bypass the output transform and see whether a display mapping causes the unwanted rolloff. Compare a known-good camera shot against a suspect one. The node graph does not solve the problem by itself, but it can show you where to look. Cullen Kelly’s node workflow article explains grouping clips shot in a common camera color space, then applying shared transforms through group nodes. The advantage is practical: if several clips share the same source profile, one group-level treatment can reduce repeated node work, while clip-level nodes remain available for shot-specific adjustments. Grouping still depends on accurate source identification. (Source: [Cullen Kelly, Frame.io Insider](https://blog.frame.io/2024/01/08/color-management-nodes-davinci-resolve/).) Visible nodes can also help preserve a creative grade when the project’s technical interpretation changes. If your transforms are separated from the look nodes, you can inspect whether the look itself depends on a particular working space. That is useful in a handoff, but it is not a guarantee that the grade will look identical after you change the pipeline. Grading operations are affected by the space in which they run. # ## Why keep transforms in project settings? Project-level RCM centralizes the technical decisions. If the whole project uses a common working space, it can be simpler to set that space once than to build and maintain repeated nodes. It may also make output changes more straightforward, because input and output transforms remain distinct from the creative nodes. This centralized approach is helpful when another editor should not accidentally delete the camera transform while cleaning up a node tree. It is also useful when you want to compare or change project-wide settings from one control panel. The tradeoff is that the transforms may be less obvious to someone inspecting an individual clip’s node graph. Document the project settings in the handoff, especially when working across versions or teams. There is no rule that custom RCM is only for facility work or that CST nodes are only for freelancers. The choice depends on how you and your collaborators prefer to represent the signal path. A centralized project setting can be highly controlled. A node chain can be highly repeatable. Neither method automatically makes a pipeline more accurate. # ## When a show LUT or shared PowerGrade is involved A LUT has an expected input and output. If a look LUT expects a camera log signal and you feed it a display-referred Rec.709 image, the result can be wrong. If a creative LUT expects a particular wide-gamut working space, placing it after an unrelated transform can also change its behavior. Before switching management systems, find the LUT’s documented input and output or the grade author’s instructions. The same is true for a shared PowerGrade. A node tree may contain CST effects, LUTs, or assumptions about the working space that are not obvious from the thumbnail. Inspect the nodes and identify the transform order before applying it to a different project. A PowerGrade that was built for DaVinci Wide Gamut/Intermediate may not behave as intended in a Rec.709 timeline if its technical transforms are absent. If the grade contains its own input and output CSTs, avoid adding another project-level transform without understanding how the two interact. That is a common route to double transforms. If the project-level settings already convert camera log to a working space and output, a node-level input conversion can map the image a second time. Use one clearly defined pipeline, or document the exact reason for a hybrid. ## How do I choose settings for a real project? Choose the project setup by listing source formats, intended output, required looks, and handoff needs before grading. Then test one representative clip from each source family and confirm the rendered output, rather than relying on a preset name alone. The following scenarios show how the choice works in practice. They are workflow examples, not claims that one camera or delivery always requires one setting. Record exact camera mode, transfer function, gamut, and output specification whenever those details are known. # ## Example 1: One mirrorless camera, log footage, SDR web video If every shot comes from one camera in a known log profile and the final video is a single SDR web master, automatic RCM may be enough. Select a suitable SDR processing path, confirm that the log input is interpreted correctly, then grade and check the result on the intended output path. A small project does not automatically require CST nodes. If the source is consistent and there is one output, project settings may be the cleanest place to manage the transform. Conversely, if a tutorial, supplied grade, or team workflow expects explicit CST nodes, you can use those. Pick the method that matches the real requirements and makes mistakes easy to spot. Before grading, note whether the camera recorded log in a standard profile or whether a manufacturer LUT was baked into the file. If a display transform is already baked in, a second log-to-Rec.709 transform can make contrast and saturation excessive. If the file is still log, treating it as Rec.709 can leave it flat. Those visual clues point to the input assumption, but camera metadata and recording notes are stronger evidence. # ## Example 2: Two cameras with different log profiles A two-camera interview may combine one camera’s log profile with another manufacturer’s log profile. Automatic RCM can still work if Resolve identifies each profile correctly or you assign the non-raw inputs. The test is whether both cameras arrive in a comparable working space before the creative matching grade. If one source is unsupported, mislabeled, or untagged, assign the input space for that source. In custom RCM, select or override the relevant Input Color Space. In a node-based workflow, use a CST with the correct input gamut and gamma for that camera. Avoid applying one camera’s technical LUT to the other camera just because the scenes need to match. Once both shots are correctly normalized, match exposure and white balance, then make creative choices. Color management can align technical encoding; it does not make two sensors, lenses, lighting conditions, or exposure decisions identical. A colorist still has to match the actual images. When grouping clips, group by actual encoding and processing requirements, not just by the camera label. The same camera may record different log profiles, gamut settings, or baked looks under different modes. A group should represent a meaningful shared technical path. # ## Example 3: Camera log footage plus phone HDR clips Phone HDR media complicates a simple SDR project because it may use an HDR transfer function and metadata that differ from ordinary SDR footage. Automatic RCM can help map known media toward the chosen output, but check that the phone files are interpreted as HDR and that the selected output is what you intend to deliver. Do not judge by a thumbnail alone. Look at the brightest regions and saturated colors in the viewer and scopes, and render a short sample. If the output is SDR, confirm that highlight handling is acceptable. If the deliverable is HDR, confirm that the display path and output settings match that target. The same clip can appear very different when its input or output assumptions change. For a project that mixes SDR and HDR sources, identify which source is in which category. Resolve’s automatic mode offers SDR and HDR processing choices in the documented Resolve 20 interface, but the correct mode depends on the project’s processing and delivery goal. Review the current Resolve 21.1 documentation for the exact labels and options. (Source: [The Colorist Guide to DaVinci Resolve 20](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf); current manual listing: [Blackmagic Design Support](https://www.blackmagicdesign.com/support).) # ## Example 4: Rec.709 camera files and graphics If a camera file is already Rec.709 and your title cards or screenshots are also standard display-referred graphics, an SDR output is a sensible baseline. Color management still matters because Resolve needs to know what the sources represent and what the output expects. Avoid sending already display-referred material through a transform intended for camera log unless that is deliberate. This is where a broad “put a CST on everything” tutorial can go wrong. The camera log clip may need a camera-to-working transform. The graphic may already be in an RGB display space. The two sources can both sit in the same timeline without sharing an identical input transform. Check a white graphic and a saturated brand color alongside the camera footage. If the graphic suddenly becomes too contrasty or shifts hue after a pipeline change, inspect whether the graphic has been treated as log or passed through an unintended transform. Correcting the input path is safer than dialing down saturation on every graphic element. # ## Example 5: Multiple outputs from one graded timeline A project that must deliver SDR and HDR, or web and broadcast variants, needs an explicit output plan. Project-level RCM can keep a common grade in a working space and apply a selected output transform, but you should determine how each deliverable will be generated and validated. A CST workflow can make each output path visible in a node or timeline structure, though it can require more organization. Do not assume that an SDR grade becomes an HDR master by changing one output menu. Highlight detail, saturation behavior, display brightness, tone mapping, and creative intent all matter. A transform can map values; it cannot decide which highlights should feel bright or how the look should adapt to a new display target. If the outputs need different creative intent, consider separate timelines or versions that share common corrections but allow output-specific adjustments. Keep the relationship between the versions clear. A client should be able to tell which file is the approved SDR master and which is the HDR version, and another editor should be able to locate the settings that generated each. # ## Example 6: A project with an external LUT package Read the LUT documentation before selecting a project pipeline. Some LUTs expect a particular camera log input. Others expect a normalized working space or a Rec.709 image. The LUT’s filename is not enough to establish its expected signal. If the LUT expects a camera log input but automatic RCM has already transformed that image into a working space, placing the LUT after the project transform may be incorrect. One option is to use a manual node pipeline that feeds the LUT what it expects. Another is to use a color-managed LUT workflow if the LUT and Resolve support the intended mapping. The right answer depends on the LUT’s documented design. Keep a clean test timeline with one representative shot. Compare the LUT’s expected input against the actual node position and project transform. Bypass transforms one at a time. If you cannot explain what signal enters and leaves the LUT, do not paste it across the whole timeline yet. ## Why does automatic color management make my footage look wrong? When automatic color management makes footage look wrong, first check the input interpretation and whether another transform is already active. Then check the timeline processing mode and output target before altering the creative grade. A drastic image shift after enabling RCM usually means the new pipeline is doing something different from the old pipeline. That is expected if the old project had no input transform or if manual nodes were already converting the footage. The goal is to identify the extra or missing transform, not to undo every change by eye. **A wrong input tag can make a correct output transform look completely wrong.** # ## Why is my log footage washed out in DaVinci Resolve? Washed-out log footage commonly means the image is being viewed without the intended log-to-working or log-to-display transform, or that Resolve is treating it as a different input than the camera recorded. Check the camera’s recording profile and the clip’s input assignment first. In automatic RCM, confirm the project is using DaVinci YRGB Color Managed and inspect the relevant input information. In custom RCM, check the clip’s Input Color Space. With CST nodes, confirm both input color space and input gamma. A mismatch between gamut and gamma can produce a less obvious but still incorrect result. Do not add contrast and saturation until the transform path is confirmed. A creative correction can hide a technical mismatch on one shot and make matching impossible on the next. Return to a known source interpretation, then grade from there. # ## Why does my footage look too contrasty or oversaturated? A harsh image can indicate a double transform, such as a camera LUT or CST applied on top of a project transform that already converted the signal. It can also happen if a LUT receives an input space it was not designed for. Inspect the full chain: camera decoding, project-level input, clip or group nodes, timeline processing, and output transform. Disable one candidate transform at a time on a duplicate or test clip. If removing one node restores a plausible image, check whether that node duplicates a project-level conversion. Another possibility is that the camera file already has a look or display conversion baked in. If so, treating it as log and applying a log-to-display transform again adds contrast and saturation. Confirm how the media was recorded or transcoded before changing the grade. # ## Why is my image flat after I turn on automatic color management? A flat image after enabling automatic management can mean the selected processing mode or output does not match the footage and target. It can also mean the footage itself was already converted, while Resolve now interprets it as log or wide gamut. Compare a known Rec.709 clip with a known log clip. If the Rec.709 clip looks normal and the log clip looks flat, inspect the log input assignment. If both look wrong, check the project output space and any global transform. If only one camera family looks wrong, focus on that family’s input tagging or decoding. The viewer’s appearance also depends on the display pipeline. If the image looks different in Resolve than in an exported file or another player, check whether the difference is caused by the player, operating system, monitor profile, or export tagging. Do not change the project’s creative grade until you know which comparison path is trustworthy. # ## Why does a clip ignore my project input color space? A clip may not follow a general project input assumption because Resolve handles certain raw formats through their raw decoding controls, or because the clip has an explicit override. Inspect the clip’s camera raw settings, metadata, and input assignment before assuming the project setting applies uniformly. Blackmagic’s Resolve 20 Colorist Guide says supported raw formats are automatically detected in project-level RCM or ACES, mapped to the working space, and transformed to the deliverable standard; it notes that input parameters then affect non-raw media. That describes a meaningful distinction between RAW and non-RAW workflow. For the exact controls in Resolve 21.1, consult the current manual listed in Blackmagic Support. (Sources: [The Colorist Guide to DaVinci Resolve 20](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf), [Blackmagic Design Support](https://www.blackmagicdesign.com/support).) A clip can also have a clip-level color space override that takes precedence over the project’s default assumption. If a clip behaves differently from its neighbors, compare its context menu input assignment with a known-good clip from the same camera mode. Avoid assigning a new profile across a large selection until you know the selection contains one recording format. # ## Why did the image change after I switched from automatic to manual? The image changed because the transform path changed. Automatic RCM, custom RCM, DaVinci YRGB with CSTs, ACES, and LUT-based workflows can use different input assumptions, working spaces, tone mapping, and output transforms even when they aim at the same display. Before switching, duplicate the timeline or project. Write down the existing color science, processing mode, output space, and any clip-level overrides. Then inspect the manual setup for duplicate transforms. Compare the same still frames before and after the change, including skin, highlights, and saturated colors. If you are moving from project-level RCM to CST nodes, the goal is to rebuild the transform path intentionally. The conversion is not necessarily a one-click translation. If you are moving from CST nodes into RCM, remove or bypass the node transforms that the project will now perform, or you may convert twice. # ## Why do my colors change in the export or on another screen? A color difference between the Resolve viewer, export, and another screen can come from output color space, tagging, playback color management, operating-system display handling, or monitor calibration. First identify where the difference appears: inside Resolve, in a specific player, or on a second display. Check that the project output matches the delivery target and that the render is tagged appropriately. Then compare the same file in a known color-managed viewing path. A consumer display is not a reference monitor, and the viewer on a laptop is not a guarantee of how every phone or television will display the result. Blackmagic’s description of color management explicitly frames its goal as more consistent decoding and display across formats and monitors. Consistency is a system outcome, not a promise that every uncalibrated display will match. (Source: [Blackmagic Design, DaVinci Resolve Color](https://www.blackmagicdesign.com/products/davinciresolve/color).) If the file is technically correct for its target but a particular platform shifts it, document the discrepancy and test that platform’s playback behavior. Don’t create several conflicting grades to chase every screen unless the delivery calls for platform-specific masters. A calibrated monitoring path and known output settings make troubleshooting more meaningful. Uncle can point to the color-management control on your screen while you check your own Resolve project. ## How do I switch between automatic and manual without breaking a grade? Switch by duplicating the project or timeline, recording the existing pipeline, and changing one part at a time. Keep a set of representative stills so you can compare the source interpretation, grade behavior, and output after the change. A safe change is controlled, reversible, and documented. Project color management affects the image pipeline, so switching after grading can alter how existing corrections behave. Cullen Kelly’s comparison emphasizes that RCM and CST nodes perform the same basic transform task when configured equivalently, but the interface and configuration differ. (Source: [Cullen Kelly, Frame.io Insider](https://blog.frame.io/2024/10/07/should-you-use-resolve-color-management-or-color-space-transforms-csts/).) # ## Before changing the color science First, capture the current setup. Note the color science, automatic setting, processing mode, input and output spaces, timeline space if visible, output tone mapping, camera raw settings, and any LUT or CST nodes. Save a project version and duplicate the timeline if you are changing a single sequence. Next, select a small test set: one clip from every camera or recording profile, one graphic, one clip with a LUT, and one shot with important highlight or skin-tone detail. If a source family has several record modes, include an example of each. The goal is not to compare every frame; it is to expose the assumptions most likely to break. Then make the new pipeline. Avoid changing the project mode and adding new nodes in the same step. If moving to manual CSTs, decide whether the project should use DaVinci YRGB, then build an input-to-working transform, grade nodes, and output transform for each distinct source path. If moving to project-level RCM, remove or bypass technical nodes that would duplicate its work. Render short tests to the actual target. A still comparison in the viewer catches some issues, but a render can reveal output tagging or playback differences. Keep the old version until collaborators have reviewed the result and the handoff notes are complete. # ## A review checklist for the converted timeline - Does every camera family have the correct input interpretation? - Does any clip or group override the project assumption? - Is raw footage being decoded through camera raw controls rather than an unnecessary non-raw transform? - Does each CST have the correct input color space and gamma? - Is a camera LUT or creative LUT receiving the expected signal? - Is there only one intended output conversion in the path? - Does the timeline working space suit the grade and any required tools? - Does the output space match the delivery specification? - Do important highlights and saturated colors behave as intended? - Does a rendered sample look consistent in the expected playback path? This checklist catches structural mistakes before they become creative workarounds. If a shot looks wrong, find the incorrect assumption and fix it where it enters the pipeline. A global look adjustment is rarely the right fix for one camera’s incorrect input tag. ## Is automatic color management or manual color management easier to learn? Automatic color management is easier to start with because it exposes fewer choices, while manual CST workflows can teach the transform chain more visibly. Neither replaces understanding what the camera recorded and what the output needs. The best way to learn DaVinci Resolve color management is to work from a real source file toward a known destination. Blackmagic’s official training includes a Color Management lesson listed at 31 minutes, with a project file, and its Colorist Guide offers a structured exercise. That is a strong free baseline because the examples and controls come from the software’s maker. (Sources: [Blackmagic Design Training](https://www.blackmagicdesign.com/products/davinciresolve/training), [The Colorist Guide to DaVinci Resolve 20](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf).) YouTube educators such as Casey Faris can be useful when you want to see someone click through a complete example. The tradeoff is that a video may use a particular camera, Resolve version, or output target. Pause and map each setting to your own clip rather than copying a tutorial by label alone. A video is a demonstration, not a substitute for the clip’s recording metadata. Reddit discussions can help surface edge cases and show how other editors reason about a problem. They vary in context and expertise, so verify technical claims against Blackmagic’s current manual or a reproducible project. Udemy or Coursera can provide a paced course and a sequence of lessons, but a course still cannot see which clip or color-management panel is open in your current project. | Learning route | Good for | Limitation for this exact decision | |---|---|---| | Blackmagic official training and guide | A source-authoritative introduction and project files | You still need to apply the lesson to your own footage and delivery | | YouTube, including Casey Faris tutorials | Seeing a complete screen demonstration and workflow | Resolve version, camera profile, and output may differ from yours | | Reddit and editor forums | Comparing real troubleshooting approaches | Advice may omit the media metadata or project settings needed to judge it | | Structured courses on Udemy or Coursera | Guided progression through broader color topics | A prerecorded course cannot inspect your active project state | | TryUncle | Getting guidance while working inside Resolve | It does not replace learning the color pipeline or making the creative grade | We have taught more than 100,000 students on Udemy and are an official Udemy Business Partner, so we know what a structured course can do well: explain a concept in order and give learners repeatable practice. For a setting-specific question, the missing piece is often context. You need to know which source clip is selected, which project mode is active, and which control applies to that situation. TryUncle’s role is narrower. Uncle sees the screen and can point to the relevant control while you work through a question in your own Resolve project. It does not automatically edit footage or decide the correct creative look. If you are stuck on which input space to inspect, [TryUncle](https://tryuncle.com/) can provide on-screen guidance for DaVinci Resolve on Mac and Windows. The official Blackmagic guide remains the best place to learn the complete technical model. **A tutorial teaches a workflow; your media metadata decides whether that workflow fits.** ## Which should I choose: automatic, custom RCM, or CST nodes? Choose automatic RCM for a reliable starting pipeline, custom RCM for project-level precision, and CST nodes when explicit signal flow in the node graph matters. Choose the method you can verify and hand off without hiding assumptions. The choice is not a permanent identity. A one-camera social edit may use automatic RCM; the next job may require a custom output transform or a node-based pipeline for a show LUT. You can change approaches between projects. Within one project, keep hybrid paths deliberate and label them so another editor can tell which transforms are active. | Choose this | If your priority is… | Check before you commit | |---|---|---| | Automatic RCM | A fast project-level baseline with a simple processing choice | Correct source interpretation, SDR/HDR mode, and output target | | Custom RCM | Specific input, timeline, output, or tone-mapping control at project level | Each camera profile, output requirement, and team handoff note | | CST nodes in DaVinci YRGB | Transform visibility, per-clip control, or a node-centric grade | Input gamut and gamma, transform order, LUT expectations, duplicate conversions | | ACES | A standardized pipeline required by a project or facility | The ACES version, input/output transforms, and team delivery requirements | ACES is a separate color-management system in Resolve, not another name for automatic RCM. Blackmagic says Resolve supports its own color-management system and ACES as defined by the Academy of Motion Picture Arts and Sciences. If you are choosing among RCM and ACES, use our [Resolve Color Management vs. ACES comparison](https://tryuncle.com/learn/davinci-resolve/resolve-color-management-vs-aces-which-should-i-use) and [plain-language ACES explainer](https://tryuncle.com/learn/davinci-resolve/what-is-aces-color-management-explained-simply). (Source: [Blackmagic Design, DaVinci Resolve Color](https://www.blackmagicdesign.com/products/davinciresolve/color).) Choose automatic if a correct input and output path is in place and you do not need to expose more controls. Choose custom RCM if you can name the project-level setting automatic mode does not give you. Choose CST nodes if the signal path should be inspected and adjusted in the node graph. Choose ACES when the project’s pipeline calls for ACES, not because its name sounds more advanced. If a CST conversion produces an unexpected color shift, see our guide to [why a Color Space Transform can desaturate footage](https://tryuncle.com/learn/davinci-resolve/why-does-color-space-transform-desaturate-my-footage-in-davinci-resolve). The useful next step is to verify input gamut, input gamma, output settings, tone mapping, and whether another transform is already active. There is no requirement to use the most complex method. There is a requirement to understand the method you choose well enough to avoid a hidden double conversion and deliver the intended image. Start simple, keep a reproducible test, and add control only when the project asks for it. ## What is the final verdict for DaVinci Resolve automatic color management vs manual? For most editors, automatic RCM is the right first test, not an unquestioned final answer. Keep it if representative clips map correctly to the intended output; move to custom RCM or CST nodes when you need a specific control, a visible transform chain, or a documented delivery workflow. The important distinction is this: Automatic Color Management simplifies setup inside Resolve Color Management. Custom RCM exposes more project-level choices. DaVinci YRGB with CST nodes puts the conversions into the node graph. Each can produce a sound image when the inputs, working space, and output are correctly configured. Blackmagic’s official learning material is a good place to ground the concepts. Cullen Kelly’s practical comparisons show how project-level RCM and node-based CSTs can produce equivalent conversions while supporting different working habits. For your own project, the decisive evidence is the source recording profile, the pipeline already in the project, and the delivery requirement. If you are beginning today, use automatic color management on a copy or a clean project, inspect one clip per source type, and check a short render. If one clip fails, investigate its input before rebuilding the entire project. If a team or client has specified a pipeline, follow and document that pipeline. Then grade the image creatively. That is the practical answer to “davinci resolve automatic color management vs manual”: start with automatic for simplicity, switch for a reason you can state, and verify the image at the output you actually need. ## FAQ ### Is automatic color management better than manual in DaVinci Resolve? Automatic color management is usually the quickest safe starting point for ordinary projects with mixed camera formats and a known delivery target. Custom project settings or CST nodes are better when you need deliberate input, timeline, output, or node-level control. ### Does DaVinci Resolve automatic color management recognize every camera file? No. Resolve can use supported raw metadata and known input profiles, but an untagged or ambiguous file may need a manually assigned Input Color Space or a transform node. ### Why does my footage look washed out after turning on color management? A flat image often means a log input was interpreted as Rec.709, or a conversion was applied twice. Check the clip input space, project color science, node transforms, and output space before changing the grade. ### Should I use DaVinci YRGB Color Managed or CST nodes? Use DaVinci YRGB Color Managed when you want input, timeline, and output transforms managed at the project level. Use CST nodes in DaVinci YRGB when you need to see and tailor those transforms in the node graph. ### Can I change automatic color management to manual after grading? You can change project color settings, but the image may change because the transform pipeline changes. Duplicate the project or timeline first, document the current input and output settings, then compare representative clips before committing. ## Sources - [DaVinci Resolve 21.1 Manual, Blackmagic Design Support](https://www.blackmagicdesign.com/support) - [The Colorist Guide to DaVinci Resolve 20, Blackmagic Design](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf) - [DaVinci Resolve Color, Blackmagic Design](https://www.blackmagicdesign.com/products/davinciresolve/color) - [DaVinci Resolve Training, Blackmagic Design](https://www.blackmagicdesign.com/products/davinciresolve/training) - [Should You Use Resolve Color Management or CSTs?, Cullen Kelly, Frame.io Insider](https://blog.frame.io/2024/10/07/should-you-use-resolve-color-management-or-color-space-transforms-csts/) - [How to Color Manage using Nodes in DaVinci Resolve, Cullen Kelly, Frame.io Insider](https://blog.frame.io/2024/01/08/color-management-nodes-davinci-resolve/) - [DaVinci Resolve 21 announcement, Blackmagic Design](https://www.blackmagicdesign.com/media/release/20260414-01)