Raspberry Pi 5 as a Media Player: The 2026 Setup Guide

The Raspberry Pi has been the default answer to "cheap Linux media box" for over a decade. The Pi 5 changed that calculation in a way most guides still have not caught up with, and if you build one without knowing about it you will be confused by your own results.

Here is the honest version: what changed, what it means for what you should run, and whether a Pi 5 is actually the right thing to buy for this job in 2026.

The Thing You Need to Know First

The Pi 5 removed hardware H.264 decoding. The Pi 4 had a dedicated hardware block for it. The BCM2712 in the Pi 5 does not — the legacy codec blocks were dropped, leaving a Pi-developed HEVC decoder.

So on a Pi 5:

• HEVC / H.265 — hardware decoded, up to 4K.
• H.264 — software decoded on the CPU.
• AV1 — software only, and realistically not viable at high resolutions.
• VP9 — software.

This sounds alarming and mostly is not, because the Pi 5's quad-core Cortex-A76 is dramatically faster than the Pi 4's CPU and handles 1080p H.264 in software comfortably. Reports of 4K H.264 playing are common, though that is much closer to the limit and depends heavily on bitrate.

But the shape of the machine has changed, and it matters:

• 1080p H.264 content: fine. This is the majority of live streams.
• 4K HEVC content: fine, and hardware accelerated. This is the Pi 5's best case.
• High-bitrate 4K H.264: marginal. Expect dropped frames and a hot device.
• AV1: do not plan around it.

