Why is Jellyfin transcoding instead of direct playing?

Jellyfin transcodes when the client can't play the file's video codec, audio codec or container directly, or when subtitles must be burned in. Check the playback info to see what's being converted. Storing device-friendly formats (HEVC/H.264, AAC/AC3, MP4/MKV) and using text-based subtitles keeps most playback on direct play instead of transcoding.

How do I enable hardware transcoding in Jellyfin?

In the Jellyfin Dashboard, open Playback, Transcoding, and select your hardware acceleration method — Intel Quick Sync (QSV), NVIDIA NVENC or VAAPI — matching your CPU or GPU, then enable the codecs it supports. Jellyfin includes this for free, unlike Plex. Once configured on capable hardware, it handles even 4K transcoding smoothly.

Why does Jellyfin transcoding fail or show a playback error?

Common causes are hardware acceleration not set up correctly, missing GPU drivers or permissions in a Docker/NAS setup, or a codec the hardware can't handle. Check the Dashboard transcoding settings and logs, confirm the GPU is passed through and drivers are installed, and fall back to software transcoding to test whether hardware acceleration is the issue.

Why do subtitles force Jellyfin to transcode?

Image-based subtitles (PGS, VobSub) must be burned into the video, which forces a transcode, and even some text subtitles trigger it on certain clients. Use text-based SRT subtitles where possible, and choose a client that supports them natively, to keep playback on direct play. Burned-in subtitles always require transcoding.

Does Jellyfin transcoding need a powerful server?

For software transcoding, yes — it's CPU-heavy. But Jellyfin's free hardware acceleration lets a modest CPU with Intel Quick Sync, or a supported GPU, transcode several streams including 4K. If you rely on software transcoding without hardware support, a weak server will struggle; enabling hardware acceleration is the key fix.

Fix Jellyfin Transcoding Issues in 2026: Full Guide

The fastest fix for Jellyfin transcoding issues is to enable hardware acceleration in the Dashboard (Quick Sync or NVENC) and store device-friendly formats and text subtitles, so playback stays on direct play or transcodes on the GPU. Jellyfin includes hardware transcoding for free — the trick is configuring it. This guide covers acceleration, codecs, burned-in subtitles and errors, with a diagnosis table. It builds on our transcoding explainer and Jellyfin setup guide.

The Jellyfin transcoding settings with hardware acceleration options — Jellyfin transcoding issues are usually hardware acceleration — enable Quick Sync or NVENC.

Causes, Most to Least Common

Hardware acceleration not set up — Jellyfin falls back to heavy software transcoding.
Incompatible codec/container — the client can’t direct-play the file.
Burned-in subtitles — image-based PGS/VobSub force a transcode.
GPU driver/passthrough missing — common on Docker or NAS setups.
Underpowered server — software transcoding on a weak CPU.

Fixes: Easiest First

Check the playback info — see if it’s Direct Play or Transcode, and what’s converting (video, audio or subs).
Enable hardware acceleration — Dashboard → Playback → Transcoding → Quick Sync/NVENC/VAAPI + supported codecs.
Confirm GPU access — drivers installed, and passthrough configured in Docker/NAS.
Use compatible formats — HEVC/H.264 video, AAC/AC3 audio, MP4/MKV containers.
Use text subtitles — prefer SRT over image subs to avoid burn-in transcoding.

A diagnosis flow for Jellyfin transcoding from hardware acceleration to codecs — Enable hardware acceleration, confirm GPU access, then fix codecs and subtitles.

Diagnosis Table

Symptom	Likely cause	Fix
Always software transcoding	Hardware accel off	Enable Quick Sync/NVENC in Dashboard
Transcode fails / playback error	GPU driver/passthrough	Install drivers; configure passthrough
Transcodes only with subtitles	Burned-in image subs	Use text SRT subtitles
Transcodes on one client	Client codec support	Use a client that supports the codec
4K stutters when transcoding	Weak server	Use hardware accel or a stronger server

By Setup

Windows/Linux install: enable the matching hardware acceleration and install GPU drivers.
Docker: pass the GPU into the container (device mapping) and install drivers on the host.
NAS (Synology/QNAP): confirm the model supports hardware transcoding and enable it in Jellyfin.
Client side: use apps that support your codecs natively so files direct-play — see the Jellyfin review.

The Bottom Line

Jellyfin transcoding issues almost always come down to hardware acceleration and formats: enable Quick Sync or NVENC in the Dashboard, confirm your GPU drivers and passthrough, store device-friendly codecs, and use text subtitles to avoid burn-in transcodes. Jellyfin’s free hardware transcoding does the rest. Understand the tech in our transcoding explainer and video codecs guide, set it up with our Jellyfin setup guide, read the full Jellyfin review, and start from our streaming troubleshooting checklist, and look up any term in the streaming glossary.