HDR vs. SDR: The Next Generation of Picture Quality

Why does HDR video look washed out on a regular display? And what's the relationship between HDR10, HLG, and Dolby Vision?

The first time you play an HDR video on a standard monitor, the picture looks washed out—pale colors, flat contrast, as if a haze has settled over the image. That's not a broken video file; it's the hallmark of missing tone mapping. HDR (High Dynamic Range) is the biggest leap in video quality since resolution increased—but it brings more than "brighter images." In fact, the jump from SDR to HDR can be more visually striking than the jump from 1080p to 4K. But understanding its technical costs and compatibility challenges is also more complex.

Dynamic Range: The Luminance Leap from SDR to HDR

Dynamic range in video refers to the ratio between the brightest and darkest parts of an image, typically measured in f-stops or nits (cd/m²).

SDR's standard peak brightness is 100 nits (cd/m²), a standard inherited from CRT monitors. HDR targets range from 1000 nits (mid-range HDR TVs) to 4000 nits (professional reference monitors) and even 10000 nits (the upper limit defined by the standard).

100 nits to 1000 nits is not a 10× sensation—human brightness perception is logarithmic. A 1000-nit image is physically 10× brighter than 100 nits, but it feels only about twice as bright to the eye. The real visual impact comes from brighter highlights combined with deeper blacks—that's the true meaning of "high dynamic range."

Why 8-Bit Isn't Enough

SDR's 100 nits encoded in 8-bit (256 steps) appears reasonably smooth to perception. But spread those same 256 steps across 0-1000 nits, and the gap between adjacent gray levels becomes visibly large—which is why HDR mandates 10-bit. Higher luminance and wider gamuts require denser sampling to avoid banding.

HDR's Two Keys: EOTF and Metadata

HDR isn't just "brighter"—it redefines how luminance values map to digital signals. This mapping is defined by the Electro-Optical Transfer Function (EOTF).

The Gamma Curve (SDR)

SDR uses a Gamma curve (approximately 2.2), originally designed to match CRT monitor physics and the human eye's logarithmic perception. Gamma allocates more code values to shadows (where the eye is sensitive to small changes) and fewer to highlights.

PQ (Perceptual Quantizer)

HDR's ST.2084 (PQ) curve is fundamentally different from Gamma. It was designed based on experiments measuring the human eye's just-noticeable difference for luminance—code values are allocated proportional to the smallest brightness difference the eye can perceive. This means the PQ curve allocates significant code values to highlights as well, because HDR's luminance range far exceeds SDR's.

The PQ curve supports a luminance range from 0.0001 nits to 10000 nits and is the foundation of HDR10 and Dolby Vision.

HLG (Hybrid Log-Gamma)

HLG, developed by BBC and NHK, takes a fundamentally different approach from PQ: it is backward-compatible with SDR displays. An HLG signal displays as normal SDR on an SDR screen (slightly compressed contrast but not washed out), while showing full HDR on an HDR display. This makes HLG ideal for live broadcasts and television distribution—no extra metadata or dual-track delivery required.

HDR Metadata

Beyond the video stream itself, HDR video carries metadata describing "how this video should be displayed":

• Static metadata (HDR10): a single set of luminance parameters (max/min brightness, gamut boundaries) for the entire video. Simple and reliable, but brightness differences between scenes are averaged.
• Dynamic metadata (HDR10+, Dolby Vision): luminance parameters delivered per-scene or even per-frame. Dark scenes aren't affected by a bright scene's "high luminance declaration," and bright scenes aren't averaged down. Dynamic metadata more accurately matches the creator's intent.

The Three Major HDR Standards Compared

Three main HDR standards coexist in the market, with different technical paths and ecosystem support:

HDR10 is the baseline: any display claiming HDR support must support HDR10. It's free, standardized, and has the widest ecosystem support.

Dolby Vision offers the highest theoretical quality (12-bit processing, frame-level dynamic metadata) but requires Dolby's hardware certification and licensing fees, making it more expensive at the device level.

SDR Compatibility: Why HDR Video Looks Washed Out on SDR Screens

This is the most common HDR pain point. The reason is simple: the SDR screen can't display HDR's luminance range, and the player isn't performing tone mapping.

An HDR video's code values under the PQ curve map to 0-10000 nits. A non-HDR-aware player simply interprets the PQ-encoded values as if they were SDR Gamma values—reading a map with the wrong coordinate system. The result is a flat, washed-out image because the brightness mapping error compresses the contrast.

Tone Mapping

The correct way to convert HDR content to SDR is tone mapping: "squeezing" HDR's wide dynamic range into SDR's narrow one. Good tone mapping doesn't simply compress; it selectively preserves perceived quality:

