DaVinci Resolve Scopes Explained: How to Read Every Scope

A DaVinci Resolve scope is a measurement tool, not a creative one. The waveform plots image levels across the width of the frame and can show luminance or overlaid color components, the RGB parade separates selected components, such as RGB, YRGB or YCbCr, into individual traces, the vectorscope reads hue and saturation, the histogram gives you a tonal distribution at a glance, and CIE chromaticity checks whether your colors sit inside the gamut you're delivering to. None of them tell you if a shot looks good. They tell you what the signal is actually doing, which is a different question, and the one your eyes answer badly by the third hour of a session.

I graded a 37-shot interview block two years ago with the scopes closed the entire afternoon because I trusted a monitor that had quietly drifted warm since lunch. Every skin tone I'd corrected needed redoing the next morning once I opened the vectorscope against fresh eyes. That's the whole argument for scopes in one sentence: your monitor lies, your eyes adapt to the lie, and the scope doesn't care what either of you thinks it's seeing.

Tested in DaVinci Resolve 21 on the Color page. Scope names and menu placement are similar across recent Resolve versions, but individual options can move between builds, so treat exact menu paths below as a starting point rather than a fixed map.

Quick Map: Which DaVinci Resolve Scope to Use

Five scopes live in DaVinci Resolve's Color page, and you rarely need all five open at once.

• Waveform: best for checking overall exposure, clipped highlights and crushed shadows, in Luma, RGB, YRGB or YCbCr mode.
• RGB Parade: best for spotting a color cast, since it separates the signal into individual component traces.
• Vectorscope: best for hue, saturation and skin tone, plotted on a circular graph.
• Histogram: best for a fast read on how much of the frame sits in shadow versus highlight.
• CIE Chromaticity: best when gamut compliance matters, HDR delivery or wide-gamut masters especially.

Waveform and vectorscope cover most of what you'll check on an ordinary shot. Bring in the parade the moment you suspect one channel is running hot. The other two are situational, not constant.

What a DaVinci Resolve Video Scope Actually Measures

A scope takes every pixel in your frame and plots some property of it, brightness, color channel, hue, saturation, on a graph instead of a picture. It has no opinion about mood, intent or whether a shot is supposed to look cold and desaturated on purpose. It reports numbers. Your creative judgment still decides what the shot should be; the scope only confirms whether it's actually doing that or just looking like it is on a screen that's lying to you a little.

Open Video Scopes from the Workspace menu on the Color page, and DaVinci Resolve drops a floating panel you can dock, expand to a two-up or four-up layout, or push onto a second monitor entirely. A keyboard shortcut exists for this too, but it's changed enough between Resolve versions and platforms that I'd rather send you to the Workspace menu than hand you a combo that might not match your build. Set your own in Keyboard Customization once and it'll stick.

DaVinci Resolve Waveform: Exposure and Clipping

In Luma mode, the waveform maps each pixel's brightness from left to right, preserving its horizontal position in the frame. Height on the scope means brightness, not vertical position in the shot, and that trips up almost everyone the first month they use one. A bright object in the bottom corner of your frame still shows up near the top of the waveform. In RGB-based modes, the waveform displays channel information rather than brightness alone, covered in more depth below.

By default the vertical scale reads as 10-bit code values, 0 to 1023. If 10-bit values feel abstract, the scopes menu (the three dots above the panel) lets you switch the Waveform Scale Style to Percentage instead, which reads 0 to 100 the way the old IRE convention did. Millivolts and 12-bit are in there too. All of them describe the same signal; pick whichever one you can read fastest under pressure.

Most tutorials tell you to fill the waveform edge to edge for a "correctly exposed" shot. That's backwards for anything but a flat, evenly lit test chart. A bright exterior doesn't have to touch 100 percent to be correctly exposed; there's no single correct mark for every shot, since that depends on the subject, the lighting and the creative call. The waveform confirms your exposure decision. It doesn't hand you a target to hit regardless of what the shot actually needs.

