novideo_srgb vs DisplayCAL: Which sRGB Clamp Should You Use?
Your wide-gamut monitor makes SDR content look radioactive, and you’ve heard there are two fixes: the tiny novideo_srgb utility or a DisplayCAL 3D LUT. They solve the same problem in very different ways — and you must never use both at once. Here’s how to pick.
The problem both tools solve
A wide-gamut panel (DCI-P3, Adobe RGB) shows sRGB content oversaturated because nothing tells it to restrain itself — the monitor just stretches the small sRGB signal across its big native gamut. An sRGB clamp remaps the output so sRGB content looks as the creator intended. For background on the DisplayCAL approach, see our sRGB clamp guide.
Option 1: novideo_srgb
novideo_srgb is a small, free, open-source utility for NVIDIA GPUs that applies an sRGB gamut clamp at the driver level. Its appeal is simplicity: run it, and SDR content on a wide-gamut screen calms down immediately, with no measurement hardware and no profiling session.
- Pros: instant, free, no colorimeter needed, tiny footprint.
Option 2: DisplayCAL 3D LUT
DisplayCAL takes the longer road: measure your actual panel with a colorimeter, then build a 3D LUT that clamps the gamut to sRGB and corrects grayscale, gamma, and white point at the same time. Loaded through a tool like dwm_lut, the result is a calibrated sRGB emulation of your specific unit — measurably more accurate than a generic clamp.
- Pros: corrects the whole chain (gamut + grayscale + gamma), verified accuracy via measurement reports, works on any GPU brand.
Which one should you use?
| Your situation | Pick |
|---|---|
| NVIDIA GPU, no colorimeter, want it fixed today | novideo_srgb |
| AMD/Intel GPU, or any non-NVIDIA setup | DisplayCAL (novideo_srgb is NVIDIA-only) |
| Photo/video work where accuracy is verified, not assumed | DisplayCAL 3D LUT |
| You own a colorimeter already | DisplayCAL — you paid for the hardware, use it |
Warning: Do not run both at the same time. Stacking novideo_srgb’s clamp on top of a DisplayCAL sRGB 3D LUT applies the gamut compression twice, which desaturates and distorts colors. Pick one method, disable or uninstall the other, and verify the result.
If you go the DisplayCAL route, the step-by-step is in our sRGB clamp guide, and if you don’t have a sensor yet, our colorimeter buying guide covers the current options.
Note: HDR content is a separate topic: an sRGB clamp is for SDR content on wide-gamut SDR pipelines. If you’re calibrating for HDR, read our HDR calibration guide instead — different targets, different workflow.
Frequently Asked Questions
Does novideo_srgb work on AMD or Intel graphics?
No. novideo_srgb is built specifically around NVIDIA driver functionality and does not work on AMD or Intel GPUs. If you don’t have an NVIDIA card, the DisplayCAL 3D LUT route is the way to clamp to sRGB.
Is novideo_srgb as accurate as a DisplayCAL 3D LUT?
No. novideo_srgb applies a generic gamut clamp; it cannot fix your panel’s individual grayscale errors, gamma tracking, or white point. A DisplayCAL 3D LUT is built from measurements of your specific unit and corrects all of those, which is why it takes longer and needs a colorimeter.
Can I use novideo_srgb together with my ICC profile?
That combination is exactly what you should avoid stacking blindly. An ICC profile and a driver-level clamp both try to define the output transform — running both can double-apply corrections. Use one color management path at a time and check the result visually against reference images.
I switched methods and colors look wrong now. What happened?
Almost certainly a leftover: the old clamp is still active. If you moved from novideo_srgb to DisplayCAL, make sure novideo_srgb is fully disabled or uninstalled. If you moved the other way, remove the 3D LUT from your LUT loader and reload a plain profile. Then re-verify.