• Preserve shadow detail: the human eye is most sensitive to shadow regions—preserve these first
• Compress highlights: specular highlights (sun, lights) can be heavily compressed or even clipped—the eye is far less sensitive to highlight detail
• Color mapping: BT.2020 gamut → BT.709 gamut; colors outside the target gamut are mapped to the gamut boundary

The quality difference between tone mapping algorithms is dramatic—good tone mapping makes HDR→SDR output look almost as if it were originally shot in SDR; bad tone mapping produces the "hazy wash" effect.

Practical Advice for Producing HDR Content Today

Capture

• Consumer devices: most flagship phones support HDR recording (typically HLG or Dolby Vision) and can shoot HDR video directly
• Professional gear: shoot in Log (S-Log, V-Log, C-Log, etc.) to retain maximum dynamic range, then apply Color Space Transform (CST) to HDR color space in post-production

Monitoring

• HDR color grading requires a monitor capable of 1000+ nits (or a high-end TV with 600+ nits)
• Without an HDR monitor, use waveform / vectorscope displays on an SDR monitor to check whether brightness exceeds the target range—don't rely on your eyes

Distribution

• YouTube / Bilibili: accept HDR10 (or HLG) uploads. After uploading an HDR version, the platform automatically generates an SDR version for users without HDR support
• Netflix / Apple TV: require HDR10 or Dolby Vision masters
• China Mainland platforms: HDR support is inconsistent; delivering an SDR version alongside HDR is advisable

The Most Realistic Strategy: Deliver Both

The most pragmatic HDR workflow today is dual-delivery of HDR + SDR:

1. Complete color grading in HDR (HDR10, P3-D65 or BT.2020)
2. Generate an SDR BT.709 version from the HDR master via color space transform
3. Archive both versions; distribute as appropriate

For individual creators: if your audience primarily watches on phones (most modern phones support HDR display), the HDR version is worth producing. If your audience is mostly desktop and TV, prioritize SDR quality first.

Common Misconceptions

1. "HDR just makes the picture brighter." HDR is about greater dynamic range—brighter highlights and deeper shadows, not turning up the overall brightness. Crudely boosting highlights destroys contrast.
2. "If the monitor says HDR, I can watch HDR." Many monitors labeled "HDR" peak at only 300-400 nits, well below the meaningful HDR threshold (VESA DisplayHDR 600 or higher). True HDR requires brightness, gamut, and bit depth working together.
3. "HDR10+ and Dolby Vision are always better than HDR10." Dynamic metadata is superior in principle, but only when content is correctly authored and the device correctly supports it. If a device doesn't support Dolby Vision, it falls back to HDR10.
4. "HLG doesn't need grading." HLG's backward compatibility with SDR reduces workload, but it's still an HDR standard requiring proper exposure and color management—it's not a "one-click HDR" solution.
5. "A screenshot of an HDR video preserves the HDR." Screenshots are SDR (sRGB) and discard HDR luminance data. Sharing HDR content requires sharing the video file itself.

Practical Tips

• First, check if your device can actually display HDR: verify peak brightness (nits) and gamut coverage (DCI-P3). VESA DisplayHDR 600 is the "entry-level" threshold; DisplayHDR 1000+ is needed for the full HDR impact.
• Watching HDR on a phone is easier than on a TV: modern flagship phones (iPhone, Samsung Galaxy, Huawei P/Mate series) have OLED screens frequently peaking above 1000 nits with mature color management. The phone screen is the most common window into HDR.
• Choose HDR10 for production: free, widest compatibility, mature toolchain. If you're unsure which standard to pick, go with HDR10.
• Perform HDR→SDR conversion in post, don't rely on the client side: creating the SDR version in your editing software using Color Space Transform (CST) or tone-mapping plugins gives you far more control than letting the playback device or platform auto-convert.
• Be aware of HDR's power cost: HDR screens draw significantly more power when displaying bright content full-screen; OLED panels also employ Automatic Brightness Limiting (ABL). These are current hardware limitations.

Further Reading

• Color Basics: RGB, YUV, and Bit Depth — the color foundations for HDR—BT.2020 gamut and 10-bit color depth explained in detail
• LUTs and Color Grading: The Color Science Behind Filters — the role of 3D LUTs in HDR grading—converting Log footage to HDR or SDR color spaces
• Resolution and Clarity: From 480p to 4K — resolution vs. dynamic range: which affects perceived quality more?

This site's video conversion and compression tools support HDR metadata preservation—when exporting HDR video, make sure to select the correct color space (BT.2020) and bit depth (10-bit) for the best platform-compatible HDR results.

Related Tools

• Video Converter
• Filter Video