DaVinci Resolve Waveform Modes: Luma, RGB, YRGB and YCbCr

Right-click the waveform, or open its three-dot menu, and you'll find more than one way to read the same signal. Luma, sometimes labeled Y, shows a single combined brightness trace for the whole image, the fastest read for overall exposure and the mode most colorists leave on by default. RGB overlays the three color channels on the same graph without separating them into their own lanes. YRGB adds the luma trace on top of those three channels together. YCbCr switches the scope to show luma plus the two chroma, color-difference, components instead of red, green and blue, a different read used more in broadcast and delivery compliance checks than in everyday grading.

For catching an ordinary color cast, the RGB parade with its separated channel lanes is the more direct tool. Reach for the waveform's YCbCr mode specifically when you need to check chroma levels against a broadcast spec rather than diagnose a general color imbalance.

DaVinci Resolve RGB Parade: Finding Color Casts

The parade separates the signal into individual traces, one each for red, green and blue by default, sitting side by side instead of blended into one luminance line. A properly neutral object, a white shirt, a grey wall, should show all three traces landing at roughly the same height. When one channel runs noticeably higher or lower than the other two, you're looking at a color cast, and the parade tells you which channel and roughly where in the tonal range the imbalance sits.

I once spent a good chunk of a session eyeballing a shot that looked slightly warm, unsure whether it was the grade or the monitor. The parade settled it almost immediately: the red trace sat visibly above green and blue through the midtones and highlights. That showed which channel was causing the cast and roughly where in the tonal range it lived. A small red-channel adjustment, not a blind gain pull by some fixed amount, brought the neutral areas back into alignment.

A strong colored light source in frame, a practical lamp, a neon sign, will legitimately bias the parade toward that color. You don't need to correct that away. Balance around the neutral parts of the image instead, skin, grey walls, a white shirt, and leave the stylistic light source doing what it's supposed to do.

DaVinci Resolve Vectorscope: Hue, Saturation and Skin

The vectorscope plots color on a circular graph. Distance from the center is saturation; angle around the circle is hue. A fully desaturated image, pure grayscale, collapses to a single point dead center. Push saturation on any color and its trace moves outward toward the edge, following the same rotational order as a standard color wheel.

Turn on the skin tone indicator in the vectorscope's menu and a diagonal line appears. Human skin under reasonably neutral lighting often clusters near a similar hue region on the vectorscope, but not at one universal coordinate. Complexion, undertone, lighting, makeup, white balance, camera color science and the creative look you're building can all move that trace in hue, saturation and brightness. Blackmagic's own description of the tool is similarly modest: the vectorscope is commonly used to check whether skin tones have shifted toward unflattering colors such as green, yellow or magenta, not to hit one universal coordinate.

That's not just theory. In a Creative COW forum thread, a colorist asked why aligning skin exactly onto the skin tone line pushed it visibly green on his monitor, even though the skin looked correct before the adjustment. The reply was direct: treat the line as a reference, not a rule, and don't force every shot onto it regardless of what your eyes and a calibrated monitor are telling you. Treat any specific saturation percentage you read online the same way, as a starting point, not a rule.

DaVinci Resolve Histogram: Distribution Without Position

The histogram uses the same family of tonal values as the waveform but reorganizes them by pixel count instead of preserving their horizontal position in the frame. Black sits at the left, white at the right, and DaVinci Resolve overlays red, green and blue distributions on top of each other so you can see channel-level clipping the same way you would on the parade.

If you shoot photography or came up through a DSLR workflow, the histogram will feel immediately familiar; it's the same display most cameras show on the back screen. That familiarity is also its limit for grading work. It tells you how many pixels sit at a brightness level but throws away where those pixels physically are in the frame, which is exactly the information the waveform keeps. I check it maybe once per session, usually on a tricky shot-to-shot match where a fresh angle on the same brightness data catches something the waveform didn't.

