mpv HDR Guide 2026: HDR10, HDR10+, Dolby Vision & Tone Mapping Explained

Last Update: October 3, 2026

Version note: The latest stable release is mpv 0.41. Current development builds intended for mpv 0.42 contain major Dolby Vision Profile 7 changes, including MEL and FEL enhancement-layer processing. Where relevant, this guide distinguishes between the two.

Introduction

If HDR video looks washed out, too dark, or inconsistent in mpv media player, the problem is usually a misunderstanding of how HDR actually works.

This mpv HDR guide explains HDR10, HDR10+, and Dolby Vision in practical terms, how mpv handles them internally, and why many HDR setups fail even with “correct” configurations. The goal is not just to fix playback issues, but to give you a clear mental model so you can predict how HDR will behave on your system.

If you’re looking for a working configuration, see the Best mpv Config 2026 guide. Platform and display-specific differences are summarized later in this article.

What HDR Actually Is (and Why It Breaks)

HDR (High Dynamic Range) is not just “brighter video.” It expands the range between the darkest and brightest parts of an image.

The key differences from SDR:

• Higher peak brightness
• Better highlight detail
• Wider color gamut
• Different transfer functions (PQ / HLG)

The problem: HDR only works correctly if every part of the chain agrees.

That chain includes:

• the video file
• the player
• the GPU
• the operating system
• the display

If any part misinterprets the signal, the result is:

• washed-out colors
• crushed highlights
• overly dark scenes

HDR Formats Explained

HDR10 (Baseline HDR)

• Static metadata (one set of brightness values for the entire video)
• Most common format
• Works everywhere

Limitation: cannot adapt scene-by-scene

HDR10+ (Dynamic HDR)

• Scene-by-scene dynamic metadata
• Can describe changing peak and average brightness across the video
• Supported by mpv/gpu-next through its ST 2094-40 metadata and tone-mapping path

In the configuration used by this guide, HDR10+ is given its own profile with tone-mapping=st2094-40 and hdr-compute-peak=no so its scene metadata is not masked by generic computed peak analysis.

Dolby Vision

Dolby Vision combines dynamic RPU metadata with a proprietary Dolby playback ecosystem and exists in several profiles, including Profiles 5, 7, 8 and 9.

The important distinction with mpv is that processing Dolby Vision source information is not the same thing as outputting native licensed Dolby Vision.

mpv’s gpu-next renderer can consume supported Dolby Vision RPU metadata internally and use it during color conversion, rendering, and tone mapping.

Profile 7 changed substantially during 2026. Stable mpv 0.41 predates the newest work, but current development builds intended for mpv 0.42 add both MEL support and actual FEL enhancement-layer processing.

In practical terms:

For Profile 7 FEL, this is more than simply reading the RPU. Current mpv can pair the base layer and enhancement layer and pass the enhancement-layer frame into gpu-next/libplacebo for rendering.

This still does not turn the PC into a licensed Dolby Vision HDMI source. mpv ultimately renders through its normal HDR and color-management output pipeline rather than switching the television into a native Dolby Vision mode.

That last distinction is important.

The upstream FEL code now actually carries a separate enhancement layer through the pipeline, rather than merely extracting metadata. gpu-next then exposes that enhancement layer to libplacebo.

Dolby Vision RPU vs hdr-compute-peak

hdr-compute-peak=yes is easy to misunderstand.

It enables image-based peak detection, but it does not necessarily force that detector to replace available dynamic metadata.

With supported Dolby Vision material, libplacebo can prefer the RPU metadata. This is why changing hdr-compute-peak on a Dolby Vision title does not necessarily produce the same behavior as it does with ordinary HDR10.

For my recommended configuration, I therefore keep Dolby Vision separate from generic HDR:

• generic HDR → hdr-compute-peak=yes
• Dolby Vision RPU → hdr-compute-peak=no
• HDR10+ → hdr-compute-peak=no

