01 / 04 COLOR · A CLEAR START
Workspace.Find your way around Color.
Do not memorize button coordinates. Understand where you choose a shot, judge the image and build a grade — and the interface becomes a working tool.
Panel map · real screenshots · first pass
Judge the selected image and compare versions. Read it together with scopes; a viewer alone does not validate the entire output pipeline.
Schematic layout, not a Resolve screenshot. Panel positions depend on your workspace. Select an area to learn its role.
UNDERSTAND THE MECHANISM
The interface is a selection system, not a collection of windows.
Before moving a wheel, ask three questions: which clip am I changing, in which processing context, and which node is selected? This is more useful than memorising every button’s position.
Clip → graph context → node → palette
Clips selects the shot; the Node Editor selects a processing stage. For a basic exercise, start in the Clip context with one explicitly selected node. Name it for its job, such as Balance. When switching between Primaries and Curves, you then know which stage owns the changes. Opening another palette does not itself create a node.
If the correction should affect only this shot, first check that a shared group or timeline context is not active. Do not test that with a strong change in a production project: use a copy, a small reversible adjustment and a comparison with a neighbouring clip. The node guide returns to processing contexts.
RememberBefore each new task, check both the selected clip and the selected node.
Comparing and applying a grade are different actions
A saved Still provides a stable comparison point as your eyes adapt to a correction. Image Wipe helps compare portions of images; Split Screen shows multiple versions together. First decide what you are comparing: the same frame before the adjustment, or another shot in the scene.
Applying a grade changes settings; it is not a viewing mode. Do not apply a Still merely to inspect a difference. Even one camera does not guarantee matching exposure, illumination or face position. Compare specific features—shadow density, face brightness and a neutral object’s hue—not just an overall impression.
RememberCompare first; decide separately whether to copy settings.
Viewer magnification and image geometry
Magnify the Viewer to inspect a mask edge, noise or fine detail. Then return to the complete frame: an improvement visible only at extreme magnification may contribute little to the scene. Do not use an image-geometry correction merely to inspect something more closely.
If the picture becomes grey, monochrome or shows only part of an object after isolation work, first check Highlight and matte display. You may be looking at a diagnostic view rather than damaged colour. Return to the normal image before judging or changing the grade.
RememberCheck the viewing mode before trying to correct what it shows.
One frame, the whole shot, the adjacent cut
A paused frame is useful for making a decision, not for final acceptance. Motion can reveal a window edge, lighting change or lost isolation. Check the beginning, middle and end, then play the shot without stopping. If something fails, note the location and return to the node responsible for that area.
Then watch the cut to the neighbouring shot. The aim is not identical traces or identical brightness everywhere: a new angle naturally changes the light distribution. Check whether the cut looks like an accidental lighting or balance jump when no such change is intended.
RememberA completed check includes playback, not just a successful screenshot.
UNDERSTAND THE TOOL
Each panel has its own role.
Gallery and Clips
Gallery and Clips are separate areas: Gallery holds stills and grades for comparison; the Clips filmstrip selects timeline shots. Copying a grade still requires adapting it to another shot’s lighting and exposure.
Viewer
The Viewer is where you look at the shot and judge the grade itself. It is the main place for checking skin tone, contrast, mood and the overall appearance of the image.
Node Editor
This is where the grading chain is built. Nodes let you separate corrections by purpose — for example, base balance, skin, local masks and the creative look.
Primaries Color Wheels
The main wheels for primary grading. This is the fastest place to balance brightness, remove an unwanted color cast and prepare the shot for deeper work.
Tracker and Keyframes
When an object moves, Tracker helps a mask follow it, while Keyframes let grading parameters change over time. This is essential for local corrections in moving shots.
Scopes
Scopes measure signal levels and color components. Together with the Viewer and properly configured monitoring, they help validate a grade; one trace cannot certify every delivery requirement.
UNDERSTAND THE TOOL
A first pass without the clutter.
- 01
Learn where everything is
First find the Viewer, Color Wheels, nodes, Tracker and scopes. Once you understand what these areas are for, the Color page stops feeling complicated.
- 02
Start with Color Wheels
Use Color Wheels to balance brightness and color, then Contrast and Saturation to bring the image to a clean starting point before deeper work.
- 03
Split the grade by task
Do not try to do everything on one node. Separate nodes for the base, skin, masks and the look keep the project readable and make mistakes easier to fix.
- 04
Check the result with scopes
After the adjustment, check both the picture and the scopes. If the image looks right and the signal levels are healthy, you can move on.
GUIDED PRACTICE
Practice: one shot, one change, a result you can verify.
Connect the panels into one sequence: select a clip, save a reference, make an adjustment and check the result. The goal is not an attractive grade at any cost, but learning to keep track of the project state and compare deliberately.
Use a project copy and two neighbouring clips from one scene. Choose a shot with readable shadows and highlights and no complicated movement. Leave colour-management settings unchanged during this exercise.
- 01
Record the starting point
DO THISSelect the first shot in Clips and park on a representative frame. Use Grab Still from the Viewer context menu. Give the Still a useful name, such as Before balance.
WHAT TO CHECKGallery now contains a reference for this frame. You can identify exactly which starting state will be used for comparison.
- 02
Check where the change will go
DO THISSelect the Clip context and the intended node, read its label and open Primaries. If another node exists, switch to it and back before changing anything.
WHAT TO CHECKYou can see that the palette follows the selected node rather than holding one application-wide correction.
- 03
Make one small change
DO THISChange only the overall level or one contrast control. Immediately inspect the Viewer and Waveform. Do not also add saturation, a mask and a LUT; that would hide which action produced the change.
WHAT TO CHECKYou can name the changed feature, for example a dark object becoming more readable while a bright reflection retains detail.
- 04
Compare without erasing settings
DO THISDisable only the correction node, then enable it again. Next compare against the saved Still using a comparison view. Do not use Reset as a before/after button.
WHAT TO CHECKThe settings remain intact and the contribution can be judged separately from the rest of the processing.
- 05
Return to the scene
DO THISPlay the shot and the cut to its neighbour. Return to the original clip, the same node and a normal Viewer display. Save once the state is clear.
WHAT TO CHECKYou have retained the selected clip, reference frame and processing stage. You can continue without guessing where the change belongs.
Completion criterion
The exercise is complete when you can show the reference, toggle your adjustment without resetting it, name the selected node and check the neighbouring shot. An attractive Still alone does not demonstrate control of the interface.
Full workspace reference for this exercise
REASON THROUGH A CASE
Three situations that can make the interface misleading.
Decide what you would check first, then open the explanation. The point is the order of investigation, not guessing the right term.
A setting changed, but the frame looks unchanged
You move a control but do not see the expected change. Should you immediately increase it further?
Check your reasoning
First check the clip, selected node and whether that node is enabled. Then check whether a mask limits the correction or later processing hides it. A larger value does not fix a wrong target; it can leave an unexpected correction elsewhere in the graph.
Applying a Still did not match the next shot
The settings transferred, but the face is darker in the second shot. Does that mean Gallery is malfunctioning?
Check your reasoning
No: the same settings were applied to different source material. Compare lighting and exposure first, then make a shot-specific adjustment. Treat the Still as a reference, not a promise that one formula produces the same result everywhere.
A tool seems to disappear after rearranging panels
A tutorial shows a panel on the right, but your layout has something else there. Should you change the project?
Check your reasoning
Do not change project settings because windows are arranged differently. Find the area by name and purpose, check visibility and the selected palette. Window size and workspace layout affect placement, not what the tool means.
Workspace map
Not just where panels live — how the Color page works as a system
The Color interface is easier to remember as a workflow rather than as button coordinates: select a clip → judge Viewer and scopes → build the correction in the Node Editor → open the needed palette → verify the result in scene context. The reference below stays useful even when panels are rearranged or the workspace changes.
the object the grade belongs to
processing order and structure
tools applied in the selected node
signal measurement, not UI decoration
What each interface area is responsible for
| Area | What it stores / shows | When to use it | Common mistake |
|---|---|---|---|
| Gallery / Stills | references, saved grades and still metadata | matching, comparison, transferring a base grade | treating a Still as a plain JPEG screenshot |
| Viewer | the current visual result | constantly — together with scopes | judging colour only by the Viewer without scopes or display control |
| Clips / Timeline | shot context and the selected clip | during matching and continuity checks | grading a shot in isolation from the scene |
| Node Editor | processing graph, RGB and key connections | before each local or technical task | putting everything in one node or building a graph without logic |
| Palettes | Primaries, Curves, Qualifier, Window, Tracker, Key, Sizing and more | once the task is clearly defined | choosing a tool by habit rather than by problem type |
| Scopes | luminance, RGB balance, chroma and signal distribution | before, during and after the grade | treating scopes as a final check instead of continuous measurement |
A deliberate working method
- 01
1. Start with context
Select the clip and inspect neighbouring shots. Before the first adjustment, separate shot-specific problems from characteristics of the whole scene.
- 02
2. Then measure
Open the relevant scope and establish what is happening with luminance, channels and saturation. This gives you a technical baseline.
- 03
3. One task — a readable node
Build the Node Editor around tasks: technical transform, balance, secondaries, look and output checks. The node count matters less than a readable order.
- 04
4. Verify in scene context
Return to Clips, Gallery and scopes. A good isolated shot does not automatically make a good sequence — continuity matters more than local impact.
WHEN SOMETHING LOOKS WRONG
Trace the cause.
01I do not know where to find the needed tool+
Possible cause. the task is framed as a button name rather than a correction type
What to check. first classify the task: global balance, curve, isolation, tracking, key, geometry or measurement
02The interface feels overloaded+
Possible cause. too many panels are open without relevance to the current task
What to check. keep the Viewer, Node Editor, one working palette and the needed scope
03After changing clips I do not understand why the grade is different+
Possible cause. clip-level, group/timeline context or grade version is being confused
What to check. check the selected clip, node-graph level and active version
FROM READING TO DOING
One clip.
Three checks.
Use a copy of your project or a test clip. These small checks turn the article into a repeatable workflow.
Back to the Color index ↗Self-check in Resolve; the site does not evaluate your work. Progress is not saved after reloading.
COMMON QUESTIONS
The details that matter.
What is on the Color in DaVinci Resolve?
The Color page contains the main DaVinci Resolve grading tools: Color Wheels, Curves, nodes, masks, Tracker, scopes, Gallery and Resolve FX. This guide shows where they are and how they work together.
Where should a beginner start color grading in DaVinci Resolve?
If you are new to the Color page, start with the Viewer and scopes, make the primary correction with Color Wheels, then place more complex adjustments on separate nodes. This keeps the grade much easier to understand.
What are Color nodes for and why use the Node Editor?
The Node Editor keeps all corrections from becoming one big pile. You can place balance, skin, masks, effects and the final look on separate nodes and always see what is changing the image.
Why use scopes if you can already see the result in the Viewer?
Use the Viewer to judge the picture with your eyes — skin tone, contrast and overall feel. Scopes show signal levels and help verify exposure, RGB balance and clipping. A reliable grade uses both.
Sources & version notes
Diagrams and interactives are teaching models, not replicas of Resolve’s interface or processing engine. Original screenshots are retained; layout depends on the version and workspace.
Illustrations in the interactive labs are teaching models. Resolve screenshots retain their original site URLs. Studio availability and control layouts should be checked against your installed version.