DaVinci Resolve CIE Chromaticity: Gamut Boundaries

CIE Chromaticity plots your image's colors against a triangle representing a target color space, Rec.709 for most SDR delivery, wider triangles for P3 or Rec.2020. Colors inside the reference triangle sit inside the displayed chromaticity boundary for that delivery space; traces outside it flag potential out-of-gamut values. This is one compliance check, not proof that the entire master is valid, since chromaticity alone doesn't represent brightness the way the waveform does, and a gamut mapping step or output transform further downstream can still change the result.

Treat this scope as a warning light, not a verdict. A shot can sit safely inside the triangle overall while one saturated highlight, a neon sign, a stage light, pokes past the edge in isolation. It's the scope I open least often on ordinary SDR work and the one I won't skip on anything shooting for HDR delivery or a wide-gamut master, where an out-of-gamut color can break a deliverable outright instead of just looking a little off.

DaVinci Resolve Scope Scale vs Data Levels: Do Not Confuse Them

DaVinci Resolve actually makes three separate level decisions, and mixing them up is one of the more common technical mistakes in a grading session: how the source clip is interpreted, how the scope scale is displayed, and how the rendered file is mapped and tagged on output.

Changing the scale style, 10-bit, 12-bit, Percentage or millivolts, only changes how the same underlying values are labelled on the ruler. It's like switching a tape measure from inches to centimeters: the object you're measuring doesn't change size, only the numbers describing it do.

Source interpretation is a different question: whether Resolve reads your clip as Video (legal) range or Full (data) range. Get that wrong and every reading downstream, scopes included, measures the wrong thing before you've touched a single control. Output range is a third, separate decision made on the Deliver page, determining how the rendered file itself is mapped and tagged. Changing the scope display changes none of that; check the source interpretation first, then the Deliver page's range setting, and use whichever scope scale is easiest for you to read.

In a nominal 10-bit video-range signal, RGB and luma map black and white to code values 64 and 940. The chroma components, Cb and Cr, use a nominal 64 to 960 range centered on a neutral value of 512. Full range uses the wider 0 to 1023 span across all of them. Most broadcast masters expect video, or legal, range.

Do not choose full range just because the destination is the web. YouTube's own encoding documentation confirms it converts full-range uploads to limited range during processing, so full range isn't automatically the safe choice for online delivery either. What matters is that your source interpretation, Resolve's output setting and the file's range metadata all agree with each other; a mismatch there, not the destination platform, is what produces washed-out blacks or crushed levels after upload. Our YouTube export settings guide covers the color space and range fields for that delivery target specifically, and the Color Grading hub covers where color management fits before you get to a range question at all.

DaVinci Resolve Low Pass Filter and Qualifier Focus

Two options buried in the scopes' three-dot menu do more work than their names suggest. Low Pass Filter smooths noise out of the waveform and parade trace, which matters most on grainy or high-ISO footage where the raw trace looks like static instead of a readable line. It cleans up the display only; it changes nothing about the actual image or grade underneath.

Display Qualifier Focus links your viewer to your scopes directly. Turn it on, hover over any part of the image, and DaVinci Resolve highlights exactly where that pixel lands across every open scope. Point at a face and watch where it sits on the vectorscope relative to the skin tone line. Point at a blown highlight and watch it spike the waveform. It's one of the fastest ways to learn what you're actually looking at on a scope instead of memorizing shapes without understanding what produced them.

DaVinci Resolve Scopes and the Node Tree: What They Actually Measure

Scopes read the signal currently displayed by the viewer. In the normal Color page view, that's the output of the complete enabled node graph, not automatically the output of whichever node happens to be selected. Selecting an earlier node changes which correction you're editing; it doesn't by itself remove downstream nodes from the viewer or the scopes.

