Choose the playback job first
For playback that already works without video conversion, try your existing PC first. For a new server that must convert video, start with a modern Intel N-series system and 8GB RAM. A processor's “i5” badge or a seller's “4K” claim is not enough to choose between them.
1. Find out what the server must change
| Playback mode | What happens | What it means for buying |
|---|---|---|
| Direct Play | The player accepts the original file | Little video-processing work for the server; check network and storage first |
| Remux / Direct Stream | The video is copied; the container or audio may change | Usually a lighter job than converting video |
| Video transcoding | The server creates a different video stream | Choose around hardware acceleration and the formats you need |
A video codec is the format, such as H.264, HEVC or AV1. An MKV or MP4 file is a container; the extension alone does not identify the video inside. Subtitles can force conversion too, especially when they must be drawn into the picture. See Jellyfin's codec guide.
2. Test three files before replacing a working PC
If you already run Jellyfin, use the actual TV, phone or browser you watch on:
- Play an ordinary film, your most demanding file, and a file with subtitles enabled.
- Check the playback information for Direct Play, Direct Stream or transcoding. Note which file and player cause conversion.
- For a troublesome file, try another audio track, turn subtitles off briefly, or try another supported player. If that removes video conversion, you may be able to keep the server.
- Repeat under the conditions that matter: two viewers together, or remote playback at the bandwidth you expect to have.
No existing server to test? Look up your player in the codec guide and plan for transcoding wherever support is uncertain. Do not buy a direct-play-only setup while assuming every future client will accept your files.
If HDR or subtitles cause buffering
Change one thing at a time, using the same file and player. Record the playback mode before and after each test. These checks help separate a buying problem from a setup problem:
| What you observe | Try this next | What the result tells you |
|---|---|---|
| Smooth with subtitles off; video transcoding with them on | Try a compatible text subtitle track, or a player that supports the original subtitle format | If video conversion stops, the subtitle/client combination was the trigger; a faster server may not be necessary |
| An HDR file transcodes for an SDR screen | Check that HDR-to-SDR tone-mapping is configured and accelerated | Tone-mapping is an extra processing stage; the ability to decode HEVC alone does not prove the whole job is accelerated |
| Direct Play still buffers | Try the same file over wired networking and check storage access | With no video conversion, investigate delivery and the player before spending on a transcoding upgrade |
| Playback works locally but buffers remotely | Compare the remote quality limit with the connection's usable upload speed; test a lower bitrate | Remote bandwidth limits can create a different workload from your living-room test |
Turning subtitles off is a diagnostic step, not a permanent solution if you need them. Jellyfin explains why unsupported subtitles may have to be burned into the video. Retest with the subtitles you actually use before keeping or returning a machine.
For HDR, Jellyfin documents separate decoding, tone-mapping and encoding stages; some can fall back to software. If enabling acceleration causes errors, check the transcoding log and the setup instructions for your OS. More RAM is not evidence that these stages will work.
Want to keep HDR on an HDR screen?
Test the exact file in your intended app on that display. An HDR-capable TV alone does not establish that its app accepts the file's codec, HDR format, audio and subtitles. Use Jellyfin's client compatibility guide and check the reported playback mode.
Jellyfin's transcoding documentation says HDR video conversion produces SDR with tone-mapping; it does not preserve HDR metadata through that conversion. A faster transcoder therefore does not by itself keep HDR output. If preserving HDR matters, first try a compatible client or subtitle/audio track that avoids video conversion. Repeat with your normal remote quality limit, which can change the playback mode.
Check AV1 input and output separately
Write down the codec in your file and the codec your player needs. They can require different GPU capabilities:
| Your playback job | What to verify before buying |
|---|---|
| The player accepts the original AV1 file | Test Direct Play on that player; the server need not create a new video stream |
| Convert an AV1 file to H.264 | Hardware decoding for AV1 and encoding for H.264 |
| Create an AV1 output stream | Explicit AV1 hardware encoding support |
Jellyfin lists separate Intel requirements for AV1 decoding and encoding. A GPU that can decode AV1 may have no AV1 encoder. If AV1 output is essential, choose hardware documented for that job; an N100/N150 recommendation for general video conversion does not establish it. During the return period, force your intended conversion and check the playback information and transcoding log for the actual input/output codecs.
3. Buy for the result
- Your files direct-play: compare a complete refurbished machine such as the HP 400 G5 Mini, i5-8500T, 8GB RAM and 256GB SSD. Its seller listed £149.99 and stock on 21 October; confirm current availability and the VAT-inclusive total. Keep the media library separate from the system SSD and test your actual players.
- You need video conversion or have mixed clients: investigate an N100/N150-class machine. The AIR12 Lite N150 is our catalogue example; confirm its final VAT-inclusive price before comparing offers.
- You need several simultaneous 4K HDR conversions: establish that exact workload before ordering. This shortlist has no measured result that proves a particular machine can handle it.
For a new purchase, Jellyfin now advises considering newer integrated graphics over Intel's 7th–10th generations, because support for the older toolkit is declining. It still considers existing machines in those generations usable. That is why our used-PC suggestion is aimed at known direct playback.
4. Check acceleration during the return period
Follow Jellyfin's Intel setup instructions for your operating system. Enable the supported acceleration method and codecs; a container installation also needs access to the graphics device. Buying the right chip does not configure this for you.
Buying an N150 for Linux? Jellyfin's known-issues page specifies Linux 6.9 or newer for its integrated graphics. Check the installed host kernel with uname -r; a newer container image does not update the host kernel. Use a currently supported distribution/kernel, not an obsolete release chosen only to meet that minimum.
To verify acceleration deliberately, temporarily select a lower playback bitrate or resolution so video conversion is required. On Windows, inspect the GPU's video-engine activity in Task Manager; on Linux, follow the verification steps in the Intel guide. A ticked settings box alone is not confirmation.
Repeat the same sample files, subtitles and simultaneous sessions. If playback buffers, use the reported playback mode to decide whether to investigate the network or conversion setup. Do not solve every playback problem by buying a faster CPU.
Sources and review date
Source dates are listed below. Recommendations are our editorial judgement; we have not physically tested these machines.
- Jellyfin: hardware selection ↗ · 18 Sept 2026
- Jellyfin: codec support ↗ · 28 Oct 2026
- Jellyfin: Intel GPU acceleration ↗ · 12 Oct 2026
- Jellyfin: hardware acceleration and tone-mapping ↗ · 18 Sept 2026
- Jellyfin: acceleration known issues and Linux requirements ↗ · 18 Sept 2026
- Root Refurb: exact HP ProDesk 400 G5 Mini offer ↗ · 21 Oct 2026
- Jellyfin: HDR-to-SDR transcoding behaviour ↗ · 28 Oct 2026