The Dolby Vision setting does not enable RPU processing; mpv/libplacebo already does that when usable metadata is available. It simply makes the intended policy explicit.

If you deliberately want to disable Dolby Vision processing and use the underlying video without its RPU metadata, mpv provides:

vf=format=dolbyvision=no

That is mainly useful for testing or troubleshooting rather than as a normal playback setting.

How mpv Handles HDR (This Is Where It Wins)

Modern mpv uses the libplacebo-based gpu-next renderer, which became mpv’s default in version 0.41. This gives it three key capabilities:

1. Tone Mapping Control

mpv can map HDR → display space intelligently instead of blindly clipping.

2. Metadata Awareness

mpv can:

• use HDR10 static metadata
• respond to HDR10+ dynamic metadata
• interpret Dolby Vision metadata (non-native output)

3. Output Flexibility

mpv can:

• work with an SDR-first desktop policy
• signal HDR-aware output when HDR content is playing
• adapt output metadata and rendering behavior to the source

This does not necessarily mean mpv is toggling the Windows HDR setting itself. Exact HDR activation behavior depends on the Windows, driver, swapchain, and display path.

The 3 Most Common HDR Problems (and Why They Happen)

Washed-Out HDR

Symptoms:

• gray blacks
• low contrast

Cause:

• HDR content displayed as SDR
• incorrect output signaling

HDR Too Dark

Symptoms:

• dim image
• lost shadow detail

Cause:

• incorrect tone mapping
• mismatch between content peak brightness and display capability

Inconsistent Brightness

Symptoms:

• scenes vary wildly in brightness

Cause:

• differences between:
  • HDR10 (static)
  • HDR10+ (dynamic)
  • Dolby Vision metadata

The Correct Mental Model

HDR is not a toggle.

It is a negotiation between systems.

Your final image depends on:

• source metadata
• mpv’s interpretation
• GPU pipeline
• OS HDR behavior
• display capabilities

If you treat HDR like a simple setting, you will get inconsistent results. If you treat it like a pipeline, you can control it.

Recommended Approach for mpv (2026)

For a dedicated or mixed-use Windows HTPC, my preferred approach is:

– use gpu-next
– keep normal desktop use in SDR if that gives your display the most predictable SDR behavior
– enable HDR-aware output for HDR content
– let mpv consume dynamic metadata where supported
– avoid forcing display-specific peak/gamut values unless you know the display characteristics

For a full working setup:

• See Best mpv Config 2026
• For Jellyfin users: Jellyfin MPV Shim Guide

mpv vs madVR (Quick Comparison)

FAQ (High-Intent Questions)

Does mpv support Dolby Vision?

mpv does not provide a licensed native Dolby Vision output mode, but gpu-next can consume supported Dolby Vision RPU metadata internally. Current development builds intended for mpv 0.42 also add substantially improved Profile 7 support, including FEL enhancement-layer processing.

Does mpv support Dolby Vision Profile 7?

It depends on the mpv version. Stable mpv 0.41 predates the newest Profile 7 work. Current development builds intended for mpv 0.42 support Profile 7 MEL and can decode and apply the FEL enhancement layer.

This should not be confused with native Dolby Vision output: mpv uses the Dolby Vision information internally while still rendering through its normal HDR/color-management output pipeline.

Is HDR10+ better than Dolby Vision?

Not strictly. Both use dynamic metadata, but Dolby Vision is proprietary and more widely adopted in streaming.

Should I enable Windows HDR all the time?

Not necessarily. For a mixed-use HTPC, I prefer an SDR-first desktop and HDR-aware output only when needed because it keeps SDR behavior predictable.

Why does HDR look different in VLC?

Different players use different tone mapping strategies and may ignore metadata.

Final Thoughts

The best HDR setup is not the one with the most settings.

It is the one that:

• respects how HDR actually works
• uses metadata correctly
• aligns the entire playback chain

If you understand that, mpv becomes one of the most powerful HDR playback tools available.