To inspect an intermediate stage, temporarily disable the downstream nodes or use the appropriate preview or bypass control in your Resolve build. Isolating an area with a qualifier or power window and switching to Highlight view does narrow what the scopes are reading to that selection, so always check whether Highlight mode is active before interpreting a trace that looks unexpectedly small or unexpectedly clean.

A Four-Step DaVinci Resolve Scope Workflow

I run the same four checks on nearly every shot before calling a grade finished, in this order:

1. Waveform first, for overall exposure. Shadows off the floor, highlights off the ceiling, nothing clipping that shouldn't be.
2. Parade second, for color balance. All three channels roughly aligned on neutral elements, any intentional color bias coming from an actual light source rather than an accident.
3. Vectorscope third, for saturation and skin. Trace centered if the shot should read neutral, skin sitting near its reference line if a face is in frame.
4. CIE Chromaticity only when the delivery target demands it, HDR masters and wide-gamut work specifically.

None of this replaces your eyes. The scopes settle the technical questions, whether something is actually clipped, actually neutral, actually within a reasonable saturation range, so your creative judgment can focus on mood and intent instead of guessing whether the monitor in front of you is telling the truth right now.

DaVinci Resolve Scopes: Free vs Studio

The same five standard scope types, waveform, parade, vectorscope, histogram and CIE chromaticity, are available in both the free version and Studio for ordinary SDR work. The graticule styles, the scale options, the Data Levels versus Video Levels toggle, the skin tone indicator, none of it sits behind the $295 Studio license. If you've read elsewhere that Studio unlocks "better" scopes across the board, that's not accurate for standard dynamic range work.

The scope-specific Studio addition documented on Blackmagic's own Studio product page is professional HDR measurement: a nit-based scale for ST.2084 (PQ) and HLG signals, letting you swap the waveform and parade's 10-bit scale for a reading in cd/m². This helps verify HDR luminance targets, but it's only one part of validating a full Dolby Vision, HDR10 or HDR10+ deliverable; the output transform, mastering display data, metadata and the deliverable format all matter too. Every SDR reading in this guide, waveform, parade, vectorscope, histogram, CIE chromaticity, works exactly the same whether you paid for Studio or not. If your color work stays in standard dynamic range, you're not missing anything on the scopes front by staying on the free version.

Common DaVinci Resolve Scope Mistakes

• Chasing the skin tone line as a hard target. It's a reference point, not a rule, and forcing every face onto it regardless of lighting and undertone can push a correct-looking shot toward an actual color error.
• Assuming a color cast will fix itself with a fixed Gain pull. The parade tells you which channel and roughly where in the tonal range the problem sits; the right tool, Offset, Gain, Gamma or a channel control, depends on where that mismatch actually lives.
• Reading a scope set to the wrong range. A legal-range signal read against a full-range scope, or the reverse, looks wrong even when the actual delivery is fine. Confirm the setting before trusting the trace.

• Assuming full range is automatically safe for the web. YouTube converts full-range uploads to limited range during processing; match your source interpretation and output setting to your delivery target instead of guessing by destination.
• Assuming the selected node limits what the scopes show. The viewer and scopes read the full enabled node graph by default, not just the selected node. Disable downstream nodes if you need to inspect an earlier stage.
• Ignoring CIE Chromaticity until the HDR delivery already broke. It's the one scope worth checking early on wide-gamut or HDR work, not after a client rejects the master.

DaVinci Resolve Scopes FAQ

What is the best scope to use in DaVinci Resolve?

Waveform and vectorscope cover most day-to-day decisions: waveform for exposure, vectorscope for color balance and skin. Bring in the parade when you suspect a specific channel imbalance, and reach for CIE chromaticity specifically on HDR or wide-gamut delivery.

Are DaVinci Resolve's scopes different in the free version?

