Jellyfin Dolby Vision Profiles Explained: 5 vs 7 vs 8 (Which Direct Plays?)

Jellyfin Dolby Vision Profiles Explained: 5 vs 7 vs 8 (Which Direct Plays?)

Dolby Vision is the most advanced HDR format available - 12-bit color depth, dynamic per-scene metadata, and a quality ceiling well above HDR10. But unlike HDR10, Dolby Vision is not a single specification. It comes in 8 different profiles, and not all of them play on every device.

If you have ever downloaded a 4K Dolby Vision remux only to watch it play in HDR10 - or worse, with washed-out colors as if HDR were stripped entirely - the cause is almost always a profile mismatch between your file and your client.

This guide explains every Dolby Vision profile, which ones Direct Play on which devices, and how to organize your library to avoid transcoding HDR content.

The 8 Dolby Vision Profiles

The four profiles you actually encounter as a self-hoster:

• Profile 5 - streaming downloads
• Profile 7 - Blu-ray remuxes (FEL or MEL variant)
• Profile 8 - re-encoded for compatibility
• Profile 4 - rare, mostly Apple

Why So Many Profiles Exist

Dolby Vision is licensed technology. Different distribution channels (cinema, streaming, Blu-ray, broadcast) negotiated different specifications based on bandwidth, hardware, and display requirements:

• Profile 5 was designed for streaming - smaller file sizes, single-layer, requires DV-capable display
• Profile 7 was designed for physical media - dual-layer for maximum quality, with backwards compatibility to Blu-ray players
• Profile 8 is the modern compromise - single-layer like Profile 5, but with HDR10 fallback so non-DV devices can still play it

The trade-off: more profiles = more compatibility headaches.

Profile-by-Profile Compatibility

Profile 5 (Single-layer, Display-led)

What it is: A single video stream with embedded RPU (Reference Processing Unit) metadata. The display does all the tone mapping. There is no HDR10 base layer - the video looks washed out on non-DV displays.

Where you encounter it: WEB-DL releases from Netflix, Disney+, Apple TV+, and other streaming services.

Direct Play compatibility:

The catch: Profile 5 has no HDR10 fallback. On a non-DV display, the file looks gray and washed out. For shared servers, this is a problem - one user with an Apple TV is fine, another user on a Samsung TV gets ruined picture.

Profile 7 (Dual-layer, Blu-ray standard)

What it is: Two video streams in one MKV file - a base HDR10 layer (BL) plus a Dolby Vision enhancement layer (EL) and metadata (RPU). Devices that don't support DV play just the HDR10 base layer. Devices that do support DV combine both layers for full DV.

There are two sub-variants:

• Profile 7 FEL (Full Enhancement Layer) - maximum quality, larger files
• Profile 7 MEL (Minimal Enhancement Layer) - quality close to HDR10, much smaller EL

Where you encounter it: Untouched UHD Blu-ray remuxes.

Direct Play compatibility:

The catch: Almost no consumer streaming device supports Profile 7 in full DV. Even the NVIDIA Shield, the gold standard for Android TV, falls back to HDR10. The only consumer devices that natively decode Profile 7 are the Ugoos AM6B+ with CoreELEC and the Vero V running OSMC.

For most self-hosters, Profile 7 means "I have the HDR10 layer, but I'm not getting full Dolby Vision."

Profile 8 (Single-layer with HDR10 fallback)

What it is: Single-layer video like Profile 5, but with an HDR10 base that ensures non-DV devices get correct HDR10 instead of washed-out SDR. This is the best compatibility profile for self-hosted libraries.

Sub-variants:

• Profile 8.1 - HDR10 fallback (most common)
• Profile 8.4 - HLG fallback (broadcast/sports)

Direct Play compatibility:

The win: Even on devices that can't decode Dolby Vision, Profile 8 plays correctly as HDR10. No washed-out colors. No transcoding required.

For shared self-hosted servers in 2026, Profile 8 is the recommended target format.

How to Identify the Profile of Your Files

Use MediaInfo (free, available on all platforms):

1. Open the MKV/MP4 file in MediaInfo
2. Look at the video stream
3. Find the line: HDR format

You will see something like:

HDR format: Dolby Vision, Version 1.0, Profile 8.1, dvhe.08.06, BL+RPU

The key fields:

• Profile 5 → Display-led, no HDR10 base
• Profile 7 → Look for "BL+EL+RPU" - dual-layer
• Profile 8 → Look for "BL+RPU" - single-layer with HDR10 base

