NAS

Plex & Jellyfin Hardware Transcoding: GPU and RAM Guide

Start with an actual playback session. Direct Play may need no hardware upgrade; a video transcode needs a supported GPU, driver and application path. This guide separates buying capabilities from fixing acceleration, with no universal stream-count promises.

Best for: Home operators selecting a media-server host or diagnosing a server that falls back to CPU transcoding.

Start here: Prove whether this session actually transcodes

Play your own representative file and open Plex Dashboard or Jellyfin playback information. Record video/audio codecs, resolution, bitrate, HDR state, subtitles, client and requested quality.

Choose hardware by the task, then prove it

Direct Play sends supported media to the client without video encoding. Remuxing changes the container; audio-only conversion is not the same workload as a 4K video transcode. Improve client-format compatibility before buying a GPU.
Intel N100/N150 mini-PCs can provide Quick Sync on supported Linux deployments. Start with the worked Linux/Docker acceleration guide, then measure your real files rather than assuming a stream count.
For an existing Plex Pass server, verify hardware decoding and encoding separately. Jellyfin does not require a paid feature licence for hardware acceleration. Application and OS support still determine which features work.

GPU capability is not a throughput benchmark

Intel integrated graphics, Intel Arc, NVIDIA and Apple VideoToolbox each have device-specific codec support. Check decoding and encoding separately, including bit depth and HDR tone mapping. A GPU supporting a codec does not mean both Plex and Jellyfin use it on every operating system.
Intel Arc can be useful for newer codec workloads when the host has supported drivers, adequate PCIe placement, airflow and power. Board outputs, form factor and idle power vary by model; check the actual board before choosing a compact case.
NVIDIA’s current support matrix lists T400 and T1000 at eight simultaneous encode sessions. Other cards have different caps or unrestricted sessions. Professional branding alone does not establish the limit; and eight allowed sessions does not guarantee eight demanding 4K transcodes.
Apple Silicon’s VideoToolbox path is application/OS-specific. Linux /dev/dri instructions do not apply to macOS or Docker Desktop. See Mac mini transcoding for that deployment.

Synology: check the CPU before chasing drivers

Synology’s official model comparison lists DS425+ with Intel Celeron J4125 and DS925+ with AMD Ryzen V1500B. These are different hardware families. DS925+ does not gain Quick Sync by installing an Intel driver.
Having an Intel CPU is only the hardware prerequisite; confirm DSM, package/container support, codec and device access for the exact model. Do not generalise one model’s instructions to every 2025 Plus NAS.
A separate Linux Intel media host can read NAS media over a least-privilege SMB/NFS mount. This lets an AMD NAS keep serving storage without forcing it to software-transcode demanding video. See NAS selection.

Docker, Unraid and TrueNAS deployment boundaries

For Intel Linux Docker, pass the render node and its actual numeric group ID to the container. Avoid privileged mode or chmod 777 as permission fixes. The official Jellyfin image includes Intel user-space media drivers, but still depends on the host kernel and device access.
TrueNAS switched Apps to Docker in 24.10. Use the GPU allocation controls and documentation matching your installed release; a Kubernetes device-plugin recipe is for the older backend.
In a VM or LXC, prove device passthrough in the guest before changing Jellyfin settings. Windows Docker and WSL are not supported QSV environments in Jellyfin’s Intel guide.

RAM, subtitles and HDR: measure the complete job

There is no honest RAM-to-stream-count conversion. Size memory for the operating system, server, transcode cache strategy, metadata jobs and other applications, then watch memory pressure and swap under the real workload. GPU/shared memory and main RAM are separate constraints.
Test one ordinary SDR transcode first. Then add HDR-to-SDR tone mapping and your subtitle format independently. Image-based subtitle burn-in can add CPU work and explain buffering even when video acceleration is active.
Record source/output codec, resolution, bitrate, HDR, subtitles, client, application version, OS/kernel, driver and concurrent sessions. Keep the measured result with those conditions; do not turn it into an unconditional hardware promise.

Operator snapshotEvidence first

First proof

Play your own representative file and open Plex Dashboard or Jellyfin playback information. Record video/audio codecs, resolution, bitrate, HDR state, subtitles, client and requested quality.

Screen to open

ls -l /dev/dri/

Expected signal

You know whether it is Direct Play, Direct Stream/remux, audio-only conversion or video transcoding.

Stop boundary

Do not buy based on an unexplained universal “4K stream count” or patch a production driver to bypass its limits.

Layer path

1A media server only needs a video encoder when the client cannot Direct Play the original format or requested quality. Audio conversion and remuxing are different jobs.

2GPU support has several independent layers: physical codec capability, OS driver/runtime, container device permissions, application support and optional Plex licensing.