No. Waveform, RGB parade, vectorscope, histogram and CIE chromaticity are identical in the free version and Studio for SDR work. The Studio-specific addition is professional HDR measurement, a nit-value scale for ST.2084 or HLG signals, which is only one part of validating an HDR deliverable. See the free version features breakdown for the rest of what Studio adds outside of scopes.

Should I trust my monitor or my scopes in DaVinci Resolve?

Trust the scopes for technical questions: is this clipped, is this neutral, is this within a reasonable saturation range. Trust your eyes for mood, intent and whether the creative choice is working. Your monitor drifts with ambient light and its own warm-up time in ways the scope simply doesn't.

Why doesn't my skin tone line up with the vectorscope's skin tone indicator?

It might not need to. The skin tone line is a reference angle, not a strict target; complexion, undertone, lighting, makeup and camera color science can all shift it. Use it to catch obvious drift, not as a single coordinate every face must hit.

Should I grade to legal range or full range in DaVinci Resolve?

Match whatever your delivery target expects rather than picking one by destination. Broadcast masters typically require legal range, 64 to 940 for RGB and luma on the 10-bit scale, 64 to 960 for chroma. Full range isn't automatically the safe choice for web delivery either, since YouTube converts full-range uploads to limited range during processing. Check your source interpretation and Deliver page range setting, not just the scope's scale display, before trusting the reading.

What is CIE Chromaticity used for in DaVinci Resolve?

It plots your image's colors against a triangle representing your delivery color space, such as Rec.709 or a wider P3 or Rec.2020 triangle. Traces outside the triangle flag potential out-of-gamut values for that space. Treat it as one compliance check, not proof the whole master is valid.

Why does the histogram look different from the waveform in DaVinci Resolve?

Both use the same tonal values, but the histogram counts how many pixels sit at each brightness level with no information about where they are in the frame, while the waveform preserves that horizontal position. Use the waveform to find which part of the image is too bright or too dark; use the histogram for a fast overall read on shadow-to-highlight distribution.

Why aren't my scopes showing up in DaVinci Resolve?

Open Video Scopes from the Workspace menu on the Color page. If the panel opens but stays blank, confirm a clip is actually loaded and selected on the timeline, since scopes read the currently active clip's signal and show nothing without one.

What's the difference between IRE and 10-bit values on DaVinci Resolve's scopes?

They describe the same signal on different scales. IRE, and the closely related Percentage scale, run 0 to 100. The default 10-bit scale runs 0 to 1023 for the same range. Switch between them in the Waveform Scale Style menu; neither changes your actual grade.

Can I zoom in on the DaVinci Resolve vectorscope?

Yes. The vectorscope's menu includes a zoom option, commonly used at 2x, which enlarges the trace so a small cluster, an isolated skin tone especially, becomes easier to read against the skin tone line.

Why do my DaVinci Resolve scopes look different after I export?

The Color page scopes measure the signal at Resolve's current viewer and scope tap point. An exported file can look different because of an output color-space transform, a data-level mapping change, codec quantization, metadata tags, or the color management used by the playback application, not necessarily because the grade itself changed.

Scopes are the part of DaVinci Resolve that take the least time to open and the longest to actually read well. Once you stop treating them as decoration next to the viewer and start checking them on every shot, grading gets faster, not slower, because you stop re-litigating decisions your eyes already got wrong once under the wrong light.

Related guides

• Color Grading in DaVinci Resolve: the hub: where scopes and color management fit into the full grading path.
• How to Color Grade in DaVinci Resolve: Beginner Tutorial: the full correction-first workflow these scopes plug into.
• DaVinci Resolve Nodes Explained: the node tree logic you'll be reading scopes against.
• How to Use LUTs in DaVinci Resolve: keeping a LUT's effect on the scopes predictable.
• DaVinci Resolve YouTube Export Settings: the range and color space fields that matter once your scopes look right.
• DaVinci Resolve vs Studio: what Studio actually adds beyond the HDR nit-value scope scale.
• DaVinci Resolve Auto Color: how it works, when it fails

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