You finish the grade. Every shadow sits where you put it, skin tones look right, the highlights roll off exactly the way you wanted. You export, you upload, you press play — and the picture is flat and washed out. The blacks are milky, the contrast is gone, and it looks nothing like the thing you spent hours building.
Watch the video: “Fix Gamma Shift in DaVinci Resolve — And Verify It Worked” the complete DaVinci Resolve setup, plus the test pattern that tells you in two minutes whether it actually worked.
This is gamma shift. It is not YouTube’s fault, and it is not a bug in DaVinci Resolve. It is a handful of settings, in two different places, that most people never touch.
Below is everything you need to configure in Resolve, and then everything worth checking on the computer itself. Work through it once and you will not have to think about it again.
What Gamma Shift Actually Is
A video file carries two things: the picture data, and metadata that tells the player how to interpret it. That metadata includes the colour space and the transfer function — in plain terms, how bright a given pixel value is supposed to look.
When those tags are missing, wrong, or ignored, the player makes an assumption. If the player’s assumption differs from the one Resolve used while you were grading, every tone in the image lands in the wrong place. Nothing has been destroyed; the numbers are intact. They are simply being read against the wrong ruler.
That is why the fix is not “add contrast until it looks right”. The fix is to make sure the file says what it means, and that your monitor was telling you the truth in the first place.
Part 1: DaVinci Resolve Settings
Project Settings → Color Management
Open Project Settings and go to the Color Management tab.
- Color Science: DaVinci YRGB
- Timeline Color Space: Rec.709 Gamma 2.4
- Output Color Space: Rec.709 Gamma 2.4
Gamma 2.4 follows BT.1886, the reference display standard used for broadcast and mastering. It is the target you want for anything that will be watched on a normal screen.
Project Settings → Master Settings
Switch to Master Settings and match the project to what your camera actually recorded.
- Timeline Resolution: match your camera, for example 4K
- Timeline Frame Rate: match your camera, for example 30
- Playback Frame Rate: the same
- Pixel Aspect Ratio: Square
Set the frame rate before you import anything. Resolve locks the timeline frame rate as soon as there is media in the project. Get it wrong and your only real option is to start a new project.
Deliver Page
With the grade finished, move to the Deliver page. YouTube re-encodes everything you upload, so your job is to hand it the cleanest possible master. Start from the H.265 Master preset and adjust a few parameters.
- Format: MP4 or MOV
- Codec: H.265
- Encoder: NVIDIA / NVENC, or Native if you have no NVIDIA card
- Resolution and Frame Rate: match the timeline
- Bitrate: around 20,000 Kb/s for dynamic 4K
- Bitrate: around 12,000 Kb/s for talking heads and podcasts
H.265 holds more detail per bit than H.264, so you keep quality at a smaller file size. Since YouTube is going to transcode the file anyway, a cleaner source means a cleaner result at the other end.
Deliver → Advanced Settings
This is the part that actually prevents the gamma shift, and it is the part most people skip because it sits behind a collapsed panel.
- Pixel Aspect Ratio: Square
- Data Levels: Video
- Color Space Tag: Rec.709
- Gamma Tag: Rec.709
Those last two lines are the whole point. They are what tells every player downstream how to read the file. Without them, the player guesses.
When everything is set, save the whole thing as a preset from the three-dot menu on the right. You will never have to configure it again.
Part 2: Verify It, Don’t Trust It
Settings you have not tested are settings you are hoping about. Build a test pattern once and you will know for certain.
- Go to Effects → Generators and drag 10 Step Grayscale onto the timeline.
- Drag an Adjustment Clip onto the track above it.
- On the Color page, select the Adjustment Clip. Using Lift, bring the shadows down until the difference between black and the darkest grey is only just visible. Using Gain, bring the highlights up until the difference between white and the brightest grey is only just visible.
- Place any photo or video on a layer above, offset so you can see both the image and the grey bars.
- Extend it to a few seconds, render with your new preset, and upload it to YouTube as unlisted.
Once it has finished processing, open it and compare it side by side with the Resolve viewer. You are looking for four things:
- White stays white on YouTube. It must not turn grey.
- The difference between white and the brightest grey is barely visible — but it is there.
- Black stays just as black.
- The difference between black and the darkest grey is barely visible — but it is there.
Check it on a phone too. You are not looking for an exact match there, only making sure the shadows have not disappeared entirely.
Part 3: The Computer and the Display
Correct export settings will not save you if the monitor lied to you while you were grading. Nothing between your project and your eyes should alter the image.
Your monitor should be showing Rec.709 / sRGB, gamma 2.2–2.4, D65 white point, SDR — with every “enhancement” switched off. Anything that adapts, boosts or tone-maps the picture changes what you see, but not what you export. That gap is where bad grades come from.
macOS
- High Dynamic Range (System Settings → Displays) — off
- Preset / Reference Mode on XDR displays — HDTV Video (BT.709 – BT.1886)
- True Tone — off
- Night Shift — off
- Automatically adjust brightness — off
- Low Power Mode (System Settings → Battery) — off, it dims the panel
- Screen dimming on battery — off
- Display profile — your own calibration, or a known Rec.709 / sRGB profile. Not the wide-gamut P3 default.
The big macOS trap: MacBook Pro and Pro Display XDR panels default to an HDR-capable, P3 wide-gamut mode. Rec.709 content shown through P3 primaries looks noticeably more saturated than it really is. If your reds and skin tones look great on the Mac and wrong everywhere else, this is why.
In Resolve, also check Preferences → System → Decode Options → Use Mac Display Color Profiles for Viewers. Whether it is on or off changes the viewer image. Pick one, then confirm it with the test-pattern upload above rather than assuming.
Windows
- Use HDR and Auto HDR (Settings → System → Display → HDR) — off
- Night light — off
- Adaptive / auto brightness — off
- Content adaptive brightness (CABC) — off
- Battery saver dimming — off
- Colour profile — your own calibration, or the sRGB / factory profile. Never a random ICC downloaded from a forum.
Close or uninstall anything that sits on top of the display: f.lux, Iris, Twinkle Tray, monitor-vendor “gaming” utilities, RGB lighting suites that touch display gamma.
GPU Driver Settings
In the NVIDIA Control Panel:
- Output dynamic range — Full for a monitor over DisplayPort
- Output colour format — RGB
- Output colour depth — 8 or 10 bpc, matching your panel
- Digital vibrance — 50%, neutral
- Adjust video colour settings — With the video player settings
- RTX Video Enhancement, RTX HDR, Video Super Resolution — off
- Image Scaling and sharpening — off
Mismatched range is the number one Windows trap. GPU on Limited with the monitor on Full gives you washed-out, milky blacks. GPU on Full with the monitor on Limited crushes your shadows and clips your highlights. Either combination is fine — as long as both ends agree.
On AMD Adrenalin, turn off Custom Color, Vari-Bright, Color Temperature Control, Video Enhancement / Fluid Motion, and any HDR toggle. In the Intel Graphics Command Center, turn off video colour enhancement, film mode detection and skin tone enhancement, and set Input Range to match your monitor.
The Monitor Itself
This is where most people lose the picture. The operating system is clean, but the panel is still quietly “improving” things.
- Picture preset — Standard, sRGB or Rec.709. Never Movie, Cinema, Vivid, Game, HDR or Reader.
- HDR / HDR Effect / HDR emulation — off
- Dynamic Contrast (DCR / Smart Contrast / ACR) — off
- Eco mode and ambient light sensor — off
- Black Equalizer / Black Stabilizer / Shadow Boost — off, or neutral
- Local dimming — off, unless it is a proper full-array reference display
- Blue light filter / Low Blue Light / Reader mode — off
- Sharpness — neutral. Many panels ship over-sharpened.
- Colour temperature — 6500K, Warm or sRGB. The factory default is often 9300K, which is far too blue.
- Gamma — 2.2 for a normally lit room, 2.4 for a properly dark one
- HDMI Black Level / Input Range — must match your GPU output range
- Overscan / Just Scan / 1:1 pixel mapping — make sure the full image is shown, not cropped
- Motion smoothing, noise reduction, MPEG NR, dynamic colour — off
Your timeline stays at Rec.709 Gamma 2.4 regardless of which monitor gamma you choose. The monitor setting is compensating for how bright your room is, not changing your delivery target.
If you are using a TV as a monitor: label the HDMI input as PC or Graphics, which bypasses most of the internal processing. Turn on Game Mode if that is the only way to disable the processing chain, and switch off motion interpolation, dynamic tone mapping, AI upscaling and every “intelligent picture” mode you can find.
Calibration
Ideally, every display you work on is calibrated with a hardware probe — a Calibrite, an X-Rite i1Display, a SpyderX or similar — to Rec.709, gamma 2.4, D65, around 100 nits. Adjusting by eye, or “calibrating” in software with no probe attached, does not count.
- Calibrate every display you grade on, to the same target.
- Recalibrate every month or two. Panels drift, OLED especially.
- A profile generated by your own calibration is good. A random ICC downloaded for “your” monitor model is not — panels vary from unit to unit, even within one production run.
- If you use a calibration LUT rather than an ICC profile, load it in Resolve under Color Management → Lookup Tables → Video Monitor Lookup Table, and do not also apply it at the operating system level. One or the other, never both.
Multiple Displays and the Room
- Every display you grade on uses the same preset, gamma, colour temperature and brightness.
- Grade on one display, always the same one. Use the second only for the interface.
- Watch out for a laptop’s internal panel running HDR/P3 next to an external SDR/Rec.709 monitor. Dragging the viewer between them changes the image.
- Keep room lighting neutral and consistent, with no sunlight moving across the screen during a session.
- No strongly coloured walls or lighting behind or beside the monitor. A neutral D65 bias light behind the screen helps, but is optional.
- Screen brightness around 100–120 nits for a dim room. Full brightness on a modern panel is far too bright for grading.
- Nothing reflective in the screen — including you, in a bright shirt.
Before You Judge the Upload
- Disable any browser extension that touches colour: Dark Reader, Turn Off the Lights, Midnight Lizard, any dark-mode filter.
- Check in Chrome. It is what most of your audience is using, so it is the view you want to match.
- If your results still look inconsistent, check
chrome://flags/#force-color-profileand set it to sRGB. - Let YouTube finish processing before you judge anything. Early playback may serve a lower-quality transcode.
- Set playback quality manually to the highest available, and compare full-screen against the Resolve viewer.
The Two-Minute Version
If you are up against a deadline and can only check five things:
- HDR off — in the operating system and in the monitor menu
- Monitor preset set to Standard, sRGB or Rec.709
- Dynamic contrast, eco mode and adaptive brightness all off
- GPU output range matching monitor input range
- Night Shift, Night Light and blue light filters off
And in Resolve: Data Levels set to Video, both tags set to Rec.709.
Re-check This When…
- You update your operating system or graphics drivers.
- You connect a new monitor, or swap a cable.
- You plug into a different port. HDMI and DisplayPort often behave differently.
- Someone else has used your machine.
- Something “just looks different” and you cannot say why. It usually is different.
Once your test pattern survives the round trip to YouTube and back, you know your pipeline is honest. From that point on, what you see on the Color page is what your audience gets — and you can go back to worrying about the grade itself instead of the plumbing.