3Concurrency depends on the exact workload. NVIDIA’s per-model session cap does not predict 4K throughput; CPU subtitle burn-in or tone mapping can bottleneck a working GPU.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Prove whether this session actually transcodes

Check: Play your own representative file and open Plex Dashboard or Jellyfin playback information. Record video/audio codecs, resolution, bitrate, HDR state, subtitles, client and requested quality.

Expected result: You know whether it is Direct Play, Direct Stream/remux, audio-only conversion or video transcoding.

If not: Direct Play does not exercise a hardware encoder. Lower the client quality below the source resolution for a controlled video-transcode test.

Match the exact CPU and GPU to a supported media path

Check: Look up the CPU/GPU model and OS support, not only the NAS brand. Synology DS425+ uses Intel Celeron J4125; DS925+ uses AMD Ryzen V1500B with no Intel Quick Sync path.

Expected result: A supported decoder/encoder exists for the source and output codecs on this deployment.

If not: An Intel driver cannot create an Intel GPU in an AMD NAS. Keep direct play, or run the media server on a separate supported Intel host using NAS media storage.

Prove the media device reaches the server process

Check: On bare-metal Linux, check /dev/dri; inside Intel containers verify the intended render node and the container user’s numeric group permissions. For NVIDIA use the supported container runtime and the "NVIDIA device and runtime" command below.

Expected result: The server can access its intended media device without privileged mode or global write permissions.

If not: Follow the Intel Linux/Docker setup. On TrueNAS 24.10 and later, use its Docker-based Apps GPU configuration; older Kubernetes instructions do not apply.

Enable the supported acceleration method and retest

Check: For Jellyfin, choose QSV/VA-API as appropriate and only select codecs the device can decode. For Plex, check the server owner’s Plex Pass and hardware acceleration settings. Test first without subtitle burn-in or HDR tone mapping.

Expected result: The active session/log reports hardware video processing and the GPU media engine is busy during the forced transcode.

If not: An enabled checkbox is not proof. Inspect the Jellyfin ffmpeg log or Plex (hw) annotation, then separate device permission, driver, codec and licensing errors.

Measure your workload before sizing more streams

Check: Add HDR tone mapping, your real subtitle format and additional clients one at a time. Record server/software versions, encode speed, dropped/buffering frames, CPU/GPU load and RAM use.

Expected result: Playback stays smooth at your required concurrency with capacity for other server jobs.

If not: Subtitle burn-in, tone mapping, cooling, memory and storage/network limits can dominate. A GPU encoder-session limit is a separate ceiling from achievable throughput.

Safe stop: Do not buy based on an unexplained universal “4K stream count” or patch a production driver to bypass its limits.

Did this solve your problem?

Your answer helps us improve this page.

No account or personal details. We store the page, answer, optional reason and day with a 90-day retention period. A random reference in this browser prevents repeat votes. Feedback privacy

Decision tree

If: Playback reports Direct Play

Then: The video encoder was not exercised

Action: Force a lower-resolution video transcode before judging acceleration.

If: The NAS is DS925+ and no Intel render device exists

Then: This Ryzen V1500B host has no Intel Quick Sync GPU

Action: Use direct play or a separate supported media host; an Intel driver cannot create the hardware.

If: The render device exists on Linux but the container cannot use it

Then: Device mapping or numeric group permission is missing

Action: Map the intended render node and its group to the container user; verify driver profiles before changing codecs.

If: An SDR hardware transcode works, but HDR or subtitles buffer

Then: A later tone-mapping/subtitle stage or whole-system load may be the bottleneck

Action: Add each feature separately, inspect the ffmpeg log and measure throughput/thermals under the actual workload.

If: A T400/T1000 refuses more than eight encode sessions

Then: The documented per-model session cap is separate from practical throughput

Action: Reduce simultaneous transcodes; check the current NVIDIA matrix for the exact card before a purchase.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
Playback reports Direct Play	Playback mode, source codec/resolution and requested output quality	The video encoder was not exercised	Force a lower-resolution video transcode before judging acceleration.
The NAS is DS925+ and no Intel render device exists	Exact model and vendor CPU specification	This Ryzen V1500B host has no Intel Quick Sync GPU	Use direct play or a separate supported media host; an Intel driver cannot create the hardware.
The render device exists on Linux but the container cannot use it	Host/container device listing, numeric group and permission error	Device mapping or numeric group permission is missing	Map the intended render node and its group to the container user; verify driver profiles before changing codecs.
An SDR hardware transcode works, but HDR or subtitles buffer	Working SDR log versus failing HDR/subtitle log, encode speed and CPU/GPU load	A later tone-mapping/subtitle stage or whole-system load may be the bottleneck	Add each feature separately, inspect the ffmpeg log and measure throughput/thermals under the actual workload.

