4K Remux vs Encode for Jellyfin: What Should You Actually Store? (2026)

4K Remux vs Encode for Jellyfin: What Should You Actually Store? (2026)

It is the most-debated question in any Jellyfin community: store raw Blu-ray remuxes (50-80 GB each) or re-encoded files (15-25 GB)? The answer affects your storage budget, your server's transcoding load, and the quality your users actually see and hear.

Both approaches are legitimate - but the right one depends on your hardware, your storage budget, and what your clients can Direct Play.

What Is a Remux?

A remux is a direct copy of the Blu-ray disc data, reorganized into an MKV container with zero re-encoding. The video bitstream, all HDR metadata (HDR10, HDR10+, Dolby Vision), and all audio tracks (TrueHD Atmos, DTS:X, etc.) are transferred without any modification.

Typical sizes:

• 1080p Blu-ray remux: 15-35 GB
• 4K Blu-ray remux (HEVC): 50-90 GB

Quality: Bit-for-bit identical to the source Blu-ray disc.

What Is an Encode?

An encode runs the source video through a software codec (HEVC/H.265 or AV1) using tools like Handbrake or FFmpeg. The encoder analyzes the video and discards data the human eye is unlikely to notice, dramatically reducing file size.

Typical sizes after encoding (4K HEVC, CRF 17):

• 4K HEVC encode: 18-30 GB (vs 50-90 GB remux)
• Storage saved: roughly 3-4x smaller

Quality: Very high at CRF 16-18, but always marginally below source on close inspection.

Side-by-Side Comparison

The Direct Play Argument

This is the most important factor for Jellyfin users: a file only has value if your clients can Direct Play it.

When Jellyfin transcodes a file - for any reason - you lose:

• All HDR metadata (washed-out colors on SDR devices)
• Lossless audio (TrueHD/DTS downmixed to lossy AAC)
• Full bitrate and quality
• Server resources

Remux Direct Play requirements:

• Client must support HEVC Main 10 for 4K HDR
• Client must support the audio codec (TrueHD, DTS-HD MA) or server transcodes audio only
• Network must sustain 60-80 Mbps consistently for high-bitrate remuxes

HEVC Encode Direct Play requirements:

• Client must support HEVC (same as remux)
• Audio can be baked in as AAC/EAC3 during encode - guaranteeing audio Direct Play on every client
• Lower bitrate means compatibility with more client setups and bandwidth situations

The encode advantage for mixed environments: By re-encoding audio to EAC3 or AAC during the encode process, you guarantee every client Direct Plays without an audio transcode - including Fire TV sticks, phones, and tablets that cannot handle TrueHD. This removes a major source of unnecessary server CPU load.

Dolby Vision: Where Remux Wins Clearly

Dolby Vision is the most important argument for keeping remuxes.

Re-encoding a Dolby Vision file correctly requires specialized tools (dovi_tool, mp4muxer) and a precise workflow. A standard Handbrake or FFmpeg encode strips Dolby Vision metadata entirely, leaving you with standard HDR10 at best.

While workflows exist to preserve DV in HEVC encodes, they are complex, slow, and prone to compatibility issues across clients. For AV1, DV encode support is even more limited.

Rule of thumb: If the content has Dolby Vision and DV matters to you - keep the remux.

Audio: Remux vs Encode

For a Jellyfin server serving clients that cannot handle TrueHD (phones, Fire TV, Roku), adding a compatibility audio track during encode is a significant quality-of-life improvement. Users on those devices get Direct Play instead of a server-side audio transcode.

Storage Math in 2026

A 20 TB hard drive costs roughly $300-400 in 2026. Encoding your entire 500-movie library to save 25 TB saves roughly $400-500 in storage hardware - at the cost of potentially hundreds of hours of CPU/GPU encoding time and marginal quality loss on your best content.

For most self-hosters, the ROI on encoding everything is questionable. Selective encoding makes more sense.

Handbrake Settings for Jellyfin Compatibility

If you encode, these settings maximize Direct Play compatibility across all Jellyfin clients:

On AV1 in 2026: AV1 encodes are ~30% smaller than HEVC at the same quality, but encoding is extremely slow (even with GPU acceleration) and client support is still maturing. HEVC is the safer bet for library-wide encoding until AV1 decode is universal across streaming devices.

The Practical Recommendation

Bottom line: Remux is always the quality leader. For a pure home theater setup with capable clients, keep remuxes. For a mixed-device server where simplicity and compatibility matter more than absolute quality, well-configured HEVC encodes are a practical alternative.

Not sure if your library is Direct Playing or transcoding on each device? Download JellyWatch on Google Play - see the exact playback method (Direct Play, Direct Stream, or Transcode) for every active session on your server, with full codec and bitrate details, in real time from your Android phone.

Storage prices and encoder benchmarks as of 2026. CRF values are starting points - adjust based on your source material and quality expectations.