PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, 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 minuteiTechGuides 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
Jellyfin transcoding is the server changing a media stream so a particular client can play it. It is not required for every playback session: Jellyfin first attempts Direct Play, which sends the original file with almost no server load. A GPU becomes important when clients cannot decode your files, remote bitrate limits require conversion, or demanding operations such as HDR tone-mapping and subtitle burn-in are involved.
The right purchase is a media engine that supports the codecs, bit depth, HDR workflow and number of simultaneous conversions in your library—not a graphics card chosen for gaming performance. For many low-power servers, an Intel processor with a suitable Quick Sync iGPU is enough; a discrete NVIDIA or AMD card is justified when the integrated engine lacks required formats or capacity.
Jellyfin’s four playback paths
Jellyfin chooses a playback path from the client’s profile and the session’s constraints. It considers video and audio codecs, the container, resolution, bitrate, audio capabilities, subtitle behavior and whether the client is local or remote.
Direct Play
Direct Play delivers the original file without transcoding. The container and every stream are already supported by the client, so the server performs little work beyond reading and sending data. This is the ideal path for quality, power use and server capacity.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Remux
A remux changes only the container. Video and audio streams remain untouched, but Jellyfin repackages them into a container the client accepts. Remuxing is substantially lighter than re-encoding because no pixels or audio samples are recomputed.
Direct Stream
Direct Stream keeps the original video while transcoding an incompatible audio track. For example, a client might decode the video codec but not the selected surround-sound format. Video quality and video-processing load stay close to the original, while the server converts audio.
Transcode
A full transcode changes the video stream, usually because the client cannot decode the source codec, resolution, frame rate or bitrate. Jellyfin decodes the source, processes it and encodes a new stream. It may also transcode audio at the same time. This is the most resource-intensive ordinary playback path.
Recommended Free Tools
Why Jellyfin starts transcoding
Unsupported video or audio
A television, phone, browser or streaming stick may not support the source codec, profile or bit depth. HEVC, VP9 and AV1 are common examples that are not universally supported. Unsupported audio can trigger Direct Stream or a full transcode when the client also cannot accept the original video.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Resolution and bitrate limits
A 4K file may need conversion for a 1080p screen, a mobile connection or a remote user with a restricted upload speed. Jellyfin lowers resolution, bitrate or both to meet the client’s requested playback profile. The source file is not altered; the converted stream is generated for that session.
Subtitles
Text subtitles can sometimes be delivered as a separate stream. When the client cannot render the subtitle format, Jellyfin may remux or transcode. Image-based subtitles and subtitles that must be displayed inside the picture require burn-in: Jellyfin renders each subtitle layer onto the video frames. Jellyfin documentation describes burning in subtitles as the most intensive transcoding method because every frame must be processed with the overlay.
HDR, Dolby Vision and SDR displays
HDR material played on an SDR client needs tone-mapping so highlights and colors fit the SDR range. Jellyfin’s current guidance states that HDR-to-HDR tone-mapping and HDR metadata pass-through are not supported during transcoding, so an HDR source being converted to SDR must be tone-mapped. Software tone-mapping can be very slow; the project recommends a GPU, noting that even a basic Intel iGPU can handle this workload comparably to a high-end CPU in suitable conditions.
Do you need a GPU?
You can run Jellyfin without a discrete graphics card, but CPU-only video transcoding is demanding. A separate GPU or integrated media engine is usually unnecessary when every client Direct Plays, or when the server performs only occasional audio conversion and remuxing. It becomes valuable in these situations:
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
- Several people stream at the same time and at least one session needs video conversion.
- Remote clients regularly request lower resolutions or bitrates.
- Your library contains 4K content that must be reduced for 1080p or mobile playback.
- Clients need HEVC 10-bit, VP9 or AV1 decoding that your CPU or client devices do not provide.
- Subtitles frequently require burn-in.
- HDR or Dolby Vision sources must be converted to SDR.
There is no universal “streams per GPU” number. Throughput depends on codec, resolution, bit depth, frame rate, tone-mapping, subtitle work, encoder settings, driver behavior and the rest of the server. Treat any stream-count claim as workload-specific rather than a specification you can apply to every library.
What to compare before buying hardware
| Capability | Why it matters | What to verify |
|---|---|---|
| Decode support | The engine must read the formats in your files. | Check HEVC 10-bit and any VP9 or AV1 content, including the exact GPU generation. |
| Encode support | The engine must produce formats your clients accept. | H.264 is broadly useful; verify HEVC or AV1 encode only if your clients and policies need them. |
| HDR processing | HDR-to-SDR playback needs tone-mapping during transcoding. | Confirm tone-mapping support, HEVC 10-bit decode and operating-system compatibility. |
| Concurrent capacity | Multiple sessions can compete for decode, encode and memory resources. | Use your expected workload; official guidance does not provide one universal stream figure. |
| Drivers and deployment | Jellyfin can use hardware only when the operating system and container expose it. | Check driver versions, device permissions and container runtime support. |
| Power, cost and noise | An always-on server benefits from efficient hardware. | An iGPU often uses less power and produces less noise than a discrete card. |
Hardware acceleration options
Intel Quick Sync and integrated graphics
Intel Quick Sync is often the simplest choice for a home server. The media engine is built into supported Intel processors, so there is no additional card, slot or power connector. It can be sufficient for multiple ordinary conversions when it supports your library’s codecs and bit depth. Verify the processor generation rather than assuming every Intel iGPU supports HEVC 10-bit, VP9 or AV1. A compatible iGPU can also be particularly useful for HDR tone-mapping while keeping power consumption low.
NVIDIA NVDEC and NVENC
NVIDIA hardware acceleration uses NVDEC for decoding and NVENC for encoding. Jellyfin’s documentation states that hardware-accelerated transcoding is supported on GPUs from the Maxwell architecture onward. NVIDIA hardware HDR or Dolby Vision tone-mapping requires HEVC 10-bit decoding, so an older or lower-capability model may fail even if basic H.264 transcoding works. Confirm the installed driver, the exact generation and the application’s access to the NVIDIA runtime. Some consumer NVIDIA cards also impose artificial concurrent-session limits; account for those limits instead of relying on the card’s raw graphics performance.
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 →AMD hardware
AMD systems can use AMF or, on Linux, VA-API paths. Results depend heavily on the operating system, driver version and codec. Check both decode and encode support for the exact GPU and test HDR tone-mapping rather than assuming that a gaming card exposes every media feature Jellyfin needs.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Apple and Rockchip media engines
Jellyfin supports Apple’s VideoToolbox and Rockchip’s RKMPP on compatible systems. These platforms can be efficient when they are already part of your server or appliance, but codec coverage, packaging and driver availability vary. Confirm that your deployment exposes the hardware acceleration API and that the formats in your library are supported end to end.
CPU-only transcoding
Software transcoding remains useful for occasional audio conversion, remuxing and troubleshooting. It is a poor default for repeated 4K conversion, HDR tone-mapping or subtitle burn-in because all decode, processing and encode work runs on general-purpose cores. Jellyfin’s hardware-selection guidance does not recommend relying on CPU video transcoding as the normal solution.
How to enable and verify acceleration
- Inventory your playback clients. Record each device’s supported video codecs, audio formats, maximum resolution, subtitle behavior and remote bitrate. This tells you whether a problem is actually caused by transcoding.
- Check the server’s media engine. Identify the exact Intel, NVIDIA, AMD, Apple or Rockchip model and confirm decode and encode support for your files, especially HEVC 10-bit, VP9 and AV1.
- Install the operating-system driver. Use the driver and media packages appropriate to your OS. On Linux, missing codec packages can leave some stages in software even when the GPU is visible.
- Expose the device to Jellyfin. For Linux containers, pass the render device (commonly
/dev/dri) into the container and grant the Jellyfin process permission to use it. NVIDIA deployments require the matching host driver and container runtime integration. Virtual machines need GPU access configured at the hypervisor level. - Open the transcoding settings. In the Jellyfin Dashboard, go to Playback and then Transcoding (the exact label can vary by release). Select the hardware-acceleration method available on your system.
- Limit codecs to confirmed support. Enable only decode and encode formats that the specific engine and driver support. Leaving unsupported options enabled can cause a software fallback or a failed session.
- Test a forced transcode. Start playback at a lower resolution or bitrate than the source, or use a client that cannot decode the source codec. Direct Play will not reveal whether acceleration is configured.
- Inspect the session. Open the Jellyfin activity details and FFmpeg log. Confirm that the session is marked as transcoding and that hardware decode and encode are being used rather than the CPU fallback.
Troubleshooting common failures
The dashboard shows transcoding but the CPU is still busy
Some pipeline stages may remain in software. Subtitle burn-in, unsupported filters, tone-mapping configuration or an unavailable encoder can force CPU work even when decoding is accelerated. Read the FFmpeg log to identify the stage that fell back, then verify codec packages, driver versions and the selected hardware encoder.
The GPU is not listed
Check that the host operating system sees the device, the Jellyfin service account has permission to use it and the container or virtual machine exposes it. Linux containers commonly require the correct /dev/dri mapping. A driver installed only on the host may not be sufficient if the container lacks the corresponding libraries.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
HDR playback fails or looks wrong
Confirm that the source is being converted to SDR, because HDR-to-HDR tone-mapping and HDR metadata pass-through are not currently supported. Verify HEVC 10-bit decode, the GPU generation, the driver and the selected tone-mapping options. If the GPU cannot perform the operation, software tone-mapping may work but can be too slow for real-time playback.
Subtitles cause buffering
Determine whether the subtitle track requires burn-in. Try a text subtitle format the client can render, or disable subtitles as a diagnostic. If burn-in is unavoidable, use hardware that can sustain the combined decode, overlay and encode workload; subtitle rendering can be the limiting stage even when ordinary video transcodes are smooth.
Only some files use hardware acceleration
Compare the files’ codecs, profiles, bit depth, resolution and audio tracks. A media engine may accelerate H.264 and HEVC 8-bit while falling back for HEVC 10-bit, VP9 or AV1. The behavior is format-specific, not proof that the entire GPU configuration is broken.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteA practical buying decision
- Start with Direct Play. If all household clients support your files and your network can deliver their bitrates, keep the current server and avoid buying a GPU.
- Measure the actual exceptions. Identify which sessions transcode, why they transcode and whether the trigger is video, audio, subtitles, resolution, bitrate or HDR.
- Choose an iGPU when efficiency is the priority. A supported Intel Quick Sync system is usually the most economical route for a small, always-on server.
- Choose a discrete GPU when requirements exceed the iGPU. Consider one when the processor has no suitable media engine, several users need simultaneous conversion, or the library requires codec and HDR capabilities the iGPU lacks.
- Validate the deployment, not just the silicon. Driver support, container permissions, operating-system APIs and consumer session limits can matter as much as the model name.
Bottom line
Jellyfin transcoding is conditional conversion for a client’s limitations, not a requirement for every stream. Direct Play and remuxing use little server power; audio-only Direct Stream is moderate; video transcoding, HDR tone-mapping and subtitle burn-in are the workloads that justify hardware acceleration. Buy media-engine capability matched to your codecs and clients, with a capable integrated GPU serving many home servers and a discrete card reserved for heavier or less compatible workloads.
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.
