# How to Calibrate Your Monitor for DaVinci Resolve Color Grading

> **Quick answer:** To calibrate your monitor for DaVinci Resolve color grading, use a hardware colorimeter, not your eyes, and set a D65 white point, gamma 2.4, and about 100 cd/m2 in a dim room. Match those exact numbers in Resolve's Color Management tab under Rec.709 Gamma 2.4, or your grade is guesswork.

*Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.*
*Updated 2026-07-31 · DaVinci Resolve 21.0.3 (July 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/how-to-calibrate-your-monitor-for-davinci-resolve-color-grading*

I've watched a client reject a grade over a color shift that didn't exist in the file. It existed in their monitor. That's the whole problem with skipping calibration: a wrong screen doesn't announce itself, it just quietly tells you a lie you have no way to catch.

As of July 2026, on DaVinci Resolve 21.0.3, that problem hasn't gone away. It's gotten easier to overlook, because Resolve's Color Management tab, its scopes, and its automatic input detection all look like they're handling color accuracy for you. They aren't. Every one of those tools assumes your display is already telling the truth, and none of them can fix a monitor that isn't.

This guide covers what "calibrated" actually means for a DaVinci Resolve workflow, the hardware that gets you there, the exact D65 and gamma numbers to target, and how to make Resolve's own settings match what your calibrated screen is showing. It also covers the room around the monitor, the difference between SDR and HDR targets, the specific mismatches that make people think their calibration failed when the real problem was somewhere else entirely, and the operating-system quirks on both Mac and Windows that trip people up after the hardware calibration is already done correctly.

## What does it mean to calibrate your monitor for DaVinci Resolve?

Calibrating a monitor for DaVinci Resolve means measuring what your screen actually outputs with a hardware sensor, then correcting it, through firmware, an ICC profile, or a 3D LUT, until it hits a known, industry-standard target: a specific white point, a specific gamma curve, and a specific brightness level.

That's a different thing than "adjusting" a monitor by eye. Adjusting by eye uses your own perception, which adapts constantly to whatever light is already in the room, as the reference. Calibration uses a colorimeter or spectrophotometer, a physical sensor that reads light the same way regardless of how tired you are, what time of day it is, or what color shirt you're wearing under the monitor's glow. **A calibrated monitor and a good-looking monitor are not the same thing, and a screen can be one without being the other.**

The three numbers every calibration targets are the same three numbers professional broadcast and cinema specs have used for decades: a D65 (6500 Kelvin) white point, a gamma curve (2.4 for controlled grading rooms, 2.2 for brighter environments), and a luminance level, typically 100 to 120 cd/m2 for SDR work. Get a hardware sensor to confirm your screen actually hits those three numbers, and you've calibrated it. Everything else in this guide is about getting there correctly and keeping DaVinci Resolve's own settings aligned with what you did.

## What's the difference between calibrating a monitor and profiling it?

The two words get used interchangeably, and that mix-up causes real problems in a Resolve workflow, because "calibrate" and "profile" describe two different steps that happen to run through the same software session.

Calibration changes the monitor itself. Your calibration software sends commands to the display's own hardware controls, or to your graphics card's gamma lookup table, and physically alters what the panel outputs: its white point, its gamma response, its brightness. A well-calibrated screen is closer to a true D65, gamma 2.4 target before any software correction happens downstream of it.

Profiling comes after, and it doesn't change the monitor at all. It measures whatever residual error is still left once calibration is done, and it writes that error into an ICC profile, a small file your operating system's color management system can read and use to correct colors on the fly for applications that respect it.

**A profile can only help an application that actually asks your operating system for it, and DaVinci Resolve's own GUI viewer doesn't, by default, on either macOS or Windows.** That's the practical reason this distinction matters here. A perfect ICC profile sitting unused on your system does nothing for a Resolve viewer window that never checks it, which is why the calibration step, the part that changes the monitor's actual output rather than just describing its error, is the piece Resolve depends on. The Mac and Windows sections further down in this guide cover exactly how each operating system's color management does, and doesn't, reach into what Resolve shows you.

## Why isn't eyeballing your screen enough for color grading in DaVinci Resolve?

Eyeballing fails because human color perception adapts to its surroundings within seconds, and a display's own output drifts over weeks without you noticing either change happening.

Two mechanisms work against you at once. The first is chromatic adaptation: your eyes recalibrate to whatever white point is dominant in a room, the same way a white shirt looks white under both fluorescent office light and warm incandescent light, even though the actual wavelengths hitting your eyes are completely different. A monitor drifting warm over months looks normal to you the whole time, because your perception drifted with it.

The second is panel aging. LCD backlights lose brightness and shift color temperature as they age. OLED panels drift too, and per Hollyland's guide on the subject, this is exactly why panels, especially OLEDs and older LCDs, need to warm up for at least 30 minutes before a calibration session even starts, since they shift color as they heat from a cold start. If the panel itself moves during a 30-minute warmup, it's certainly capable of moving over the months between "looks fine" and "client rejects the delivery."

**If you cannot verify your monitor's actual output with a sensor, you are grading against a moving target that your own eyes cannot detect moving.** That's not a knock on your eye for color, colorists develop genuinely excellent relative color judgment over years of work. It's a statement about what eyes are built to do, and matching an absolute, numeric standard like D65 isn't it. That's the entire reason hardware colorimeters exist as a separate product category from "a good monitor."

## What hardware do you actually need to calibrate a monitor for DaVinci Resolve?

You need one piece of hardware, a colorimeter or spectrophotometer, plus calibration software to drive it. Everything else is optional depending on your monitor and budget.

A colorimeter is the entry point. It reads red, green, and blue light through filters tuned to the human eye's sensitivity curve, and it's accurate and inexpensive for standard LCD and most OLED panels. A spectrophotometer measures the full visible spectrum directly instead of through filters, which makes it more accurate on wide-gamut and unusual backlight technologies, and it's the tool of choice for calibrating other colorimeters against, not just for calibrating a display directly.

For most single-editor and freelance setups, a colorimeter is the right call. Per PremiumBeat's own reporting, a Datacolor SpyderX Pro runs $169.99, cheap enough that the cost argument for skipping calibration mostly evaporates. If you're working with a wide-gamut or HDR-capable display, step up to a high-luminance model. Calibrite's Display Plus HL, according to its own B&H Photo Video product listing, measures up to 10,000 cd/m2, five times the range of the standard Display Plus, specifically to stay accurate on the newest Mini-LED and OLED panels rather than saturating or reading inaccurately near the top of their brightness range the way a standard colorimeter can.

Here's how the tiers break down:

| Hardware tier | Example | Best for | Rough price |
| --- | --- | --- | --- |
| Entry colorimeter | Datacolor SpyderX Pro | Single SDR monitor, freelance and YouTube work | $169.99 |
| Professional colorimeter | Calibrite Display Pro HL | Wide-gamut LCD/OLED, up to 3,000 cd/m2 | Mid-range |
| High-luminance colorimeter | Calibrite Display Plus HL | HDR grading, Mini-LED and OLED up to 10,000 cd/m2 | Premium |
| Spectrophotometer | X-Rite i1Display Pro (i1 series) | Reference monitors, unusual backlights, calibrating other sensors | Premium |

You'll also need software: a calibration engine that talks to the sensor and drives your monitor or Resolve through test patterns. DisplayCAL is free and open source, and per Lowepost's own coverage of the process, it's widely considered more accurate than the bundled software that ships with many consumer colorimeters. i1Profiler is X-Rite's own software. CalMAN is the industry standard for broadcast and reference-monitor work, and per Flanders Scientific's own CalMAN calibration guide for its AM, BM, CM, and DM series monitors, DaVinci Resolve itself can act as CalMAN's test pattern generator, sending calibration patches directly from Resolve to the display while the software reads them back through the probe. You don't need a separate hardware pattern generator if Resolve is already in your signal chain.

## What are the correct calibration targets for color grading in DaVinci Resolve?

Three numbers matter for standard SDR grading: a D65 white point, a gamma of 2.4 or 2.2 depending on room brightness, and a luminance of roughly 100 to 120 cd/m2.

D65, corresponding to a 6500 Kelvin color temperature, is the white point standard across video and cinema work, and it's the same reference white ITU-R BT.2408's own operational guidance for HDR production builds on. Set your monitor's white point here and don't deviate from it for creative reasons. Any warm or cool "look" belongs in your grade, applied deliberately and visibly in the node graph, not baked silently into your reference display where you can't see it happening and no one downstream can undo it.

Gamma is where the room you're working in actually changes the right answer. **Gamma 2.4, following the BT.1886 standard, is the correct target for a dim, controlled grading room, and it's also the broadcast and cinema delivery standard DaVinci Resolve's own Rec.709 Gamma 2.4 output preset is built around.** If you're working in a brighter office or living room environment, or delivering content that's consumed almost entirely on phones and laptops in ambient light, gamma 2.2, the sRGB standard, is the more honest target, since it accounts for the added stray light hitting your eyes and your screen in that kind of room.

Luminance is the third leg. Per Hollyland's calibration guide, 100 cd/m2 is the standard target for a properly dim grading suite, and 120 cd/m2 is the more practical number for a typical office environment with real ambient light present. Push much brighter than that for SDR work and you're grading against a monitor that's punchier than any actual delivery target, which reads as an over-contrasted, harsh grade the moment it's viewed correctly somewhere else.

| Setting | Dim grading room | Brighter office/home setup |
| --- | --- | --- |
| White point | D65 (6500K) | D65 (6500K) |
| Gamma | 2.4 (BT.1886) | 2.2 (sRGB) |
| Luminance | ~100 cd/m2 | ~120 cd/m2 |
| Ambient/bias light | D65, ~5 cd/m2 bias light only | Controlled but present room light |

Whichever pair you land on for gamma and luminance, the number that actually matters is that it's a deliberate choice, documented somewhere you'll remember, not whatever your monitor happened to ship with out of the box.

## How do you calibrate a monitor step by step for DaVinci Resolve?

Here's the actual sequence, in order, the same shape whether you're using a $170 colorimeter or a broadcast-spec spectrophotometer.

1. **Warm up the monitor for at least 30 minutes.** Per Hollyland's guide, panels, especially OLEDs and older LCDs, shift color as they heat from a cold start, so calibrating immediately after power-on bakes a temporary drift into your profile.
2. **Reset the monitor to factory defaults** through its on-screen display menu. Any prior manual tweaking, a saturation nudge, a brightness bump, needs to be zeroed out before a fresh calibration can measure anything meaningful.
3. **Disable every dynamic display feature**: Auto-Brightness, Eco Mode, Dynamic Contrast, ambient light sensors, and any local dimming setting that isn't a fixed backlight level. These features actively fight a static calibration by changing output in response to content or room light.
4. **Darken the room and set up bias lighting.** Turn off overhead and task lighting, and set a neutral D65 bias light behind the monitor, covered in more depth in the room setup section below.
5. **Mount the sensor on the panel**, either with a counterweight strap for a colorimeter or a tripod-mounted spectrophotometer pointed straight at the screen's center, non-angled.
6. **Open your calibration software** (DisplayCAL, i1Profiler, or CalMAN) and set your targets: D65 white point, your chosen gamma, your chosen luminance.
7. **Run the profiling pass.** The software steps through a sequence of color and grayscale patches while the sensor reads each one, building a correction curve or LUT from the difference between what was requested and what the sensor actually measured.
8. **Save the result** as an ICC profile for your operating system, or as a 3D LUT if your monitor or a LUT box supports loading one directly, which is generally the more accurate path for a professional reference display.
9. **Verify the result** with a second pass or a validation report from the software, checking that your Delta E, the numeric measure of color error covered later in this guide, sits in an acceptable range rather than just trusting the process completed without an error message.

Two of those steps trip people up more than the rest. Step 3 gets skipped constantly because dynamic display features are often buried two or three menus deep in a monitor's OSD, and a calibration run against a screen that's still auto-adjusting brightness will produce a profile that's already wrong the moment ambient light in the room changes even slightly. And step 9 gets skipped because it feels redundant, but a colorimeter that's slipped slightly out of position, or a monitor that didn't fully accept the correction curve, produces a "successful" calibration run that's still measurably off. Fifteen extra minutes checking your work here is cheaper than a client catching the error for you.

## How do you set up DaVinci Resolve's Color Management tab to match your calibrated monitor?

Open Project Settings, go to the Color Management tab, and set your Timeline and Output Color Space to match the exact gamma and gamut you just calibrated your monitor against, not whatever Resolve defaults to.

This is the step people forget, because it feels like it's already done once the monitor is calibrated. It isn't. Calibrating your display and configuring Resolve's color management are two separate systems solving two separate halves of the same problem, and neither one knows what the other is set to unless you set them to match deliberately. Per Frame.io's own cheat sheet on Resolve's color management setup, DaVinci Wide Gamut Intermediate as your working space with an output transform to Rec.709 Gamma 2.4 remains the standard, all-around setup for most editors, and that Gamma 2.4 output is exactly what a properly calibrated grading-room monitor should be showing.

The practical checklist:

- **Color Science**: DaVinci YRGB Color Managed, with DaVinci Wide Gamut Intermediate as your preset, unless your project has a specific reason to run ACES instead. Our [full comparison of Resolve Color Management and ACES](https://tryuncle.com/learn/davinci-resolve/resolve-color-management-vs-aces-which-should-i-use) covers which one actually fits your project if you're unsure.
- **Output Color Space**: Rec.709 Gamma 2.4 if your monitor is calibrated to that target, or the corresponding 2.2/sRGB setting if it isn't.
- **Data Levels**: set explicitly to match your monitor's own data-level setting (Video or Full), never left on Auto. Per Hollyland's guide, Auto is described as unreliable specifically because it guesses rather than reads your actual signal path, and a mismatched guess here silently crushes blacks or lifts them, in a way that looks like a calibration problem but isn't one.
- **Monitor LUT**: if your calibration software produced a 3D LUT rather than a system ICC profile, load it into Resolve's Video Monitor LUT slot for the specific display it belongs to, not into the general viewer settings, so it only applies to the calibrated screen it was built for.

**A monitor calibrated to D65 and gamma 2.4, paired with a DaVinci Resolve project still outputting gamma 2.2, will look wrong in a way that resembles a bad calibration but is actually a setting that was simply never changed to match.** This is one of the most common false alarms in a grading setup: the hardware did its job correctly, and the software configuration one layer up just wasn't told about it.

## Should you monitor through the GUI viewer, a clean feed, or a dedicated I/O device?

The signal path between DaVinci Resolve and your monitor matters as much as the calibration itself, and the three common paths carry very different accuracy.

The GUI viewer, Resolve's own on-screen preview window rendered by your computer's GPU on your main display, is the least accurate path. It's subject to your operating system's own display compositing and color handling, it typically renders in 8-bit regardless of your project's actual bit depth, and on a Mac specifically it may or may not reference your ColorSync display profile depending on a preference setting covered in the next section. It's fine for editing. It's not a reliable reference for a final color decision.

A clean video feed through a monitor's own HDMI or DisplayPort input, driven by your computer's second video output rather than a dedicated capture card, is a step up, since it bypasses the GUI window chrome and gets closer to a direct signal, but it's still running through your GPU driver's own scaling and color handling rather than a purpose-built video path.

A dedicated I/O device, a Blackmagic DeckLink or UltraStudio, is the accurate path. It sends a clean, uncompressed video signal at your project's actual bit depth directly to a reference monitor, completely bypassing your operating system's GPU compositing and color management stack. This is the path professional grading suites use, and it's also the path CalMAN and similar calibration software expect when Resolve is acting as their test pattern generator, per Flanders Scientific's own calibration documentation for its reference monitors.

| Signal path | Approximate cost | Accuracy | Best for |
| --- | --- | --- | --- |
| GUI viewer only | $0 | Low, OS-dependent | Editing, rough color |
| Clean feed via second GPU output | $0 | Medium | Client review, budget grading |
| Dedicated I/O device (DeckLink/UltraStudio) | $120 to $1,000+ | High, bypasses OS entirely | Professional color grading |

If you've calibrated a beautiful reference monitor and you're still previewing your grade through Resolve's GUI window on your laptop's built-in display, you haven't actually put that calibration to work yet. The calibrated monitor needs to be the thing you're grading against, connected through a path that doesn't reintroduce the exact color handling problems calibration was supposed to eliminate.

## Why does DaVinci Resolve look different from QuickTime Player or a browser on the same Mac?

Because Resolve, unlike QuickTime Player, a web browser, or Photoshop, doesn't reference your Mac's ColorSync display profile by default, so the same file can render two visibly different ways on the exact same screen depending on which app is showing it.

Per a Blackmagic Forum thread specifically about this behavior, Resolve doesn't use ColorSync by default the way most Mac applications do, and its "Use Mac display color profiles for viewers" preference exists specifically to close that gap by letting Resolve reference whatever profile is active in macOS's own Displays settings, the same way QuickTime Player already does automatically. Rodrigo Polo, writing about this exact color shift on his own blog, frames the tradeoff plainly when describing the common fix of enabling that preference alongside an sRGB output setting: doing so, in his words, means "you are just disabling color management for your delivery" rather than actually reconciling the two systems, since it papers over the mismatch instead of fixing which color space each application thinks it's showing.

A second, related mismatch shows up specifically on export. Per a Blackmagic Forum thread on the subject, Resolve added a Rec.709-A gamma option specifically because Apple's own frameworks misinterpret a standard Rec.709 Gamma 2.4 file's metadata tag, which produces a washed-out, lower-contrast look the moment that file gets opened in QuickTime Player or uploaded to a platform like YouTube that runs it through Apple's decode path. Setting your Deliver page's gamma tag to Rec.709-A instead of leaving it on "Same as Project" fixes that specific mismatch for anyone finishing in gamma 2.4 on a Mac, without touching your actual grade.

**A perfectly calibrated monitor and a perfectly configured Resolve project can still disagree with QuickTime Player on the same Mac, because the mismatch lives in a third layer: whether each individual application references the operating system's color profile at all.** That's not a calibration failure. It's a compatibility setting, and it's fixed with a checkbox and a gamma tag, not a recalibration.

## Does macOS's built-in Display Calibrator Assistant work for DaVinci Resolve color grading?

Not on its own, and not for anything you're delivering to a client. Apple's built-in tool, reached through System Settings, Displays, Color Profile, Calibrate, is a real calibration utility, but its default walkthrough is a perceptual one: it asks you to visually match target patches and slide brightness controls by eye, then builds a profile from your own subjective judgment rather than from a sensor's measurement, per Apple's own support documentation on calibrating a Mac display.

That's the exact eyeballing problem covered earlier in this guide, just wrapped in a nicer interface. A hardware colorimeter reads the actual light your panel emits and corrects against that measurement. Apple's assistant, run without a hardware sensor, corrects against what you perceived in that moment, in that room, under whatever ambient light was hitting your eyes. It's genuinely useful for getting a personal laptop closer to a sane default. It isn't a substitute for the colorimeter-and-DisplayCAL, i1Profiler, or CalMAN workflow this guide walks through, and it isn't something you'd want a paying client's deliverable riding on.

Two macOS-specific settings sit on top of this and deserve their own callout, because neither Photoshop, Lightroom, nor DaVinci Resolve can override them from inside the app: True Tone and Night Shift. Both are operating-system-level features that continuously shift your display's white point and color rendering, True Tone based on ambient light sensors, Night Shift based on time of day, and per Apple's own support page on True Tone, both should be turned off for any color-critical work, including photo editing, video grading, and print proofing. Since these features operate below the application layer, an app has no way to detect or compensate for them, which means a monitor you calibrated perfectly an hour ago can be quietly shifted by True Tone reacting to a cloud passing over your window. Turn both off in System Settings, Displays, before you start a calibration session, and leave them off for the whole grading session, not just the calibration pass itself.

## How does monitor calibration work differently on Windows?

The hardware and the target numbers, D65, your chosen gamma, roughly 100 to 120 cd/m2, don't change on Windows. What changes is how the operating system loads and applies the result, and that has its own gotchas separate from anything covered in the Mac section above.

Windows 10 and 11 load ICC profiles and, on newer hardware, a full hardware-accelerated calibration pipeline through the Windows Color System, per Microsoft's own developer documentation on the display calibration pipeline. In practice that means your calibration software writes a profile, Windows Settings, System, Display, Color Profile is where you confirm the right one is assigned to the right monitor, and from there most color-managed applications on the system read it automatically. DaVinci Resolve's GUI viewer sits in a similar position on Windows as it does on Mac: it's a rendering surface your GPU draws to, and it doesn't guarantee it's asking the OS for that profile the same way a fully color-managed app like Photoshop does, which is exactly why the calibration itself, not just the profile sitting on disk, is what a Resolve session actually depends on.

Night Light is Windows's equivalent of Night Shift, a system-wide, time-based color temperature shift, and per Microsoft's own support documentation on display brightness and color, it lives in Settings, System, Display, and can be toggled off from there or directly from the Action Center. It needs to be off for the same reason True Tone needs to be off on a Mac: it operates below any individual application, including Resolve, and a calibrated monitor with Night Light quietly active is not actually showing you D65 anymore, regardless of what your calibration software reported minutes earlier.

One more Windows-specific wrinkle worth knowing if you're on an HDR-capable display: turning on Windows HDR restricts some ICC-managed apps to a narrower color window unless you specifically enable Windows's legacy display ICC color management option for that app, since standard ICC profiles were designed for SDR and don't map cleanly onto an HDR display's wider gamut on their own. If your grading monitor is HDR-capable and you're seeing unexpected color behavior in Resolve or your calibration software right after enabling Windows HDR, that setting is the first thing worth checking before assuming your calibration itself failed.

## How should you set up your room: bias lighting, wall color, and ambient light?

Set bias lighting to D65 at roughly 5 cd/m2 behind the monitor, keep the surrounding room dark and neutral, and paint or drape any wall in your direct line of sight a neutral mid-gray rather than white, black, or a strong color.

Bias lighting is a small, dim light placed directly behind your monitor, angled away from you and toward the wall behind the screen. Its job isn't to light the room, it's to give your eye's iris a consistent reference brightness so it doesn't have to constantly readjust between a bright screen and a pitch-black surrounding room, which causes real eye strain over a long grading session and subtly shifts your perceived contrast and saturation as your pupil dilates and contracts. Per ProVideo Coalition's own coverage of grading room setup, professional bias illumination should sit at D65, matching your monitor's white point, at a luminance of approximately 5 cd/m2 measured at the display surface, dim enough to do its job without competing with the actual image on screen.

The wall directly behind and around your monitor matters more than most home setups account for. A pure white wall reflects too much light back at the screen and biases your eye toward reading everything on screen as slightly darker and more saturated than it actually is. A pure black wall does the opposite, and a colored wall introduces a color cast your eye will partially, invisibly compensate for. The generally recommended target, per ProVideo Coalition, approximates a middle gray, roughly Munsell N5, sitting in the middle of the reflectance scale, with N7 or N8 latex paints offered as more affordable, close-enough alternatives for a home setup that doesn't need studio-spec precision.

None of this is theoretical. Alan Brown, the developer of the bias-lighting product Ideal Lume, put the underlying point bluntly in that same ProVideo Coalition piece: "The room is always critical in both sound and video and the one component that gets ignored is the viewer." A calibrated monitor sitting in an uncontrolled room is still being viewed by a human eye that's constantly recalibrating itself against whatever light is actually in that room, which is exactly the variable a good bias-lighting and wall-color setup is built to remove.

You don't need a purpose-built grading suite to apply this. A single D65 LED bias light strip behind a monitor, a roll of neutral gray fabric or paint on the visible wall section, and the discipline to turn off overhead lighting during a session covers most of what a professional room buys you, at a fraction of the cost.

## What is Delta E, and how do you read a calibration validation report?

Delta E, usually written dE or dE2000 in a calibration report, is the number your software uses to say how far off a measured color is from the target color it was supposed to produce. It's the single most useful number on a validation pass, and most people skip straight past it to the pass or fail summary at the top of the report.

Per Tom's Hardware's own explanation of the metric, a dE2000 value under 1 is excellent and generally imperceptible in normal viewing, and an average under 2 is considered the practical bar for trustworthy professional work across photo, design, and video. Values between 2 and 3 are still usable but leave less margin for skin tones, client proofing, and matching color across multiple displays, and anything consistently above 3 is where visible drift becomes a real concern rather than a rounding error.

That scale gives the earlier verification step in this guide a concrete target: after a calibration run, don't just glance at a "calibration complete" message, open the actual validation report and check the average and maximum dE2000 figures it reports. An average under 2, with no single patch spiking wildly above that, is what a healthy SDR grading monitor should show. A report sitting consistently in the 3-to-5 range on a monitor you just calibrated points at a deeper problem: the panel's native gamut may not fully cover what you're targeting, the sensor may have shifted during the pass, or, as the next section covers, the sensor itself may be the thing that's drifted.

| Average dE2000 | What it means | What to do |
| --- | --- | --- |
| Under 1 | Excellent, imperceptible drift | Nothing, this is a healthy calibration |
| 1 to 2 | Ideal for professional client work | Nothing, this is the standard target |
| 2 to 3 | Usable but tighter margins on skin tones and matching | Acceptable for rough color, recheck before final delivery |
| Above 3 | Visible drift | Recalibrate, check the sensor, or check the panel's gamut coverage |

## How often should you recalibrate, and how do you know your monitor has drifted?

Recalibrate monthly as a professional floor, weekly if you're on OLED or running mission-critical delivery work, and treat any grade that suddenly needs correction it didn't need last month as a signal to check calibration before anything else.

Backlights age. LCD panels lose brightness gradually and shift color temperature as they do, and OLED panels drift in their own way as individual subpixels age at slightly different rates depending on how much red, green, or blue content they've displayed over their lifetime. Neither of these processes announces itself with an error message. They show up as a monitor that quietly isn't telling you the truth anymore, exactly the failure mode calibration exists to catch.

There's no universal number for how fast a given panel drifts, since it depends on backlight technology, usage hours, and how bright you typically run the display, which is exactly why a fixed recalibration schedule, rather than waiting for a visible problem, is the standard professional practice. If your monitor's calibration software logs Delta E validation numbers over time, watch that trend rather than just the pass/fail result of each individual run.

Between full recalibrations, your scopes are the honest backstop. A waveform, vectorscope, or parade display reads pixel values mathematically, independent of anything your monitor is doing to display them, which means it can't be fooled by a drifted panel the way your eye can. If a grade looks subtly off but your scopes read exactly where you'd expect them to for that shot, the problem is very likely your display, not your grade. It's worth checking that the scopes themselves are actually behaving before you trust that read; a frozen or misbehaving scope panel is a [separate, well-documented issue](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-scopes-not-updating) that can masquerade as either a calibration problem or a grading mistake, so rule it out first, then stop grading and recheck calibration rather than second-guessing the work you already did.

**A monitor that looked perfect at your last calibration session can drift into looking equally convincing and equally wrong six weeks later, without a single visible warning sign along the way.** That's not a hypothetical. It's the specific, quiet failure mode a recalibration schedule exists to catch before a client does it for you.

## Does your colorimeter itself need to be recalibrated?

Yes, and this is the drift nobody checks. Every colorimeter and spectrophotometer is a physical measurement instrument, and physical instruments drift for the same underlying reasons your monitor does: components age, internal light sources and filters change, sensors lose sensitivity, and dust, temperature swings, and general handling all chip away at accuracy over time.

Per Datacolor's own guidance on instrument calibration in professional color workflows, this drift is inevitable precisely because it's a hardware problem, not a software one, and it tends to happen gradually enough that an aging sensor will keep completing measurements and generating reports that look perfectly normal even as the underlying readings slowly move away from ground truth. An instrument that's drifted doesn't throw an error. It just quietly starts handing your calibration software slightly wrong numbers, which then get faithfully written into a monitor profile that's wrong from the moment it's created.

Most consumer colorimeters aren't designed for the owner to recalibrate at home; the practical fix is either a manufacturer recalibration service for higher-end units, where available, or periodic replacement on a multi-year cycle for budget sensors that don't offer one. If you own both a colorimeter and a reference spectrophotometer, the spectrophotometer's job, beyond calibrating displays directly, is often to periodically cross-check the colorimeter's readings against a known standard, catching drift in the cheaper, faster instrument before it quietly propagates into every monitor calibration you run with it. For a single-editor setup with one colorimeter, the more realistic guardrail is simply this: if your Delta E validation numbers start creeping upward across several sessions on a monitor that hasn't otherwise changed, don't assume the panel is failing before you've considered that the sensor reading it might be the thing that's actually drifted.

## How is calibrating for HDR grading in DaVinci Resolve different from SDR?

HDR calibration targets a much higher peak luminance, a wider color gamut, and a different transfer curve entirely, PQ or HLG instead of gamma, which means your SDR calibration numbers don't carry over at all.

Where SDR grading targets roughly 100 to 120 cd/m2, HDR grading in DaVinci Resolve typically targets a monitor capable of at least 1,000 cd/m2 peak brightness, with some reference displays and Apple's own XDR-class panels reaching 3,000 cd/m2 or higher. That's not a brighter version of the same target, it's a fundamentally different transfer function. PQ (Perceptual Quantization) and HLG (Hybrid Log-Gamma) encode brightness on a curve built to preserve detail across a much wider range than gamma 2.4 was ever designed to hold, and a colorimeter calibrating an HDR display needs to measure and validate against that curve specifically, not against a gamma target repurposed for a brighter screen.

There's a specific reference white value worth knowing here too. Per ITU-R BT.2408's own guidance for operational practices in HDR production, HDR content uses a diffuse reference white of 203 nits, roughly 58% of full PQ signal level, a deliberate scaling that maps SDR's familiar 100 cd/m2 peak white up to the equivalent point on an HDR curve. If you're grading a project that needs both an SDR and an HDR deliverable from one timeline, that 203-nit reference white is the anchor point both versions are built around.

Dolby Vision work adds a metadata layer on top of the display calibration itself. Per Dolby's own Color Grading Best Practices Guide, the Dolby Vision workflow requires you to tell the system which Mastering Display you calibrated for, a setting like "1000 nits, P3-D65, ST2084, full," which gets stored as metadata alongside your grade, and then to run separate Trim Passes for each additional target display, typically defaulting to a 100-nit, BT.709, BT.1886 SDR trim as one of several. Each trim pass is graded against a different calibrated reference, which is why HDR finishing setups often run two monitors, an HDR reference and an SDR reference, side by side rather than trying to judge both deliverables off one screen.

One practical note if you're planning Dolby Vision or HDR10+ delivery specifically: per Blackmagic's own DaVinci Resolve Studio product page, the metadata palettes for both formats are exclusive to the paid Studio tier. The underlying HDR color pipeline and monitor calibration process described here work identically in the free version, but the specific tools for authoring and trimming Dolby Vision or HDR10+ metadata do not.

| Calibration factor | SDR grading | HDR grading |
| --- | --- | --- |
| Peak luminance target | ~100 to 120 cd/m2 | 1,000 cd/m2 or higher |
| Transfer curve | Gamma 2.2 or 2.4 | PQ or HLG |
| Reference white | 100 cd/m2 | 203 nits (per ITU-R BT.2408) |
| Metadata/trim passes | Not applicable | Dolby Vision Mastering Display + Trim Passes |
| Studio-exclusive tooling | No | Dolby Vision/HDR10+ metadata palettes only |

## Do you need DaVinci Resolve Studio, a reference monitor, or CalMAN to calibrate properly?

No to all three for standard SDR delivery work. Calibration itself is a hardware and software process entirely separate from which version of DaVinci Resolve you're running, and a well-calibrated consumer monitor beats an uncalibrated professional one every time.

DaVinci Resolve's free version handles the Resolve side of this guide completely: the Color Management tab, Data Levels, Video Monitor LUT loading, and acting as a test pattern generator for calibration software like CalMAN are not gated behind Resolve Studio. What Studio adds, per Blackmagic's own product page, are things adjacent to calibration rather than part of it: the Neural Engine's AI tools, Dolby Vision and HDR10+ metadata palettes, and extra ResolveFX. If your project needs those specific HDR delivery formats, you'll need Studio for that piece. The calibration process itself doesn't care which tier you're on.

A dedicated reference monitor from Flanders Scientific, Sony, or a similar broadcast vendor buys you two things a good consumer display generally can't match: built-in hardware calibration that doesn't rely on your GPU or operating system at all, and a panel engineered specifically for color accuracy across its entire life rather than for contrast ratio marketing numbers. That's a real advantage for a facility doing client-facing broadcast or streaming delivery work every day. It's not a requirement for a freelance editor or YouTube creator producing accurate, deliverable-ready color on a well-chosen consumer monitor that's actually been calibrated.

CalMAN specifically is the professional calibration software standard, and it's genuinely worth the cost if you're calibrating multiple reference displays regularly or need its automated validation reporting for client sign-off. For a single editor calibrating one or two personal monitors, DisplayCAL, free and open source, and per Lowepost's own coverage, widely considered more accurate than many bundled manufacturer tools, gets you to the same D65, gamma, and luminance targets without the license cost.

**Neither a Resolve Studio license, a five-figure reference monitor, nor a CalMAN subscription is what separates an accurately calibrated setup from an inaccurate one. A cheap colorimeter used correctly is.** The gear tier changes your ceiling for HDR peak brightness and wide-gamut accuracy. It doesn't change whether basic SDR calibration was done correctly in the first place.

## Can you color grade professionally on a laptop screen?

Yes, for rough color, editorial decisions, and personal projects, but not as the final reference for a client deliverable, even calibrated.

A laptop's built-in display has three structural disadvantages a colorimeter can measure and partially correct, but can't eliminate. First, a narrower native color gamut than most dedicated grading monitors, which means some colors your final deliverable needs to represent simply fall outside what the panel can physically display, calibrated or not. Second, viewing-angle color and contrast shift, since laptop panels are rarely built with the wide, consistent viewing cone a professional monitor prioritizes, so tilting the lid a few degrees during a long session measurably changes what you're seeing. Third, a chassis and lid design that isn't built around a stable, uniform backlight the way a reference display is, which can produce visible brightness and color unevenness across the panel that no calibration profile fully corrects, since ICC profiles and 3D LUTs correct a display's overall response curve, not physical panel non-uniformity.

That said, calibrating a laptop screen is still worth doing, and it's a real improvement over skipping calibration entirely. It gets you a documented, known baseline instead of an unknown one, and for editorial work, rough color passes, and personal YouTube content where the final viewer is watching on an equally uncalibrated phone or laptop anyway, that baseline is genuinely useful. Treat it as your working reference for everything up to the point where a client, a broadcaster, or a streaming platform's technical spec is actually judging color accuracy, and bring in an external, calibrated reference display for that final decision.

If you only own a laptop and a client project genuinely needs accurate color, the cheapest fix isn't a full reference monitor, it's a mid-range external display plus a colorimeter, run through a clean signal path rather than the laptop's own screen. That combination, calibrated properly, will outperform an uncalibrated laptop lid by a wide enough margin that it's worth the modest cost before you take on paid color work.

## Do you need to calibrate every monitor in a multi-display editing setup?

No. You need one monitor calibrated properly, the one you're actually making color decisions on, and the rest of your displays just need to be reasonably close to it so your eyes aren't constantly readapting between two very different white points.

A typical multi-monitor edit bay has a clear split in roles. One screen shows the grading viewer, the image you're judging. The others show scopes, the node graph, bins, and other UI panels. Only the first one needs the full colorimeter, D65, gamma, dim-room treatment this guide walks through. Scopes and UI panels aren't color judgments, they're instruments and controls, and a slight color shift on that screen doesn't corrupt your grade the way the same shift on your primary viewer would.

That doesn't mean your secondary displays can be ignored completely. If your UI monitor runs noticeably warmer or cooler than your calibrated grading display, your eyes spend the whole session subtly readapting every time your gaze moves between them, which is the same chromatic adaptation problem covered earlier in this guide, just introduced by your own desk setup instead of a drifting panel. A cheap, uncalibrated but reasonably neutral secondary monitor, or a fast default calibration pass with the same colorimeter you already own, closes most of that gap without needing a second full professional workflow.

If budget forces a choice between calibrating one monitor well or two monitors poorly, calibrate the one showing the actual image. A perfectly calibrated waveform monitor tells you nothing if the picture you're grading against is still lying to you.

## A worked example: calibrating a single budget monitor for client delivery

Say you're a solo editor with one external monitor, delivering YouTube and social content graded in DaVinci Resolve's free version, and you've never calibrated anything before.

1. **Buy an entry-level colorimeter.** A Datacolor SpyderX Pro, at $169.99 per PremiumBeat's own reporting, covers standard SDR work on a typical consumer monitor.
2. **Install DisplayCAL**, free and open source, rather than the manufacturer's bundled software, which per Lowepost's coverage tends to be less accurate for this exact use case.
3. **Warm up the monitor for 30 minutes**, reset it to factory defaults, and disable Auto-Brightness and any Dynamic Contrast setting in its OSD menu. If you're on a Mac, also turn off True Tone and Night Shift, and on Windows, turn off Night Light, before you start.
4. **Darken the room** and, if your budget allows, add a small D65 LED bias light strip behind the monitor.
5. **Run DisplayCAL targeting D65, gamma 2.2** (since a typical home office is brighter than a dim grading suite), and 120 cd/m2 luminance, saving the result as your system ICC profile.
6. **In DaVinci Resolve's Color Management tab**, set your Output Color Space to Rec.709 Gamma 2.4 for delivery, but confirm with your platform's actual spec, since gamma 2.2 output paired with gamma 2.2 monitor calibration is the more consistent match for a room that bright.
7. **Recalibrate monthly**, and recheck immediately if a delivered grade comes back from a client looking different than you remember approving.

Total cost here sits under $200, and it closes the single largest gap between an amateur and a professional monitoring setup: knowing, with a number, that your screen is telling you the truth.

## A worked example: calibrating a broadcast-spec suite with a reference monitor and I/O device

Now the higher-stakes version. Say you're building a small color suite for client-facing broadcast and streaming delivery, running DaVinci Resolve Studio with a Flanders Scientific reference monitor and a Blackmagic UltraStudio I/O device.

1. **Connect the reference monitor through the UltraStudio**, not through the computer's own GPU output, so the signal path bypasses your operating system's color handling entirely.
2. **Set up the room properly**: dark walls at a neutral Munsell N5 gray in your sightline, D65 bias lighting at roughly 5 cd/m2 behind the monitor, and no uncontrolled ambient light source.
3. **Use CalMAN with DaVinci Resolve as the test pattern generator**, per Flanders Scientific's own calibration documentation for its monitor line, sending calibration patches from Resolve through the UltraStudio to the reference display while a spectrophotometer reads them back.
4. **Target D65, gamma 2.4 (BT.1886), and 100 cd/m2** for your primary SDR reference, since this is a controlled, dim grading environment rather than a bright office.
5. **Load the resulting calibration directly into the reference monitor's own hardware**, or into a 3D LUT slot the monitor accepts natively, rather than relying on a system ICC profile.
6. **In DaVinci Resolve's Color Management tab**, confirm Output Color Space matches exactly: Rec.709 Gamma 2.4, Data Levels set explicitly rather than Auto.
7. **If HDR delivery is part of the scope**, add a second calibrated HDR reference display targeting 1,000 cd/m2 or higher with the appropriate PQ or HLG curve, and set up Dolby Vision's Mastering Display metadata to match, available in Resolve Studio.
8. **Send the spectrophotometer back for periodic recertification** on whatever schedule the manufacturer recommends, and cross-check the primary colorimeter against it, since mission-critical delivery work is exactly where undetected sensor drift does the most damage.
9. **Recalibrate on a stricter schedule**, weekly rather than monthly, given the mission-critical delivery work running through the suite.

The gear list here runs well past what a freelance editor needs, and that's the point. This setup buys accuracy margin and metadata capability a single-monitor freelance rig doesn't need, but it's still built on the exact same three numbers, D65, a gamma or transfer curve, and a luminance target, the budget example above uses.

## What goes wrong when calibration and Resolve's color management don't match?

Most of the "my calibration didn't work" reports actually trace back to one of eight specific mismatches, not a failed calibration run.

**Leaving Data Levels on Auto in DaVinci Resolve's Color Management tab.** Per Hollyland's own guide, Auto is unreliable specifically because it's guessing at your signal path rather than reading it directly, and a wrong guess here crushes or lifts your blacks in a way that looks exactly like a display calibration problem. Set it explicitly to match your monitor's actual configuration.

**Running a calibration session with dynamic display features still enabled.** Auto-Brightness, Eco Mode, and Dynamic Contrast all actively change your monitor's output in response to content or ambient light, which means a calibration run against a screen that's still adjusting itself produces a profile that's already partially wrong the moment room conditions change even slightly.

**Skipping the 30-minute warmup**, particularly on OLED and older LCD panels, which per Hollyland's coverage measurably shift color as they heat from a cold start, baking a temporary drift into a profile meant to last a month or more.

**A mismatched gamma between your monitor's calibration target and Resolve's Output Color Space.** A monitor calibrated to gamma 2.4 paired with a Resolve project outputting gamma 2.2, or the reverse, produces a visible contrast and brightness mismatch that reads exactly like a bad calibration, even though the hardware calibration itself was done correctly.

**Enabling "Use Mac display color profiles for viewers" without testing the actual result.** Per the Blackmagic Forum thread on this exact preference, the setting doesn't always produce the expected result, and the conversion it applies isn't guaranteed accurate for every monitor and profile combination. Test against a known reference, don't assume the checkbox alone fixed the mismatch.

**Leaving True Tone, Night Shift, or Night Light active during a session.** All three sit below the application layer, on Mac or on Windows, and none of them can be detected or compensated for from inside Resolve or your calibration software, which means a calibration you trust completely can still be quietly wrong the moment one of these features reacts to the time of day or the light in your room.

**Ignoring the QuickTime/Rec.709-A gamma tag mismatch on export.** As covered earlier, a standard gamma 2.4 export can read washed out in QuickTime Player or after a YouTube upload on a Mac, purely because of how Apple's frameworks read the file's metadata tag, a problem the Rec.709-A output setting fixes without touching your grade at all.

**Switching monitors or signal paths mid-project without recalibrating for the new path.** A calibration profile built for your monitor's HDMI input doesn't automatically carry over if you switch to a DisplayPort connection or route through a different I/O device, since the physical signal path itself can introduce its own handling differences.

**One sentence covers most of this section: your monitor being correctly calibrated and DaVinci Resolve's own settings being correctly configured to match it are two separate facts, and a failure in either one produces the exact same symptom on screen.** Work through the checklist in order rather than assuming a color problem in Resolve is automatically a hardware calibration failure, or the reverse. If a desaturated, flattened look specifically is what you're chasing rather than a general color mismatch, it's also worth ruling out [Color Space Transform's own tone mapping and gamut mapping settings](https://tryuncle.com/learn/davinci-resolve/why-does-color-space-transform-desaturate-my-footage-in-davinci-resolve), which desaturate footage on purpose under certain settings and can look identical to a calibration problem at a glance.

## Which calibration setup should you actually use?

Match your setup to what's actually downstream of your grade, not to what sounds the most professional.

| Your situation | Recommended setup |
| --- | --- |
| Solo editor, YouTube/social delivery, tight budget | Entry colorimeter (SpyderX Pro), DisplayCAL, one calibrated consumer monitor, D65/gamma 2.2/120 cd/m2 |
| Freelance editor delivering to clients regularly | Mid-range colorimeter, a dedicated external monitor (not a laptop lid), monthly recalibration |
| Multiple monitors on one desk | Full calibration on the grading viewer only, a rough match pass on secondary UI/scope displays |
| HDR or wide-gamut display work | HL-series colorimeter (Calibrite Display Pro HL or Plus HL), targeting PQ/HLG and 1,000+ cd/m2 |
| Broadcast/streaming delivery, mission-critical work | Reference monitor (Flanders Scientific or equivalent), UltraStudio/DeckLink I/O, CalMAN, weekly recalibration |
| Dolby Vision or HDR10+ metadata delivery | DaVinci Resolve Studio, HDR reference display, Mastering Display metadata plus Trim Passes |

Choose the freelance or solo-editor path if no one downstream of you is checking your color against a documented technical spec. Choose the broadcast-spec path if a streaming platform, a broadcaster, or a studio has a published delivery requirement waiting for your file. Both paths rest on the exact same three numbers, D65, a matched gamma or transfer curve, and a documented luminance target, verified with a hardware sensor instead of your own adapting eyes.

## Where do you go from here?

Monitor calibration is one of the questions that comes up constantly around Resolve, right alongside "why does my export look different from my preview." It's rarely a Resolve bug. It's almost always an uncalibrated screen, a Resolve setting that doesn't match a calibration that was done correctly, an operating-system feature quietly overriding both, or a room fighting all three at once.

[TryUncle](https://tryuncle.com/) is the on-screen assistant for DaVinci Resolve on macOS. Ask in plain words, and Uncle points at the exact control on your screen. If you've just finished calibrating your monitor and you're staring at Resolve's Color Management tab trying to remember whether Data Levels needs to be Video or Full for your specific setup, that's exactly the kind of question Uncle answers live, pointed at your actual project, instead of sending you back through a settings menu built for a different configuration than yours.

Buy the colorimeter before you buy anything else on this list. It's the cheapest item here and the one every other decision in this guide depends on. Set your D65, gamma, and luminance targets deliberately, match Resolve's Color Management tab to whatever you land on, turn off True Tone, Night Shift, or Night Light for the session, and put a recurring reminder on your calendar to check it again next month. Everything else, the reference monitor, the I/O device, the CalMAN license, is a matter of how much accuracy margin your work actually needs, not whether calibration itself is worth doing.

## FAQ

### Why does my DaVinci Resolve grade look different on another screen?

Almost always because your grading monitor was never calibrated to a known target, or because DaVinci Resolve's output color space doesn't match what that monitor was calibrated to. Resolve sends pixel values straight to your GPU without checking your operating system's display profile, so an uncalibrated screen and a mismatched Color Management setting can both push your grade off target at the same time, in different directions, without either one throwing an error.

### Do I need an expensive colorimeter to calibrate a monitor for DaVinci Resolve?

No. A budget colorimeter like a Datacolor SpyderX Pro, priced at $169.99 according to PremiumBeat's own testing, will get a standard SDR monitor to a usable D65, gamma 2.4 target for most freelance and YouTube work. You only need a higher-end spectrophotometer or an HL-series colorimeter, built to measure past 1000 cd/m2, once you're grading HDR or a wide-gamut OLED panel where cheaper sensors lose accuracy.

### What gamma and white point should I use for color grading in DaVinci Resolve?

D65 (6500K) for white point in essentially every case. For gamma, target 2.4 (BT.1886) in a dim, controlled grading room, since that's the broadcast and cinema delivery standard, or 2.2 if you're working in a brighter room or delivering exclusively to web and sRGB-referenced displays. Whichever you pick, set the identical value in DaVinci Resolve's Color Management tab, since a monitor calibrated to 2.4 paired with a Resolve project set to 2.2 will look wrong in a way neither setting alone explains.

### Can I calibrate a laptop screen for color grading in DaVinci Resolve?

You can run a colorimeter on a laptop screen and it will measurably improve consistency, but it won't fix the panel's real limits: a narrower color gamut than a real grading display, viewing-angle color shift, and a chassis or lid that can't hold true D65 without an ICC profile fighting the panel's native white point. Treat a calibrated laptop screen as good enough for editing and rough color, not as the final reference for a paying client's deliverable.

### How often should I recalibrate my monitor for DaVinci Resolve?

Monthly is the general floor professional colorists work to, since panels drift as they age and as backlights degrade. OLED and older LCD panels drift faster and are worth checking more often, and color grading facilities running mission-critical delivery work often recalibrate weekly. If a shot that graded clean last month suddenly needs correction it didn't need before, check calibration before you assume the footage or your eyes changed.

### Why does DaVinci Resolve look different from QuickTime Player or a web browser on the same Mac?

Because Resolve, by default, doesn't reference your Mac's ColorSync display profile the way QuickTime Player and browsers do, so the same pixel values get displayed two different ways on the same screen. Turning on "Use Mac display color profiles for viewers" in Resolve's preferences closes part of that gap, and setting your Deliver page's gamma tag to Rec.709-A instead of the standard 1-2-1 tag fixes the specific washed-out look Apple's own frameworks introduce when they misread a 2.4-gamma QuickTime file.

### Is there an app that helps you while you're actually calibrating and setting up DaVinci Resolve?

Yes. TryUncle watches your actual Resolve window on macOS and points at the exact setting, whether that's the Color Management tab, the Data Levels dropdown, or the Deliver page's gamma tag, instead of making you match this guide's screenshots to your own screen. It's a paid subscription at founder pricing, and it won't run your calibration software for you, but it will find the Resolve setting your calibration depends on.

## Sources

- [How to Calibrate Your Monitor for DaVinci Resolve: The Colorist's Guide to Accuracy (Hollyland)](https://www.hollyland.com/blog/tips/calibrate-your-monitor-for-davinci-resolve)
- [Monitor calibration in DaVinci Resolve (Lowepost Insights)](https://lowepost.com/insider/insights/monitor-calibration-in-davinci-resolve-r51/)
- [The Color Grading Environment and Ideal Lume Bias Lights, by Steve Hullfish (ProVideo Coalition)](https://www.provideocoalition.com/the-color-grading-environment-and-ideal-lume-bias-lights/)
- [Why You Should Drop Everything and Calibrate Your Monitors Now (PremiumBeat)](https://www.premiumbeat.com/blog/calibrate-monitors-for-color-accuracy/)
- [Use a Cheat Sheet for DaVinci Resolve Color Management Setup (Frame.io Insider)](https://blog.frame.io/2023/12/04/color-management-cheat-sheet-davinci-resolve/)
- [Blackmagic Forum: Resolve, ColorSync, and "Use Mac Display Color Profile..."](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=46464)
- [Addressing DaVinci Resolve's color shift, by Rodrigo Polo](https://rodrigopolo.com/2021/07/26/addressing-davinci-resolves-color-shift/)
- [Blackmagic Forum: A new colorspace/gamma option named Rec.709-A](https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=114047)
- [Report ITU-R BT.2408-5: Guidance for operational practices in HDR television production](https://www.itu.int/dms_pub/itu-r/opb/rep/R-REP-BT.2408-5-2022-PDF-E.pdf)
- [DaVinci Resolve 21 New Features Guide (Blackmagic Design, PDF)](https://documents.blackmagicdesign.com/SupportNotes/DaVinci_Resolve_21_New_Features_Guide.pdf?_v=1776322810000)
- [FSI Calibration Guide for AM/BM/CM/DM Series Monitors Using CalMAN with DaVinci Resolve (Flanders Scientific, PDF)](https://www.flandersscientific.com/calibration/CalMAN/FSI-I1-CalMAN-Resolve.pdf)
- [DaVinci Resolve Studio product page (Blackmagic Design)](https://www.blackmagicdesign.com/products/davinciresolve/studio)
- [Dolby Vision Color Grading Best Practices Guide, Version 4.0 (Dolby Laboratories, PDF)](https://professional.dolby.com/siteassets/pdfs/dolby_vision_best-practices_colorgrading_v4.pdf)
- [i1Display Pro (X-Rite Monitor Calibration Device)](https://www.xrite.com/categories/calibration-profiling/i1display-pro)
- [Color Managed Workflow in Resolve: ACES (Netflix Partner Help Center)](https://partnerhelp.netflixstudios.com/hc/en-us/articles/360002088888-Color-Managed-Workflow-in-Resolve-ACES)
- [Calibrite Display Plus HL Colorimeter (B&H Photo Video product listing)](https://www.bhphotovideo.com/c/product/1770372-REG/calibrite_ccdis3plhl_display_plus_hl.html)
- [DaVinci Resolve 21 final release (Newsshooter)](https://www.newsshooter.com/2026/06/02/davinci-resolve-21-final-release/)
- [Calibrate your Mac display (Apple Support)](https://support.apple.com/guide/mac-help/calibrate-your-display-mchlp1109/mac)
- [Use True Tone on Mac (Apple Support)](https://support.apple.com/en-us/102147)
- [What Is Delta E? dE Values and Monitors Explained (Tom's Hardware)](https://www.tomshardware.com/reviews/delta-e-glossary-definition-color-monitors,6199.html)
- [Instrument Calibration in Global Color Workflows (Datacolor)](https://www.datacolor.com/business-solutions/blog/instrument-calibration-global-color-workflows/)
- [Windows hardware display color calibration pipeline (Microsoft Learn)](https://learn.microsoft.com/en-us/windows/win32/wcs/display-calibration-mhc)
- [Change display brightness and color in Windows (Microsoft Support)](https://support.microsoft.com/en-us/windows/change-display-brightness-and-color-in-windows-3f67a2f2-5c65-ceca-778b-5858fc007041)