iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Direct Play sends the original media file to your device unchanged. Direct Stream converts the audio while leaving the original video stream intact. Remuxing changes only the container, or wrapper, around the streams. Transcoding converts the video (and sometimes audio, subtitles, or other parts), making it the most demanding mode for the server. Jellyfin chooses among these modes from the combined capabilities of the client and the file: container, video codec, audio codec, subtitles, bitrate, resolution, and other limits all matter. The same file can therefore Direct Play on one television and transcode on another.
The four Jellyfin playback modes at a glance
Jellyfin’s playback labels describe how much of a file the server must change before a client can play it. Its documentation orders the modes from lowest to highest server work as Direct Play, remux, Direct Stream, and Transcode. The practical differences are:
| Mode | What Jellyfin changes | What remains from the source | Typical server load |
|---|---|---|---|
| Direct Play | Nothing | The complete original file | Almost none |
| Remux | Only the container or wrapper | Original video and audio streams | Low; Jellyfin says it should not concern even a Raspberry Pi 3 |
| Direct Stream | Audio is transcoded | Original video stream | Higher than remux, usually lower than video transcoding |
| Transcode | Video is transcoded; audio, subtitles, or other processing may also be involved | Only the portions that do not need conversion | Highest of these four modes |
Jellyfin’s official explanation is concise: “Direct Play: Delivers the file without transcoding. There is no modification to the file and almost no additional load on the server.” See the Jellyfin Transcoding documentation for the terminology used by the server and clients.
Direct Play
With Direct Play, Jellyfin reads the stored file and delivers it as-is. No container, video stream, audio stream, or subtitle data is converted. Because the server is not decoding and re-encoding the media, this mode normally consumes very little CPU and does not require a powerful graphics processor. The client must support every relevant part of the file, however; a compatible video codec alone is not enough.
#1 Best Overall
- Entry-level NAS Personal Storage：UGREEN NAS DH2300 is your first and best NAS made easy. It is designed for beginners who want a simple, private way to store videos, photos and personal files, which is intuitive for users moving from cloud storage or external drives and move away from scattered date across devices. This entry-level NAS 2-bay perfect for personal entertainment, photo storage, and easy data backup (doesn't support Docker or virtual machines).
- Set Your Devices Free, Expand Your Digital World: This unified storage hub supports massive capacity up to 64TB.*Storage drives not included. Stop Deleting, Start Storing. You can store 22 million 3MB images, or 2 million 30MB songs, or 43K 1.5GB movies or 67 million 1MB documents! UGREEN NAS is a better way to free up storage across all your devices such as phones, computers, tablets and also does automatic backups across devices regardless of the operating system—Window, iOS, Android or macOS.
- The Smarter Long-term Way to Store: Unlike cloud storage with recurring monthly fees, a UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $459.98 for a NAS, while for cloud storage, you need to pay $719.88 per year, $2,159.64 for 3 years, $3,599.40 for 5 years. You will save $6,738.82 over 10 years with UGREEN NAS! *NAS cost based on DH2300 + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Blazing Speed, Minimal Power: Equipped with a high-performance processor, 1GbE port, and 4GB RAM on Board, this NAS handles multiple tasks with ease. File transfers reach up to 125MB/s—a 1GB file takes only 8 seconds. Don't let slow clouds hold you back; they often need over 100 seconds for the same task. The difference is clear.
- Let AI Better Organize Your Memories: UGREEN NAS uses AI to tag faces, locations, texts, and objects—so you can effortlessly find any photo by searching for who or what's in it in seconds. It also automatically finds and deletes similar or duplicate photo, backs up live photos and allows you to share them with your friends or family with just one tap. Everything stays effortlessly organized, powered by intelligent tagging and recognition.
Remux
Remuxing repackages the existing streams in a different container. The video and audio bits are not re-encoded, so there is no generational quality loss and comparatively little computation. Jellyfin notes that many video containers are remuxed for streaming, often into HLS/TS. A remux is therefore not the same thing as Direct Stream: remuxing changes the wrapper, whereas Direct Stream normally includes audio conversion.
Direct Stream
In Direct Stream, Jellyfin leaves the video stream untouched but transcodes an incompatible audio stream into one the client can decode. This is why a file that appears to have a supported video codec can still show a Direct Stream label. Audio conversion is generally much less intensive than converting video, although the exact cost depends on the codec, bitrate, number of simultaneous sessions, and server hardware.
Transcode
Jellyfin uses “Transcode” in its playback list when the video stream must be converted. The server decodes the source video and encodes a new stream for the client. Audio may also be converted, and subtitle processing can add another workload. Video transcoding is the mode most likely to expose CPU, GPU, driver, thermal, or storage limits.
How Jellyfin decides which mode to use
Jellyfin aims to Direct Play whenever the client can handle the media. The client sends a capability profile to the server, including supported containers and codecs, maximum resolutions, bitrate limits, and other constraints. Jellyfin compares that profile with the file and selects an output the client is expected to accept. The relevant compatibility dimensions are documented in the Jellyfin Codec Support tables.
Rank #2
- 【Advanced Home Data & Media Hub】For advanced home users who need phone backup, file storage, and centralized data management. Centralize family photos, 4K videos, movies, computer backups, and personal files in one place while running multiple apps for home entertainment and everyday data management. Suitable for households with growing digital libraries and multiple NAS use cases.
- 【Built for Creators, Media Servers & Advanced Apps】Powered by the Intel N100 Quad-Core CPU, 8GB DDR5 RAM, 2.5GbE networking, and dual M.2 NVMe slots, DXP2800 handles large files and heavier workloads with ease. Run Docker, virtual machines, and media server applications compatible with Plex—ideal for content creators, tech enthusiasts, and advanced home users managing 4K videos, RAW photos, personal media libraries, and multiple NAS apps.
- 【Up to 80TB for Growing Digital Libraries】 Supports up to 80TB of storage using two HDD bays and two M.2 NVMe SSD slots for family photos, movies, RAW photos, 4K videos, work files, and device backups. AI photo management supports recognition of people, objects, scenes, and locations, album organization, and duplicate photo detection. HDDs and SSDs are not included.
- 【AI-powered Home Surveillance】Turn DXP2800 into a centralized home surveillance hub by connecting compatible network cameras and storing recordings locally on your NAS. AI-powered features include Face Recognition, People Detection, and Pet Detection, helping advanced home users review important events more efficiently while managing home surveillance and personal data in one place.
- 【One data Center Across Your Devices】Keep files from desktops, laptops, phones, tablets, and other devices together instead of scattered across cloud accounts and external drives. Access, back up, organize, and share data across Windows, macOS, Android, iOS, web browsers, and compatible smart TVs—ideal for creators and advanced home users working across multiple devices.
Container compatibility
A container such as MP4, Matroska, or MPEG transport stream is a wrapper that organizes audio, video, subtitles, and metadata. A client can support the codecs inside a file but still reject the wrapper. In that case Jellyfin can remux the streams into a supported container without touching the encoded audio or video. Remuxing is usually preferable to a full transcode because it preserves quality and requires little processing.
Video-codec compatibility
If the client cannot decode the video’s codec, profile, bit depth, level, or frame-rate combination, Jellyfin must transcode the video. Modern HEVC and high-bit-depth formats are common examples of files that exceed an older television, browser, or mobile app’s decoder capabilities. A network connection that can carry the file does not solve a decoder incompatibility; the client still has to understand the compressed video.
Audio-codec compatibility
An unsupported audio codec usually causes Direct Stream rather than video transcoding. The server decodes and re-encodes only the audio while passing through the original video. This generally uses far fewer resources than a video conversion, so do not assume every Direct Stream session needs a high-performance GPU.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallBitrate, resolution, and other client limits
Even when codecs are supported, a client may advertise a maximum bitrate or resolution that is lower than the source. Jellyfin selects output settings within those limits. Its documentation says the resulting resolution depends on input resolution and frame rate, target bitrate, codecs, and client constraints; that page does not provide a manual resolution override. A bandwidth-saving setting or an adaptive streaming condition can therefore trigger video transcoding on a file the client could decode at its original quality.
Rank #3
- Your Personal Streaming Server - Build your own Netflix-style media library and stream 4K movies, shows and photos to any device without monthly fees
- Create Your Own Cloud - Store your entire photo, video and music collection; access from anywhere with fast 282 MB/s transfer speeds
- Creator-Grade Backup Solution - Protect your irreplaceable content with automated backups to cloud services, external drives and remote NAS
- Multi-Layered Data Protection - Combine RAID redundancy, automated backups and snapshot technology to prevent data loss from any cause
- Smart Home Surveillance - Support up to 30 IP cameras with AI detection, instant alerts and secure remote monitoring
Subtitles are a frequent hidden cause
Subtitles can change the playback mode even when the container, video, and audio appear compatible. The result depends on the subtitle format, the container, and the particular client. Text subtitles may be passed through, converted, or remuxed. Image-based subtitles and formats the client cannot render may require Jellyfin to burn the text into the picture.
Why burn-in is expensive
Burn-in combines the subtitle layer with every video frame. Jellyfin must decode the video, render the subtitle graphics at the correct timing and position, and encode a new video stream. Its documentation describes subtitle burn-in as the most intensive subtitle method. It can therefore turn an otherwise Direct Play file into a full video Transcode.
How to avoid unnecessary subtitle conversion
- Choose a subtitle format your client supports natively, such as a compatible text format, when available.
- Check the client-specific compatibility tables before assuming that SRT, WebVTT, ASS/SSA, VobSub, or MP4TT/TXTT will behave identically everywhere.
- Test playback with subtitles disabled. If the mode changes from Transcode to Direct Play, the subtitle path is the cause.
- Remember that the same subtitle file can be harmless in one app and force burn-in in another; compatibility is not universal across televisions, browsers, and mobile clients.
Use the live codec and subtitle compatibility tables for the exact client and app version, because those tables and client capabilities can change.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →How to find out why a file is transcoding
Do not start by buying hardware. First identify which component is incompatible. The dashboard reports the active playback mode while a session is running.
Rank #4
- [Quad-Core Processor for Daily Tasks] Powered by Realtek RTD1619B quad-core 1.7GHz CPU, ensuring stable performance for file storage, backup, and personal cloud usage.
- [Fast 2.5GbE Network Upgrade] Equipped with 2.5-Gigabit Ethernet, delivering faster transfer speeds than traditional Gigabit NAS for home data management.
- [1GB DDR4 Efficient Memory] Optimized 1GB DDR4 memory ensures stable system performance for basic multitasking and background services.
- [Personal Cloud Backup Solution] Create your own private cloud to store, access, and manage files securely from anywhere with full data ownership.
- [Tool-Free Installation for Fast & Easy Setup] Designed for user convenience with tool-free drive installation, allowing quick HDD/SSD setup without screws—perfect for beginners and IT professionals.
- Start the movie or episode on the device that has the problem.
- Open the Jellyfin server dashboard and view the active session or playback details.
- Record whether the session says Direct Play, Remux, Direct Stream, or Transcode. Note any separate indicators for video, audio, subtitles, bitrate, or resolution.
- Compare the file’s container, video codec and profile, audio codec, resolution, frame rate, bitrate, and subtitle format with the capability profile for that client.
- Disable subtitles and replay the same timestamp. A change to Direct Play identifies subtitle handling as the likely trigger.
- Try the same file in another supported client. If the second client Direct Plays it, the original app or device has the narrower capability profile.
- Only after confirming video transcoding should you investigate server decoding and encoding performance or enable hardware acceleration.
This sequence separates a compatibility problem from a capacity problem. A server that is fast enough for one Direct Stream session can still struggle with several simultaneous 4K video transcodes, while a powerful server cannot make an unsupported client codec play without conversion.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Server load and hardware acceleration
Jellyfin’s mode ordering is a useful capacity guide: Direct Play adds almost no extra server load, remuxing is light, audio conversion is usually modest, and video transcoding is the heaviest of the four. Subtitle burn-in is especially demanding because it is part of the video-processing pipeline.
What hardware acceleration actually does
Jellyfin documents hardware acceleration for Intel Quick Sync, NVIDIA NVDEC/NVENC, AMD AMF, VA-API on Linux, Apple VideoToolbox on macOS, and Rockchip RKMPP on Linux. The pipeline can include decoding, optional deinterlacing, scaling or pixel-format conversion, HDR tone-mapping, subtitle burn-in, and encoding. The hardware-acceleration guide explains the settings for each platform.
Acceleration is not an all-or-nothing switch. Hardware and driver limitations can leave one stage in software while another stage runs on the GPU. For example, a device may decode HEVC in hardware but fall back to software for a particular profile, HDR conversion, subtitle burn-in, or encoder. Check the server log and the active session details rather than assuming that an enabled option means every stage is accelerated.
Best Value
- Entry-level NAS Home Storage: The UGREEN NAS DH4300 Plus is an entry-level 4-bay NAS that's ideal for home media and vast private storage you can access from anywhere and also supports Docker but not virtual machines. You can record, store, share happy moment with your families and friends, which is intuitive for users moving from cloud storage, or external drives to create your own private cloud, access files from any device.
- Smart Photo Backup & AI Album: Automatically back up photos and videos from your phone in real time and keep growing family memories organized with AI-powered photo albums. Semantic search, custom learning, and recognition of people, objects, pets, and similar photos help you quickly find the moments you want. Duplicate photo removal also helps keep your library organized—ideal for families and users with large photo collections.
- User-Friendly App & Easy Setup: Connect quickly via NFC, set up simply and share files fast on Windows, macOS, Android, iOS, web browsers, and smart TVs. You can access data remotely from any of your mixed devices. What's more, UGREEN NAS enclosure comes with beginner-friendly user manual and video instructions to ensure you can easily take full advantage of its features.
- More Cost-effective Storage Solution: Unlike cloud storage with recurring monthly fees, A UGREEN NAS enclosure requires only a one-time purchase for long-term use. For example, you only need to pay $629.99 for a NAS, while for cloud storage, you need to pay $719.88 per year, $1,439.76 for 2 years, $2,159.64 for 3 years, $7,198.80 for 10 years. You will save $6,568.81 over 10 years with UGREEN NAS! *NAS cost based on DH4300 Plus + 12TB HDD; cloud cost based on 12TB plan (e.g. $59.99/month).
- Your Data, You Control：No third-party clouds, no hidden access, UGREEN NAS provides a more secure and private data storage solution. It stores data locally on your private hard drives and does automatic backups. Thus, you can keep full control over it. The advanced encryption is TRUSTe certified in the United States and is awarded the first (and only) ETSI EN 303 645 certification mark for NAS products by TÜV SÜD Group.
Choosing hardware for a real workload
Jellyfin’s hardware-selection guidance recommends a platform capable of hardware-decoding HEVC 10-bit, because software decoding of modern codecs can be demanding. It recommends at least 8 GB of RAM for an average deployment; 4 GB may be enough for a Linux server without a graphical interface. These are broad deployment recommendations, not a universal specification for every library or number of users.
If repeated video transcoding is confirmed as your bottleneck, a mini PC or server with Intel Quick Sync and HEVC 10-bit decode support is one possible direction. Verify the exact processor generation, operating system, drivers, and codec support before purchasing. Headline GPU performance alone does not establish that a system can accelerate your particular Jellyfin pipeline. A compatible client or a media format that Direct Plays may eliminate the workload without any hardware upgrade.
When storage caching helps
Jellyfin lists SSD or RAM-disk caching as a possible optimization when transcoding throughput is limited by storage input/output. This is a secondary measure for a diagnosed I/O bottleneck. It will not make an unsupported client codec compatible and will not remove the need for video encoding. Confirm the bottleneck first, then size the cache for the number and resolution of concurrent sessions.
Practical fixes, in the right order
If you see Remux
Remuxing is normally benign. If playback is smooth, no action is required. If a particular client has trouble, choose a container it supports or use a different client; changing the video codec is unnecessary when the streams themselves are compatible.
If you see Direct Stream
Inspect the audio track first. Selecting an alternate audio track that the client supports can restore Direct Play. If the client has no compatible track, audio transcoding is usually a reasonable compromise because it preserves the original video and costs less than a video transcode.
If you see video Transcode
Identify whether the cause is video codec, bitrate or resolution limits, or subtitle burn-in. Use a client with the required decoder, select a lower-bitrate stream only when bandwidth requires it, or use compatible text subtitles. If conversion remains necessary, configure and test hardware acceleration for the server’s operating system and drivers.
If playback buffers or stops
- Check the dashboard to distinguish buffering during Direct Play from a saturated transcoder.
- For a video transcode, check CPU/GPU utilization, thermal throttling, encoder session limits, and whether any pipeline stage fell back to software.
- For a remux or Direct Play session, investigate network throughput, Wi-Fi reliability, storage read speed, and the client’s own decoder.
- For subtitle-related failures, repeat the test without subtitles and then with a supported text subtitle.
What to remember
Think of the labels as a ladder of intervention. Direct Play changes nothing; remuxing changes only the wrapper; Direct Stream changes audio while preserving video; Transcode changes video and can include several additional processing stages. The correct goal is not to force every session into Direct Play at any cost. It is to identify the smallest conversion needed for the specific client, then provide enough server capacity for the conversions that remain.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