You can also use dovi_tool info input.mkv from the command line for detailed analysis.

Converting Profile 7 to Profile 8

If you have a Profile 7 Blu-ray remux and want it to Direct Play on an Apple TV or Shield, you can convert to Profile 8 using dovi_tool:

# Extract video stream
mkvextract input.mkv tracks 0:video.hevc

# Convert Profile 7 to Profile 8.1
dovi_tool -m 2 convert video.hevc -o video_p8.hevc

# Remux back into MKV (preserving audio and subtitles)
mkvmerge -o output.mkv video_p8.hevc audio.dts subs.srt

Trade-off: You lose the FEL enhancement layer (the highest-fidelity DV data). The result is "Profile 8 from Profile 7 BL" which is visually equivalent to Profile 8.1 but slightly below true FEL quality. For most viewers on consumer displays, the difference is invisible.

What Jellyfin Does With Each Profile

Jellyfin's role is to deliver the file to the client. It does not understand DV profiles - it just passes the bytes through. Whether the file plays correctly depends entirely on the client.

What this means in practice

Tone mapping HDR to SDR

If the client cannot display HDR at all (web browser, old phone), Jellyfin's transcoding pipeline can tone-map HDR to SDR. This requires:

• Hardware tone mapping enabled (Dashboard → Playback → Transcoding)
• A GPU that supports it (Intel 11th Gen+, NVIDIA RTX, modern AMD)

Without hardware tone mapping, software tone mapping is too slow for real-time playback. The result is washed-out colors or stuttering.

Best Practices for a Mixed-Device Server

If you serve users with different devices (Apple TV, Samsung TV, Fire TV, browsers), here's the strategy:

1. Convert all Profile 7 sources to Profile 8.1 - widest compatibility, plays as HDR10 on non-DV devices
2. Keep Profile 5 streaming sources as-is - Profile 5 works on all major streaming devices
3. Avoid storing Profile 7 long-term unless you have a Ugoos AM6B+ or Vero V
4. Enable hardware tone mapping for users on browsers or older devices
5. Document which content is DV in your library tags (use Bazarr or Kometa overlays)

For a single-user server with an Apple TV or Shield, this matters less. For a shared server with diverse devices, Profile 8 standardization is worth the conversion effort.

Common Dolby Vision Issues in Jellyfin

Profile Quick Reference

When in doubt:

• Streaming source (WEB-DL): Profile 5 - works on streaming devices, fails on Samsung
• Blu-ray remux (untouched): Profile 7 - falls back to HDR10 on most devices
• Re-encoded for compatibility: Profile 8 - the recommended target
• Apple ecosystem only: Profile 4 - rare, ignore for shared servers

For shared self-hosted libraries, Profile 8 is the safest target because it provides full DV on capable devices and HDR10 fallback on everything else.

FAQ

Does Jellyfin support Dolby Vision? Jellyfin passes DV files through to clients without modification. Whether DV is preserved depends on the client device's hardware and software support.

Can I tell which DV profile is best? For self-hosted libraries with mixed devices: Profile 8.1. For maximum quality with a Ugoos AM6B+ or Vero V: Profile 7 FEL.

Why does my Profile 7 file play as HDR10 on the Shield? The NVIDIA Shield does not support Profile 7. It plays the HDR10 base layer and ignores the DV enhancement layer. To get full DV, convert the file to Profile 8.

Can I play Profile 5 on a Samsung TV? Not properly - Samsung does not support Dolby Vision (Samsung uses HDR10+ instead). Profile 5 plays without HDR metadata, resulting in a washed-out picture. You need Profile 8 or HDR10+ source content for Samsung TVs.

Does Plex handle Dolby Vision better than Jellyfin? No. Both servers pass the file through identically. The difference is the client - Apple TV with Infuse handles DV best regardless of which server is hosting.

Can I convert Profile 7 to Profile 8 without quality loss? You preserve the HDR10 base layer perfectly. You lose the Dolby Vision enhancement layer (FEL). For most viewers, the visual difference is undetectable on consumer displays.

Will the JellyWatch Watch Party feature work with DV content? JellyWatch monitors sessions, including DV streams. Group watching uses Jellyfin's native SyncPlay - whether DV plays correctly depends on each participant's device.

Tracking your DV streams? Verify Direct Play in real time. Download JellyWatch on Google Play - see the exact codec, profile, and playback method for every active session on your Jellyfin server.

On Emby? Download EmbyWatch on Google Play - the same monitoring experience for Emby servers.