# DaVinci Resolve Input Color Space: Clip vs Project

> **Quick answer:** In DaVinci Resolve Color Management, the project Input Color Space is the default for clips without their own assignment. A clip-level Input Color Space overrides that default for that media. Set the project default for your common source, assign exceptions at clip level, and verify the camera’s actual gamut and gamma before grading.

*Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.*
*Updated 2026-11-02 · DaVinci Resolve 21.1 (September 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-input-color-space-clip-vs-project*

I would not start by choosing a color space from a list that merely looks familiar. I would first identify what the camera recorded, then decide whether the project default or a clip-specific assignment should describe that source. As of October 2026, the current release is DaVinci Resolve 21.1, and this guide focuses on Resolve Color Management rather than a hand-built Color Space Transform node pipeline. [Blackmagic Design lists the 21.1 manual and update on its support page.](https://www.blackmagicdesign.com/support)

## What is the difference between DaVinci Resolve Input Color Space clip vs project?

The project Input Color Space is a default interpretation for clips that do not have an individual assignment; a clip-level Input Color Space specifies the source interpretation for that clip instead. In DaVinci YRGB Color Managed, Resolve uses source, timeline, and output transforms together, so the input choice is only one part of the pipeline. [Blackmagic’s Resolve Color page describes these input, timeline, and output transformations](https://www.blackmagicdesign.com/products/davinciresolve/color), and the [DaVinci Resolve 20 Colorist Guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf) explains assigning the source color profile and selecting the project’s working and delivery spaces.

Think of the project value as a default rule, not a command that makes every clip identical. If your project default is Rec.709 Gamma 2.4, a clip with no individual input assignment uses that default. If you explicitly assign an appropriate camera gamut and gamma to a log clip, that clip is interpreted according to its own assignment. The rest of the project can still use the project default.

That difference matters most when one timeline contains material from multiple cameras or recording modes. One camera might produce ordinary Rec.709 video, while another records a log image. The clips may sit beside each other in the same timeline, but they do not necessarily have the same source encoding. A single project default cannot accurately describe two genuinely different encodings at once. The default can cover the common case; clip-level assignments can describe exceptions.

This is not a choice between “correct project settings” and “correct clip settings.” Both have a job. The project default fills in for unassigned media, while an explicit clip assignment tells Resolve how to interpret that particular media instead. If all clips share one encoding, a project default may be all you need. If they do not, you need a deliberate method for identifying and assigning the differences.

There are three color-space questions people often collapse into one:

| Setting | What it describes | Where you set it | What it is not |
| --- | --- | --- | --- |
| Input Color Space | The color characteristics of source media entering the managed pipeline | Project Settings for a default, or an individual media assignment | The project’s final export setting |
| Timeline Color Space | The working space into which managed sources are transformed for grading | Project color-management settings | A camera’s recording format |
| Output Color Space | The target display or delivery space for viewing and output | Project color-management settings | A correction that repairs incorrectly identified source media |

Resolve’s official description presents input, timeline, and output as distinct transformations. A source assignment tells Resolve how to read the media. Timeline settings define the working environment. Output settings direct the result toward the intended display or delivery target. [Blackmagic’s color-management overview](https://www.blackmagicdesign.com/products/davinciresolve/color) is the primary reference for that three-part distinction.

**In a color-managed project, a clip-specific input assignment takes precedence over the project’s input default for that clip.**

Use that rule carefully. It does not mean Resolve always guesses every camera format correctly, and it does not mean that an input setting is a grade. It describes the interpretation that comes before the creative corrections in a managed pipeline. If the interpretation is wrong, the rest of the grade begins from the wrong image.

## Should I set Input Color Space in Project Settings or on each clip?

Set the project Input Color Space to the source format you expect to use as the default, then assign clips individually when their source format differs. This keeps the project settings useful without forcing a single input interpretation onto every camera, recording mode, or pre-processed clip.

A project-level default is a good fit when the project is built around one consistent source. A one-camera interview, a short film shot entirely in one log format, or a collection of screen recordings encoded consistently may not need individual overrides. In that case, a sensible project default reduces repetitive setup. You still need to confirm that the selected setting matches the actual source.

Clip-level settings become important when sources differ. Imagine a short documentary with a log camera, a second camera recording a different log curve, and a phone used for a few pickup shots. If the project default represents the main camera, the other two sources may need their own clip-level assignments. The project default can remain useful for the majority, while exceptions are explicit rather than hidden in the grade.

Use this decision matrix before changing anything:

| Footage situation | Project Input Color Space | Clip-level assignment | Why |
| --- | --- | --- | --- |
| All source clips share one known camera encoding | Set that source as the project default | Usually not needed unless a clip differs | The default accurately describes the unassigned clips |
| Most clips share a format, with a few exceptions | Set the common format as the project default | Assign each exception to its actual source format | One default handles the majority; overrides handle the rest |
| Several cameras record different log formats | Choose a deliberate default, often the dominant source format | Assign each camera group or clip correctly | Different source encodings need different input interpretations |
| Footage is already normalized to a known display space | Set a matching default only if it applies to the unassigned clips | Override log or other non-matching sources | Avoid transforming normalized footage as if it were still log |
| Source format is unknown | Do not guess based on appearance alone | Verify camera, recording mode, and metadata first | A plausible-looking image does not prove the input transform is right |
| Project uses plain DaVinci YRGB | Project Input Color Space is not functioning as a Resolve Color Management default | Use an intentional manual workflow if appropriate | Plain DaVinci YRGB is not the same as DaVinci YRGB Color Managed |

The last row matters. DaVinci YRGB and DaVinci YRGB Color Managed are different project color-science modes. Blackmagic describes project-level color management as the place to define input, timeline, and output transformations. A manual node workflow can use Color Space Transform effects or other explicit processing, but do not assume the project input default is controlling that workflow. [Blackmagic’s color-management page](https://www.blackmagicdesign.com/products/davinciresolve/color) describes Resolve Color Management and ACES as distinct supported systems.

For a mostly single-camera project, avoid making the workflow more complicated just because the menu offers many choices. Set the project default to the actual common source, review a representative clip, and identify exceptions. For a mixed-format job, do the reverse: identify the sources first, group by camera or encoding, and apply clip assignments in a controlled pass. That is easier to audit than assigning settings opportunistically while grading.

A practical rule is: project default for the ordinary case, explicit clip assignment for a verified exception. If you cannot say what a source was recorded as, pause before selecting a transform. Ask the camera operator, check the camera’s recording settings, inspect trustworthy metadata, or consult the source documentation. Guessing from a washed-out or saturated preview is not reliable evidence.

## Why is the project Input Color Space not changing every clip?

The project Input Color Space only supplies a default for clips without their own input assignment, so clips that already have individual settings can keep a different interpretation. Some project color-management modes also use automatic or preset behavior that changes which controls are available or how much manual input selection you need.

Start by selecting two source clips that appear to behave differently. Check the project’s Color Science mode and input settings, then inspect each clip’s assigned input value if the project uses DaVinci YRGB Color Managed. If one clip has an explicit assignment, changing the project default is not expected to replace that assignment. It should affect only media that still inherits the default.

This can create a confusing result. You change the project Input Color Space, but the key shot in the viewer does not change. That is not necessarily a bug. The shot may already have a clip-specific value. Another possibility is that the selected timeline item is not the original source clip you think it is, or the project is using plain DaVinci YRGB rather than the managed mode.

Run this diagnostic in order:

1. Open Project Settings and go to Color Management.
2. Confirm the project’s Color Science mode. Distinguish DaVinci YRGB Color Managed from DaVinci YRGB.
3. Note the project Input Color Space or the selected color-management preset.
4. Select a source clip in the Media Pool, not just a timeline segment or a derived composition.
5. Inspect the clip’s context menu for its current Input Color Space assignment.
6. Compare a clip with an explicit setting against one without one.
7. Change the project default only after recording the original value, then inspect the unassigned clip again.
8. If the two clips respond differently, check which one has a specific override.

Use a reversible test. Save a project version or duplicate the project before changing the overall color-management setup. Change one setting at a time and compare the same frame, not different frames with different lighting. If you change project input, timeline space, output space, and a clip override all at once, you cannot tell which decision caused the visual change.

An input change may affect the entire clip wherever that source appears. It is not necessarily limited to the single visible edit instance on the timeline. Blackmagic’s color-management workflow is organized around source media and project transforms; its Colorist Guide describes assigning an input color space to clips and then choosing timeline and output spaces for the project. [The guide is available from Blackmagic Design](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf).

There is another distinction worth keeping straight: the source-level input assignment and the clip’s grade are not the same thing. The input interpretation belongs to color management; exposure, white balance, contrast, and creative look are grading decisions. If a shot looks wrong, first determine whether the source is being interpreted correctly. Then balance and match it. Do not use a creative correction to conceal an input mismatch that will affect later work.

**Changing the project input default does not necessarily change clips that already have explicit input assignments.**

For Resolve 21.1, refer to the [current Blackmagic manual listing](https://www.blackmagicdesign.com/welcome/en/W-DRE-03) if menu placement or labels differ from an earlier release. Blackmagic’s support page lists DaVinci Resolve 21.1 and its manual as current as of the September 2026 release. The core decision remains easy to test: compare a clip with a verified override to one that inherits the project default.

## How do I assign an Input Color Space to one clip?

In a DaVinci YRGB Color Managed project, select the source clip in the Media Pool and use its Input Color Space context-menu option to choose the source encoding that matches the camera footage. The exact menu can vary with project mode, selected media type, and release, so verify the selection on a representative clip before applying it broadly.

Here is a cautious one-clip workflow:

1. Identify the clip’s recording format from reliable information. Use camera notes, production metadata, or documentation for the exact camera and recording mode.
2. Open Project Settings and confirm that the project is using DaVinci YRGB Color Managed if you expect Resolve Color Management to interpret the input assignment.
3. Select the source clip in the Media Pool.
4. Open the contextual menu and look for Input Color Space. In a dual-setting configuration, the menu may expose gamut and gamma separately.
5. Choose the exact matching camera gamut and gamma, or the matching combined option if the project uses a single-setting configuration.
6. Return to a representative frame and compare the result with the prior state.
7. Check scopes as well as the viewer, and confirm that the output setting still matches your intended delivery.

The selection should be based on capture format, not just a camera model name. A camera may record in multiple codecs, gamuts, transfer functions, or picture profiles. The same camera can produce materially different source characteristics depending on the selected mode. For example, the phrase “Sony footage” does not specify whether a clip is S-Log3, a standard video profile, or a transcoded intermediate. Likewise, “Blackmagic footage” does not tell you which camera generation, film profile, or color science produced a particular file.

If you are not sure, inspect the clip’s metadata and verify the camera’s actual recording settings. Resolve may expose useful metadata, but metadata does not always contain the full picture-profile information required to identify every source accurately. Blackmagic’s Colorist Guide recommends obtaining definitive information from the filmmakers when the origin or format is unknown, rather than pretending the input profile is obvious. [See the Blackmagic Colorist Guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf).

After applying a setting, check a few types of content, not only a face or a gray wall. Look at skin, saturated colors, highlight roll-off, shadows, and any known neutral object. The purpose is not to make every shot look finished at once. It is to confirm that the chosen interpretation is plausible and that the project’s managed conversion is behaving as expected.

Do not mistake the right-looking viewer image for proof that the assignment is technically right. A wrong input transform may be partially hidden by a LUT, a node, or a display transformation. That can create a pleasing frame while leaving the pipeline internally inconsistent. Confirm the source metadata and assignment first, then grade.

If the Input Color Space menu is absent, check the diagnostic section below before concluding that Resolve cannot assign a clip input. The project may be in a different color-science mode, or you may have selected a compound, nested, or otherwise derived item instead of the original source.

## How do I assign the same Input Color Space to multiple clips?

Select only clips that share the same verified source encoding, then assign the matching Input Color Space to the selection in one operation if Resolve offers that contextual action. Grouping by camera is efficient, but only when the clips in that group also share the same recording mode and relevant color characteristics.

The safe batch workflow is based on verified categories, not convenience:

1. Create a list of the cameras and recording modes used for the project.
2. Sort, filter, or bin the source clips so each selection contains one known camera-and-format combination.
3. Select a small sample from the group and confirm the expected input assignment.
4. Apply the assignment to the full matching selection.
5. Check a second sample from the beginning, middle, and end of the group.
6. Repeat with a separate selection for every materially different source format.
7. Keep a short record of the assignment choices in project notes or production documentation.

A group name like “Camera A” may not be specific enough. The camera could have recorded standard video for one scene and log for another, or a second operator may have used different capture settings. A more useful label includes the device and recording mode, such as “Camera A, S-Log3, S-Gamut3.Cine” when that is what the footage actually uses. The label is only a reminder; the source information still needs verification.

A useful workflow for an interview with two cameras might look like this:

| Bin or selection | Example source condition | Input assignment approach |
| --- | --- | --- |
| A-cam log | Camera A recorded in a documented log mode | Assign that mode to the matching camera clips |
| B-cam log | Camera B recorded in a different log mode | Assign the B-camera mode separately |
| Phone pickups | Phone clips are known to be standard video or HDR | Verify each recording mode; do not assume every phone clip matches |
| Screen capture | Captures are already display-referred or encoded by a capture tool | Confirm format and avoid treating it as camera log |
| Transcoded proxies or intermediates | Files may preserve or alter source characteristics | Check the media pipeline and whether transforms were baked in |

The table is a worked example, not a report about observed footage. The camera labels and formats are illustrative. The correct assignment depends on the actual recording and any processing applied after capture.

Batch assignment can save time, but a wrong batch can multiply the mistake. If two different modes are mixed in a selection, an assignment that is correct for one subset is wrong for the other. Do not bulk-select by filename prefix alone unless that naming convention reliably separates the actual source formats. Verify the selection before using a batch operation.

You can also make a project template with a useful default, but a template should not silently replace source verification. Templates are most valuable when they capture stable choices such as the intended output, timeline setup, and common source profile for a recurring production. If a new production adds a camera or a recording mode, update the input assignments rather than assuming the old template covers it.

## What happens when a clip-level input setting overrides the project default?

A clip with an explicit input assignment is interpreted using that clip-specific source description, while unassigned clips continue to use the project default. The override changes the clip’s input interpretation, not the project’s timeline or output setting.

Here is a worked example. Suppose the project default is set to a common Rec.709 source. A log clip from a camera with a documented gamut and gamma is assigned that camera format at clip level. Resolve now has two input descriptions in the same project: the default for unassigned Rec.709 clips, and the explicit camera description for the assigned log clip. Both can be transformed into the same timeline working space, then toward the same output space.

The practical result is that mixed sources can share one timeline without pretending they were recorded in one format. It does not make the source footage identical, nor does it automatically match exposure, white balance, lens response, lighting, or artistic intent. Color management normalizes technical differences in encoding; the colorist still balances and matches images.

A clip override is not an override of every project decision. It does not mean that clip now has its own project output color space or independent timeline working space. It supplies input information for that source. The managed pipeline still routes the interpreted image through the project’s timeline and output choices, unless you have built a different explicit workflow with nodes or other processing.

Consider a three-shot scene: one angle is log, one is Rec.709, and one is a phone HDR clip. You may have three different source interpretations, but you still need a coherent output plan. Resolve Color Management can place those differently encoded sources into a common working environment. You then assess their brightness, contrast, color balance, and matching. If the phone footage is already tone-mapped or transformed, selecting a camera-log input could make it look worse, not better.

This is why a clip-level assignment can appear to “take over” after a project setting change. It is not necessarily taking control of the whole project. It is replacing the default for that one source. The distinction is easier to see if you compare an assigned clip and an unassigned clip side by side, then change only the project default temporarily.

A clip override can also have consequences for multiple timeline uses of the same source media. If the same source is used more than once, changing source-level interpretation may affect each use of that media. Review the complete source wherever it appears, particularly if one media file contains shots with different camera settings or if a long take changes recording mode. If one media file includes genuinely different image encodings, a single source-level assignment may not describe every frame correctly. Such cases may need a different conform or node strategy rather than a careless global setting.

**A clip override changes that source’s input interpretation, not the project’s timeline or output color space.**

## Why is Input Color Space missing when I right-click a clip?

The Input Color Space option may be unavailable because the project is not using a managed color-science mode, the selected item is not a supported source clip, or the current release presents that operation differently. Confirm the project mode and selected media before searching for a hidden menu.

Use this checklist:

| What you see | What to check next |
| --- | --- |
| No Input Color Space option anywhere | Confirm Color Science is set to DaVinci YRGB Color Managed, not plain DaVinci YRGB |
| The option exists for some clips but not this one | Check whether the selected item is a compound clip, nested timeline, or another derived object |
| The Media Pool menu differs from the Color page menu | Select the original source in the Media Pool, then compare the clip thumbnail context menu on the Color page |
| A preset or automatic mode exposes different controls | Review the active project preset and its behavior in the current Resolve manual |
| You are selecting a timeline segment | Try selecting the source media item rather than the edit instance |
| The assignment menu is present but the expected camera profile is absent | Confirm the version, gamut/gamma naming, and whether the project is using RCM or ACES |

The Blackmagic forum has documented examples of users finding the option unavailable on compound clips while it remained available for ordinary source clips. That is a community report, not a universal rule for every Resolve 21.1 configuration, so treat it as a troubleshooting clue rather than a guarantee. [See the Blackmagic forum discussion about the missing Input Color Space menu](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=222178).

If the project uses plain DaVinci YRGB, then it is not using Resolve Color Management’s project input default in the same way. You may be using manual transforms in nodes, a LUT-based workflow, or another method. In that case, changing the project’s color science mode just to make the menu appear can change the entire image pipeline. Save a copy first and understand the transform consequences before switching modes.

If the missing item is a compound clip or nested timeline, consider whether you need to set the input on the underlying source clips instead. A compound object may represent a processed result rather than a direct camera original. Applying an input profile at the wrong level can double-transform or misinterpret content. Inspect the structure: open the compound or nested timeline, identify its source footage, and decide where the transform belongs.

If you are using an automatic color-management preset, read the active mode’s description in the current manual and inspect what Resolve has inferred. An automatic workflow can make some controls less visible or reduce the need to assign every clip manually. That does not mean the source identity is irrelevant. When the automatic interpretation seems wrong, verify the file’s actual recording characteristics and determine whether the mode allows a manual override for that source.

On a current installation, use the [DaVinci Resolve 21.1 manual listing](https://www.blackmagicdesign.com/welcome/en/W-DRE-03) to confirm release-specific labels and procedures. Version differences can change navigation and available options; do not rely on a menu path captured from an older tutorial if your interface differs.

## How can I tell whether the Input Color Space assignment is correct?

A correct input assignment matches the source’s recorded gamut and gamma or other applicable encoding, and it produces a technically plausible starting point inside the chosen managed pipeline. A pleasing image alone is not enough evidence, because grading, LUTs, display transforms, or incorrect monitoring can disguise an input mistake.

Check the assignment against the recording chain. Find the camera model, firmware or recording format when relevant, picture profile, gamut, transfer function, and any transcoding or LUT processing performed before the file reached Resolve. The source’s file extension is not a complete color-space description. Neither is the manufacturer name.

Then make a controlled visual check:

- Compare the same frame before and after the input assignment.
- Examine both the viewer and the scopes.
- Look for unexpectedly clipped highlights or crushed shadows.
- Check skin and neutral objects, but do not treat either as a sole test.
- Inspect saturated colors that may reveal a gamut mismatch.
- Confirm that no technical transform has already been baked into the footage.
- Verify that the output color space still describes the intended delivery.

The goal is not to force every camera image into a generic “normal” look. Log footage can look flat before the appropriate viewing transform, and a managed transform may produce a more display-ready image. But if a clip suddenly becomes excessively contrasty, strangely saturated, or severely clipped after the assignment, pause. The selection may be wrong, a transform may be duplicated, or a separate output/monitoring issue may be involved.

A useful diagnostic sequence is to disable or bypass creative nodes temporarily, while preserving the project’s color-management setup. If the problem disappears only when you bypass a look node, the source assignment may not be the cause. If the problem follows one source across timelines, inspect that source’s input metadata and override. If all clips look wrong in a similar way, check project-level timeline, output, and monitor settings as well as the input default.

Resolve’s official guidance distinguishes the input, timeline, and output stages. Therefore, a wrong-looking image does not automatically point to the input stage. The timeline working space, output transform, tone mapping, display configuration, and additional node processing can all influence what you see. [Blackmagic’s overview of Resolve color management](https://www.blackmagicdesign.com/products/davinciresolve/color) is a useful map of those stages.

Take care with RAW media. RAW decoding controls can include camera-specific parameters such as white balance and exposure-related settings. A RAW workflow is not always the same as assigning an ordinary compressed clip’s input gamut and gamma. Check the camera RAW panel and the manual for that file type rather than applying an unrelated transform because a tutorial uses it for log video.

For camera-specific projects, keep evidence of the choice. A short note such as “A-cam: recorded S-Log3/S-Gamut3.Cine, assigned matching input; B-cam: Rec.709” is more useful than “fixed color.” A later editor can understand what the pipeline expects. This matters when the project travels to another workstation or another person needs to conform the media.

If the visual result remains uncertain, create a test timeline with a small selection of original clips and compare a few plausible interpretations under the same timeline and output settings. Do not declare one correct just because it is brighter. The assignment should agree with known capture information, and the result should make technical sense without hidden corrective operations.

## Should I use a project default for mixed-camera footage?

For mixed-camera footage, use the project default for the common source and make explicit clip-level assignments for verified exceptions. If several source types are equally common or the media is a complicated mixture, prioritize clear source organization over trying to find one universal default.

A mixed-camera project can be simple if it is organized well. Make bins or smart filters for sources, name the camera and recording mode, and separate proxies or transcoded copies when their processing differs. Assign by verified source group, then check representative clips from each group. Leave the project default set to a sensible fallback that describes the largest or most common unassigned group.

A worked example:

- Camera A records log footage in a documented camera gamut and gamma.
- Camera B records a different log format.
- A phone records a mix of standard video and HDR clips.
- A screen-capture application produces display-referred media.
- An archive folder includes previously graded Rec.709 material.

This is an example of possible project contents, not a claim about what every production contains. The key lesson is that the source label alone is insufficient. A phone may record more than one format. Previously graded footage may already contain a display transform. A proxy may or may not preserve the source’s color values and metadata. Establish the status of each source before assigning it.

Avoid assigning one input profile to a whole bin if the bin is grouped by subject rather than by recording format. For instance, a bin named “interview” might contain both cameras and a phone insert. It is useful for editorial organization but poor for bulk color assignment unless all clips share the same encoding.

Color management can make different sources more manageable, but it does not promise a matched camera look. Once sources are correctly interpreted, shots can still differ because of exposure, white balance, lens transmission, sensor response, lighting, camera settings, and time of day. The next step is shot balancing and matching. Blackmagic’s Colorist Guide explicitly cautions that color management does not remove the need to balance and match footage. [Read the guide from Blackmagic Design](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf).

A useful operational division is:

- **Input stage:** describe what the source media is.
- **Timeline stage:** choose the working environment for grading.
- **Output stage:** define the delivery or monitoring target.
- **Grade stage:** balance and shape each shot after the managed transforms are understood.

When a project has a colorist, editor, or client handoff, document the project-level default and any unusual clip-level assignments. Include known recording modes and identify any footage with baked-in looks or transforms. That record prevents another operator from “correcting” an intentional override or applying a second transform.

If sources are too uncertain to classify reliably, do not hide the uncertainty behind a broad default. Put the questionable media in a separate bin, request the original camera or transcode notes, and test a representative shot. A cautious unknown is safer than an unexamined assumption that quietly affects every unassigned clip.

## Is project Input Color Space the same as a Color Space Transform node?

No. A project Input Color Space is part of Resolve Color Management’s source interpretation, while a Color Space Transform node is an explicit processing operation that you place in a node graph. They can both perform color-space conversions, but they belong to different workflow structures.

Resolve Color Management manages conversions at the project level. You define or select source interpretations, a timeline working space, and an output space. Resolve applies the transforms as part of the color-managed pipeline. A Color Space Transform effect gives you a visible node with explicit input and output parameters inside the grade. That can make the transform easy to inspect in the node graph, but it also means the operator must manage the placement and consistency of those nodes.

Cullen Kelly describes node-based color management as a way to build the pipeline explicitly in groups and nodes. In his words, “Essentially, color management takes what the camera sees and transforms it into what your display can show.” [Kelly’s article on node-based color management](https://blog.frame.io/2024/01/08/color-management-nodes-davinci-resolve/) explains his approach and its relationship to source cameras and display output. This is a named colorist’s description of the concept, not a statement that every workflow should use nodes.

Use project-level management when you want Resolve to apply the pipeline centrally and keep source interpretation, timeline space, and output target in project settings. Use explicit node transforms when you need a node-visible pipeline, a specific custom architecture, or a workflow that deliberately avoids project-level color management. The latter requires discipline: one transform at the wrong location or a duplicate transform can change the image substantially.

Do not combine methods casually. A project-managed input transform followed by a node that performs the same camera-to-working-space conversion may double-transform the source. Conversely, a node pipeline in plain DaVinci YRGB may be intentional, even though project Input Color Space is not the control doing the work. Identify where the conversion occurs before adding another one.

The practical question is not “Which method is always better?” It is “Which method does this project use, and where are its input and output transforms applied?” A project can be color-managed at the project level, in nodes, with ACES, or through a carefully designed combination. Each method needs a coherent order and an explicit understanding of what the source and output spaces are.

For a new editor, a managed project with deliberate source assignments often makes the stages easier to reason about. For a colorist with a well-documented node template, a node-based approach may provide the visibility or control they want. Compare the workflow goals, not just the label in a menu. If you are deciding between project RCM and manual transforms, see [Resolve Color Management vs. ACES](https://tryuncle.com/learn/davinci-resolve/resolve-color-management-vs-aces-which-should-i-use) and the separate explanation of [automatic color management vs. manual workflows](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-automatic-color-management-vs-manual).

**A project input setting and a Color Space Transform node can serve related purposes, but they are not the same control.**

## What should I do if a LUT or CST is already on the clip?

First determine whether the LUT or Color Space Transform is a technical conversion, a creative look, or both; then check whether Resolve Color Management is already making the same conversion. Avoid stacking an input transform and a node transform without knowing the intended sequence.

A LUT can be used for different purposes. A camera manufacturer LUT may convert log footage toward a display-referred image, while a creative LUT may add a look. Some LUTs combine normalization and a creative rendering. The file’s name alone may not tell you which. Check its documentation and the project’s node order.

A Color Space Transform node typically exposes input and output color-space parameters and may also offer additional processing options. It can be used for a camera-to-working conversion, a working-to-output conversion, or another specified transform. The effect depends on how it is configured. Do not assume every CST node is an input transform just because it appears near the beginning of a node tree.

Use this review sequence:

1. Identify the project Color Science mode.
2. Read the source clip’s input assignment, if any.
3. Inspect the node graph for CSTs and LUTs.
4. Check what each node’s input and output settings are intended to do.
5. Determine whether the transform is technical normalization, a display transform, or a creative look.
6. Bypass one node at a time to observe its role.
7. Keep only the transforms required by the chosen pipeline.

If the project is color-managed and the clip has an explicit camera input assignment, a first-node CST from that same camera encoding into the same timeline space may duplicate work. If the project is plain DaVinci YRGB and uses a CST at the head of the node tree, that transform may be the mechanism that normalizes the source. The same-looking node can be redundant in one project and essential in another.

Do not remove a LUT because someone says “color management already handles it.” A LUT may be a creative look, a camera-specific transform, or a required display conversion. Determine its job first. Likewise, do not add a CST simply because a clip looks flat. The flat look may be the intended log source before its correct input transform, or the project may already be transforming it.

When a clip looks desaturated after applying a CST, that can come from wrong input settings, wrong output settings, double transformations, mismatched data, or an unexpected source format. Work through the diagnosis in [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) rather than changing unrelated project settings at random.

Keep the existing pipeline in mind when receiving a project from someone else. A node tree may encode deliberate technical decisions. Before modifying it, ask whether the project is managed, whether transforms are baked into media, and which output the grade targets. If that information is missing, duplicate the timeline or project and test on one source clip before changing the whole sequence.

## How do automatic color management and clip overrides work together?

Automatic color management can make source interpretation easier, but it does not remove the need to understand which clips are being interpreted automatically and whether any clip-level assignment is available or necessary. The exact controls depend on the selected color-management mode and Resolve version.

A manual project default is not the only possible way to manage inputs. Resolve’s color-management modes and presets can automate parts of the pipeline. A preset may choose or infer settings for a typical workflow, while a more customized setup exposes more decisions. The important question is whether the active mode is using metadata or a preset assumption to interpret the source, and how you can correct that interpretation when it does not match the footage.

Do not treat “automatic” as synonymous with “always correct.” Automatic behavior depends on the information available in the media and the rules in the selected mode. If the file metadata is incomplete, ambiguous, or altered during transcoding, an automated choice may need review. Conversely, do not manually override every clip merely to feel certain. If the automatic mode correctly handles the footage and the result matches the known source pipeline, unnecessary overrides can create inconsistent behavior.

Use these principles:

- Start with the project’s chosen color-science mode and preset.
- Check whether the mode expects manual clip assignments, uses metadata, or applies a defined project-wide transform.
- Verify any clip that appears wrong against camera records.
- Change one source interpretation at a time.
- Record which clips are exceptions and why.
- Confirm that your timeline and output settings remain intentional.

The [TryUncle guide to automatic color management vs. manual settings](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-automatic-color-management-vs-manual) discusses the broader decision between those approaches. For the current control names and workflow details in Resolve 21.1, check the [Blackmagic manual listing](https://www.blackmagicdesign.com/welcome/en/W-DRE-03).

Automatic management and clip overrides are not necessarily opposing ideas. A project may use automation for routine footage and specific corrections for exceptional sources. Think of the system as a pipeline with defaults and exceptions. The default handles the sources that fit the rule. A verified exception should be documented, not left as a mystery for the next editor.

Be especially careful with footage that has passed through multiple applications. A proxy may preserve the camera source values, but a transcoding process might have applied a LUT or converted to another space. A social-media download may already be compressed and display-referred. A screen recording may have a different color profile from camera media. The file may retain a camera name in metadata even though its pixel values have been transformed. In those cases, the processing history matters as much as the original camera.

If your automatic setup makes the image look reasonable but you cannot explain the path from source to output, pause before building a grade on top of it. You do not need to memorize every color-science detail, but you should be able to identify the project mode, the source assumption, the working space, the target output, and any manual transforms. That minimum map prevents the common mistake of applying a second conversion to “fix” an image already converted.

## How do version differences affect Input Color Space settings?

The current version context for this guide is DaVinci Resolve 21.1, listed by Blackmagic Design as released on September 8, 2026. Menu wording and navigation can change between releases, so confirm the exact control in the manual for your installed version instead of relying on a screenshot or instruction made for an earlier version. [Blackmagic’s support center lists Resolve 21.1 and its manual](https://www.blackmagicdesign.com/support).

The underlying distinction in this guide is the relationship between an unassigned clip and the project default versus a clip with its own source interpretation. When Resolve updates the interface or adds formats, the visible labels and available choices can change. A new camera profile may appear in a later release; an automatic mode may expose different options; a contextual menu may behave differently for different media types. Those details are version-sensitive.

Before following an older tutorial, compare its stated Resolve version with yours. Look for the actual Color Science mode and current menu labels. If the video shows a combined gamut-and-gamma menu but your project displays separate controls, check whether the project uses a dual-setting configuration. If the tutorial opens Project Settings but your setting is an automatic preset, the mismatch may be the selected mode rather than a missing feature.

Resolve 21.1 adds many new tools and controls, but the Blackmagic support page’s release notes do not claim that the fundamental project-default versus clip-override distinction has been replaced. Do not infer a color-management behavior change merely because another feature changed in the same release. For a technical difference that affects your footage, consult the 21.1 manual and verify with a controlled test project.

A simple compatibility note can make project handoffs clearer:

| Record this | Example of useful information |
| --- | --- |
| Resolve version | DaVinci Resolve 21.1 |
| Color Science mode | DaVinci YRGB Color Managed |
| Project default input | The verified common source format |
| Clip exceptions | Camera, recording mode, and assigned input |
| Timeline space | The chosen grading working space |
| Output space | The target delivery or monitoring space |
| Additional transforms | LUTs, CST nodes, or baked-in conversions |

These are documentation fields, not recommended universal values. The example “DaVinci Resolve 21.1” identifies the version context; the remaining values must describe your project. A handoff note that only says “managed” does not tell another editor whether clip overrides exist or what the final output target is.

If a control appears to have moved, search the current manual for its label and consult Blackmagic’s official Resolve training resources. The [official training page](https://www.blackmagicdesign.com/uk/products/davinciresolve/training) includes color-related materials, while the current manual should be the authority for the controls in your release.

TryUncle is the on-screen assistant for DaVinci Resolve on Mac and Windows, and Uncle can point to the relevant control while you work in the project. [TryUncle](https://tryuncle.com/) is an option if you want on-screen guidance for checking the project mode or finding the input assignment control; you still choose the settings and make the grade.

## What is the safest checklist before grading?

Before grading, verify the project mode, identify the source formats, confirm the default and overrides, choose the intended timeline and output spaces, and check that no duplicate conversion is hiding in the node graph. This turns an ambiguous color problem into a set of decisions you can inspect.

Use this pre-grade checklist:

- **Project mode:** Confirm whether the project uses DaVinci YRGB Color Managed, plain DaVinci YRGB, or ACES.
- **Version:** Note the installed DaVinci Resolve version, especially if following instructions from an older tutorial.
- **Project default:** Record the default input interpretation and confirm which sources are meant to inherit it.
- **Source list:** Identify each camera, picture profile, and recording mode.
- **Overrides:** Check which clips have their own input settings and why.
- **Timeline:** Confirm the working color space expected for grading.
- **Output:** Confirm the delivery or monitoring target before judging the viewer image.
- **Node graph:** Inspect CSTs, LUTs, and other technical transforms for duplicates.
- **RAW controls:** If applicable, confirm camera RAW decoding separately from ordinary clip assignments.
- **Validation:** Compare representative frames and scopes from each source group.
- **Documentation:** Record exceptions for editors and colorists who inherit the project.

A useful small test project can answer difficult questions more safely than changing a finished timeline. Import a few original sources, use the intended project settings, and compare the same frames under a known output. Keep the test simple: one representative clip per recording format, no unnecessary looks, and only one variable changed at a time.

The test should answer practical questions. Does the project default affect the unassigned clip as expected? Does the clip override affect only the source you intended? Does the chosen timeline and output combination produce the right viewing target? Does a CST or LUT duplicate a conversion that is already happening? If the answer to one of these is unclear, resolve it before grading a full sequence.

Do not chase a specific “cinematic” look while diagnosing an input mismatch. First establish whether the footage is interpreted correctly. Then correct exposure and balance. Then match related shots. Finally, build the creative look and evaluate the output. This order keeps technical normalization separate from artistic decisions.

If you need a deeper comparison of color-management approaches, the related guide on [Resolve Color Management vs. ACES](https://tryuncle.com/learn/davinci-resolve/resolve-color-management-vs-aces-which-should-i-use) explains the broader workflow choice. For this query, the decisive rule is simpler: set a project default for the unassigned footage it accurately describes, and set clip-level inputs only when verified source differences require them. Use that rule, check one representative frame from every source type, and save the project before moving on to the grade.

## FAQ

### Does a clip input color space override the project input color space in DaVinci Resolve?

Yes, in a DaVinci YRGB Color Managed project, an explicit input color space assigned to a clip takes precedence over the project Input Color Space default. The project value remains the default for clips without their own assignment.

### Why is Input Color Space missing when I right-click a clip?

First check that the project uses DaVinci YRGB Color Managed rather than plain DaVinci YRGB, and that the selected item is a supported source clip rather than a compound or derived item. The available menu options can depend on the selected media and project color-management mode.

### Should I set Input Color Space in Project Settings or on each clip?

Use Project Settings for the common source format that should be the default, then assign clip-level exceptions for sources with different color characteristics. If you have many cameras or formats, organize and assign the matching clips together, then verify representative shots.

### Does changing a clip's Input Color Space change the Timeline or Output Color Space?

No. Input describes how Resolve interprets source media. Timeline describes the working space used for grading, and Output describes the display or delivery space. Changing one does not mean the other two have changed.

## Sources

- [DaVinci Resolve 21.1 Reference Manual](https://www.blackmagicdesign.com/welcome/en/W-DRE-03)
- [DaVinci Resolve 20 Colorist Guide](https://documents.blackmagicdesign.com/UserManuals/DaVinci-Resolve-20-Colorist-Guide.pdf)
- [DaVinci Resolve Color](https://www.blackmagicdesign.com/products/davinciresolve/color)
- [DaVinci Resolve Training](https://www.blackmagicdesign.com/uk/products/davinciresolve/training)
- [How to Color Manage Using Nodes in DaVinci Resolve, by Cullen Kelly](https://blog.frame.io/2024/01/08/color-management-nodes-davinci-resolve/)
- [Resolve Color Management vs. ACES: Which Should You Choose?, by Cullen Kelly](https://blog.frame.io/2024/02/12/davinci-resolve-color-management-vs-aces-which-should-you-choose/)