The counter-intuitive consequence: a Pi 5 is better at 4K HEVC than at 4K H.264. That inverts the usual assumption that the older, simpler codec is the safe one. (Hardware vs software decoding, and how to tell which you're getting.)

Should You Buy a Pi 5 For This?

Let me be genuinely useful rather than enthusiastic.

A Pi 5 build costs more than you think. Board, official power supply (the Pi 5 is fussy about power and will throttle or fail on an inadequate one), case with active cooling (it throttles without it), microSD or NVMe storage, and an HDMI cable. Realistically you are at or above the price of a Google TV Streamer or an NVIDIA Shield once you total it.

A dedicated streaming box will be better at being a streaming box. It boots instantly, has a remote that works, wakes the TV over HDMI-CEC without configuration, and gets tested against streaming services. (What to look for in one.)

So buy a Pi 5 for this if:

• You want a machine that also does other things — home automation, network services, a file server.
• You specifically want a fully open, Linux system you control end to end.
• You already own one.
• The building is part of the appeal. That is a completely legitimate reason.

Buy a streaming box instead if you just want video on the television with minimum fuss. There is no shame in that and it will be the better experience.

I say this as someone who likes Pis. Choosing the right tool matters more than defending the interesting one.

The Hardware Build

Board: Pi 5, 4 GB or 8 GB. 4 GB is plenty for media; 8 GB matters only if the machine has other jobs.

Power: the official 27 W USB-C supply. This is not an upsell. The Pi 5 has real power requirements and an inadequate supply produces mysterious instability that looks like software problems for weeks.

Cooling: mandatory. The Pi 5 throttles under sustained load without it, and software H.264 decoding is exactly sustained load. The official active cooler or a case with a fan. A passive heatsink alone is not enough for continuous video.

Storage: an NVMe drive via the M.2 HAT is transformatively faster than microSD and worth it if the Pi has other jobs. For pure media playback, a good A2-rated microSD is adequate — you are streaming, not reading from disk.

Network: use Ethernet. The Pi 5 has gigabit Ethernet, and a live stream is the least forgiving thing on a network. Wi-Fi works; Ethernet removes an entire class of intermittent problem. (Whether Ethernet actually helps in your case.)

Remote: an HDMI-CEC-capable TV lets you drive it with the TV remote, which is the single biggest quality-of-life improvement available. Failing that, a cheap USB or Bluetooth media remote.

The Software

Three approaches, in order of how appliance-like they feel.

Option A: A dedicated media-centre OS

Image the SD card with a purpose-built distribution, boot, and you have a media centre. No desktop, no maintenance, and it starts straight into the interface.

Pros: simplest possible result, tuned for the hardware, boots to the thing you want. Cons: it is a media centre and not much else. If you wanted the Pi to do other jobs, this is the wrong route.

Option B: Raspberry Pi OS plus a player

Install the standard desktop OS and add whichever player you prefer. The Pi becomes a small Linux computer that also plays video.

Pros: the Pi remains general-purpose. Full package availability. Cons: you are maintaining a desktop system. Boots to a desktop rather than to your content unless you configure autostart.

For a living-room build, set your player to launch automatically at boot and hide the desktop. That closes most of the gap to Option A.

Option C: Headless server plus a client elsewhere

Run the Pi as a media server — Jellyfin, for instance — and watch on other devices. This is the Pi's genuinely strongest role, because serving files does not require decoding them. (How home media servers fit together.)

Note the Pi 5's decoding limits apply to transcoding too. It can transcode, but do not expect it to serve several simultaneous transcoded 4K streams. Direct play, where clients handle their own decoding, is what a Pi serves well.

Making It Feel Like an Appliance

The difference between a Pi that gets used and one that ends up in a drawer is almost entirely these details.

Auto-start the player at boot. Nobody wants to see a desktop and open an app to watch television.

Enable HDMI-CEC so the TV remote drives it and the TV wakes it.

Disable screen blanking, or the display sleeps mid-programme.

Set the audio output correctly. HDMI audio on the Pi needs to be selected explicitly and is a frequent source of "no sound". (No sound fixes.)

Fix its IP address via a router DHCP reservation, so you can always reach it.

Turn off unnecessary services. Every background process is CPU you need for software decoding.

Realistic Expectations

What a well-built Pi 5 media box actually does:

That is a capable machine with a specific weak spot. Know the weak spot and it is fine.

Which Player to Run — and Where Tuneline Doesn't Fit

Straight answer, because I would rather lose the click than mislead you: Tuneline has no Raspberry Pi build. Our Linux packages are compiled for x86_64, and a Pi is ARM (aarch64), so they will not run on it. If and when we ship an ARM64 build, I will update this article. Until then, point your Pi at software built for ARM.

Which, fortunately, is well served:

• Kodi is the default for a Pi media centre, ships for ARM, and is what the purpose-built media-centre distributions are built around. If you want the appliance experience, this is the route. (What's new in Kodi 22.)
• VLC is in the Raspberry Pi OS repositories and opens essentially anything, including awkward local files.
• mpv is the lightest option and the best behaved for pure playback, though it needs a front-end to be living-room friendly.

Where Tuneline is still relevant to a Pi household is the rest of the house. If you run the Pi as a Jellyfin server (Option C above), you need clients on your other screens — and Tuneline runs on macOS, Windows, x86_64 Linux, iPhone, iPad, Android, Android TV, Google TV and Apple TV, playing the stream URLs your server publishes. It is free, ships with no content of its own, and optional Pro (lifetime $34.99) syncs the same setup across those devices.

That is the honest boundary. The Pi runs Kodi or VLC; everything else in the house can run whatever you like.

The Bottom Line

• The Pi 5 has no hardware H.264 decoder. HEVC is hardware accelerated; H.264 runs on the CPU.
• 1080p H.264 is comfortable; 4K HEVC is its best case; high-bitrate 4K H.264 is marginal; AV1 is out.
• Active cooling and the official 27 W supply are not optional. Most "mysterious Pi problems" are one of those two.
• Ethernet over Wi-Fi for live content.
• A Pi is the right choice if it has other jobs or you want to build it. A streaming box is better at only being a streaming box.
• Its strongest role may be as a server, not a client.
• Tuneline has no ARM build, so run Kodi, VLC or mpv on the Pi itself. (The fuller Pi player guide.)

Using the Pi as a server? Download Tuneline for the screens around it — macOS, Windows, x86_64 Linux, iPhone, iPad, Android, Android TV, Google TV and Apple TV. Free, with no bundled content.