Reference

Commands and settings paths

Intel render devices

ls -l /dev/dri/

Where: Linux host, then inside the media container

Expected: The intended renderD node is present and accessible

Failure means: Absent on host: driver/BIOS/unsupported GPU. Absent in container: missing device mapping

Safe next step: Fix the proven layer; match the group ID without chmod 777.

NVIDIA device and runtime

nvidia-smi

Where: Linux host and NVIDIA-enabled container

Expected: The intended GPU is listed; inspect activity during a forced video transcode

Failure means: Host-only visibility does not prove container access

Safe next step: Use the supported NVIDIA container runtime and the application’s codec support documentation.

Session evidence

Plex Dashboard → Now Playing; Jellyfin playback information and ffmpeg transcode log

Where: Web admin / active playback

Expected: Video transcoding and hardware decoder/encoder evidence for the actual file

Failure means: Direct Play cannot validate the encoder; hardware decode does not alone prove hardware encode

Safe next step: Force a lower-resolution test and inspect both ends of the video pipeline.

Hardware boundary

Hardware and platform boundary

Change only when

Buy only after the current host demonstrably lacks your required codec or measured throughput.
Keep a NAS as storage and run the media service on a separate supported host when its CPU lacks a suitable GPU.

Evidence that matters

Exact codecs and bit depth, OS/container support, subtitle handling, HDR tone mapping, measured thermal/power limits and practical memory use.
Check NVIDIA’s current matrix for the exact card: T400 and T1000 list eight simultaneous encode sessions, rather than unlimited sessions.

Evidence that does not matter

A headline stream count without a reproducible workload.

Avoid

Do not assume every Synology Plus has an Intel GPU or that an i915 package repairs an AMD model.
Do not assume TrueNAS 24.10+ still uses Kubernetes Apps; do not copy older device-plugin instructions.

Last reviewed

2026-09-27 · Reviewed by HomeTechOps. Reviewed 2026-09-27 against Jellyfin, Plex, Synology, NVIDIA’s per-model matrix and TrueNAS 24.10 notes. Removed conflicting unconditioned stream counts, stale prices and the claim that all professional NVIDIA cards are uncapped. These are source-confirmed capabilities, not HomeTechOps hardware benchmarks.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Jellyfin Docs: Hardware AccelerationUsed for VideoToolbox hardware acceleration on macOS, and that hardware encode/decode needs direct media-engine access — which a Linux container on a Mac cannot reach, so keep the media server native.Jellyfin: Intel GPU hardware accelerationLinux render devices, numeric group permissions, official Docker image drivers, QSV and verification; Windows Docker/WSL boundary.Plex: Using hardware-accelerated streamingUsed for the rule that Plex hardware transcode requires an active Plex Pass plus a capable GPU (e.g. Intel Quick Sync); without it Plex falls back to CPU software transcoding.Synology: DS425+ and DS925+ model comparisonConfirms DS425+ Celeron J4125 and DS925+ Ryzen V1500B; do not conflate CPU families.NVIDIA: Video Encode and Decode GPU Support MatrixExact GPU codec support and session limits; T400/T1000 eight encode sessions at the 2026-09-27 review.TrueNAS: 24.10 release notesApps backend switched from Kubernetes to Docker in 24.10; procedures must match the installed release.

FAQ

How many 4K streams can an N100 or N150 handle?

There is no universal count. Codec, bitrate, HDR tone mapping, subtitles, driver/runtime, client and cooling change the result. Verify one forced hardware transcode, add your required features and clients, and retain the conditions with the measured result.

Can an Intel driver enable Quick Sync on DS925+?

No. Synology lists DS925+ with AMD Ryzen V1500B; it does not have an Intel Quick Sync GPU. Use direct play or a separate supported media host.

Are T400 and T1000 NVENC sessions unlimited?

No. NVIDIA’s current model-specific matrix lists eight simultaneous encode sessions for these cards. Throughput may be lower for demanding workloads, and other professional cards have different limits.

Do I need Plex Pass for hardware acceleration?

Plex’s hardware-accelerated streaming feature requires an active Plex Pass on the server owner account. Check Plex’s current feature documentation and purchase page for terms and local pricing. Jellyfin’s hardware acceleration does not require a subscription.

Planning a purchase?

We keep a source-backed, price-free comparison so you can buy once and right. No star ratings, every spec cited.

NAS for Plex & Jellyfin: transcoding →

Get the deal & firmware alerts

Home Stack Field Notes: NAS deals, firmware changes worth acting on, restore-test reminders, and new decision guides — plus the capacity & backup sizing cheatsheets from our calculators. Unsubscribe anytime.

Subscribe on beehiiv