
Illustration of the same library playing on two different screens.
An Intel N100 can read an AV1 movie in hardware and send H.264 video to an older tablet. Ask the same machine to create an AV1 copy and the answer changes. Before replacing a media server, write down the codec of one troublesome file and the codec the player actually requests. The first tells you which decoder you need. The second identifies the encoder.
Match the file to the graphics engine
These rows cover ordinary 4:2:0 video. The HEVC columns cover both directions, reading and writing. The AV1 columns separate them because several popular mini PCs gained the decoder a generation or more before the encoder. Look up the integrated graphics fitted to your exact processor. A Ryzen 7000 label alone does not identify its media engine.
| Integrated graphics | HEVC 8-bit | HEVC 10-bit | AV1 decode | AV1 encode |
|---|---|---|---|---|
| Intel HD 530, Skylake | Both | No full hardware path | No | No |
| Intel HD 630, Kaby Lake | Both | Both | No | No |
| Intel UHD on N100 or N150 | Both | Both | Yes | No |
| Intel Arc graphics on Core Ultra 5 125H | Both | Both | Yes | Yes |
| Radeon Vega on Ryzen 5 5500U | Both | Both | No | No |
| Radeon 680M on Ryzen 7 6800H | Both | Both | Yes | No |
| Radeon 780M on Ryzen 9 7940HS | Both | Both | Yes | Yes |
| Radeon 890M on Ryzen AI 9 HX 370 | Both | Both | Yes | Yes |
Jellyfin documents full HEVC Main 10 acceleration from Kaby Lake in the Intel Core family. Intel’s Tiger Lake graphics added AV1 decoding. Meteor Lake integrated Arc graphics added encoding. On AMD, the 680M and 780M differ precisely where a library conversion job cares most. Both read AV1, but only the 780M of those two can write it in hardware. Jellyfin Intel media capabilities and Jellyfin AMD media capabilities.
The 890M row follows AMD’s mapping of Strix Point to VCN 4. Confirm the profiles on the installed driver before buying for a particular output format. Intel also publishes separate decode and encode columns by platform. AMD video engine table and Intel media driver capabilities.
A camera original marked HEVC 4:2:2 falls outside this table even when its bit depth is ten. A Dolby Vision or HDR10 label also adds a separate question. If the destination screen needs SDR, the server may have to tone-map the picture between decode and encode. For a choice between two newer Ryzen machines, our Radeon 890M and 780M comparison covers the graphics differences beyond these yes-or-no codec cells.
Read one file and follow one playback session
Start with a file that causes trouble on a specific player. FFprobe can report its video track without changing the file. Replace the filename and run this wherever you can read the original.
ffprobe -v error -select_streams v:0 \
-show_entries stream=codec_name,profile,pix_fmt,width,height,color_transfer \
-of default=noprint_wrappers=1 "movie.mkv"
For example, codec_name=hevc, profile=Main 10 and pix_fmt=yuv420p10le identify a ten-bit 4:2:0 HEVC input. The first two fields alone miss the chroma format. A transfer characteristic of smpte2084 identifies PQ. An unknown transfer characteristic leaves HDR handling unresolved. FFprobe documentation.
- Play at original quality. Check the server dashboard. Direct Play hands the file to the client. A remux can change the container while copying the same video. An audio-only conversion also leaves the video encoder idle.
- Force video conversion on that same client. Select a lower resolution or bitrate. Record the output codec and the server’s reason for transcoding. A player that cannot display a subtitle format may ask the server to burn text or images into every frame. Repeat once with subtitles off to isolate that cost.
- Check what the server can open. On Linux, run
vainfo --display drm --device /dev/dri/renderD128with the media service’s permissions, substituting its actual render node. Look for the matching profile withVAEntrypointVLDfor decode and an encode entry such asVAEntrypointEncSliceorVAEntrypointEncSliceLPfor output. In a container, a successful host check tells you little about the guest’s permissions. Follow the Jellyfin render-device walkthrough for that case. - Read the transcode log for that play. In Jellyfin, check the input hardware initialization and the selected output encoder. An encoder such as
h264_qsvorh264_vaapiidentifies hardware H.264 output. A software encoder such aslibx264can still follow a hardware decoder. Check for a fallback or a second invocation after an error before calling the accelerated path successful.
Work through an older tablet and a newer TV
Suppose the TV accepts a 10-bit AV1 film directly. The mini PC delivers bytes from disk, so replacing an older Vega box with an AV1-capable iGPU changes little for that session. Now take the same film to a tablet that requests H.264 at a lower bitrate. The server must decode AV1, scale the frames and encode H.264. An N100 has the two codec engines this path needs. The absence of an AV1 encoder has no bearing on that output.
Change the job to converting a shelf of HEVC films into smaller AV1 files and the missing encoder matters. A 680M can read those films and play the finished files, yet the conversion itself would need software AV1 encoding or another device. Before committing an entire library, convert a sample, compare a dark or fast-moving scene at your intended settings, and keep the original until your actual clients can play the result.
When to keep the mini PC you have
If the troublesome film plays directly on every other screen, try a compatible client or subtitle track before buying hardware. If several remote users need conversion, collect a representative session with HDR and subtitles enabled. Fill in the transcode calculator for an estimate and confirm playback on your own mix. A supported codec does not establish simultaneous stream capacity.
For hardware selection, the Jellyfin mini PC guide and Plex mini PC guide cover complete systems. Plex has its own platform, subscription and output-format requirements. A driver advertising AV1 encode does not promise that Plex will choose it for streaming. Plex hardware-accelerated streaming requirements.
Frequently Asked Questions
Can an Intel N100 or N150 transcode AV1 to H.264?
Yes. Its integrated graphics can decode common AV1 video and encode H.264. Confirm the driver, the media server and the client select that path.
Which older Intel Core graphics handle 10-bit HEVC?
Kaby Lake integrated graphics such as HD 630 support full hardware decode and encode for ordinary HEVC Main 10 video. Skylake HD 530 handles eight-bit HEVC but lacks that full ten-bit path.
Does the Radeon 680M have an AV1 encoder?
No. The 680M can decode AV1. The Radeon 780M and 890M also have AV1 hardware encoders.
Does Direct Play need an AV1-capable server GPU?
No. The player decodes the video during Direct Play. Check its codec and profile support before changing the server.
Why does CPU usage rise with hardware acceleration enabled?
Software decoding, subtitle burn-in, tone mapping or software encoding can still occupy the CPU. Compare logs for the same scene with subtitles on and off and check both ends of the conversion.
