Linux Video Playback in 2026: Wayland, VA-API and HDR

Linux video playback spent about fifteen years being the thing you apologised for. In 2026 that is genuinely no longer true — but the pieces involved have opaque names, the advice online is a decade of contradictory forum posts, and it is hard to tell what applies to your machine.

I ship a Linux build, so I have had to learn this properly. Here is the current state of play, in the order that actually matters.

Hardware Decoding: What VA-API Is and Why You Want It

Hardware decoding means your GPU's dedicated video block does the decoding work instead of your CPU. The difference is not subtle: correct hardware decoding of a 4K stream might use a few percent of CPU, while software decoding the same stream can saturate several cores, spin the fans, and drain a laptop battery in ninety minutes. (The general explainer.)

On Linux, the interface to that hardware block is VA-API (Video Acceleration API). Historically there was also VDPAU, an older NVIDIA-oriented interface; in 2026 VA-API is what you should expect and target. If a guide is telling you to configure VDPAU, it is old.

What works where, broadly:

• Intel — the smoothest story. VA-API support is mature and generally works out of the box on any current distribution.
• AMD — very good. The open-source driver stack supports VA-API well, and it needs little intervention.
• NVIDIA — historically the difficult one, now substantially better with the proprietary driver plus a translation layer that exposes VA-API. Still the most likely to need attention.

Checking your own machine

Two commands tell you almost everything. Install your distribution's VA-API utilities package, then:

vainfo

That lists the codecs your GPU can decode in hardware. Look for entries mentioning H264, HEVC, VP9 and AV1. If vainfo errors out entirely, VA-API is not set up — usually a missing driver package.

Then, while playing something, run:

top

If your player is using a few percent of CPU, hardware decoding is working. If it is using several hundred percent, it is not, and vainfo will tell you whether that is because the codec is unsupported or because the setup is broken.

That is the whole diagnostic. Everything else is detail.

The AV1 line

AV1 is where hardware ages out. Recent GPUs across all three vendors decode it; older ones do not, and software AV1 decoding at 4K is not realistic on most machines.

Given AV1's growing share of streaming — roughly 30% of Netflix, over 75% of YouTube — this is the spec that determines whether a Linux machine stays comfortable. vainfo answers it definitively. (More on AV1 and device support.)

Wayland: Why It Mattered for Video

Wayland has now replaced X11 as the default display server on essentially every mainstream distribution, and for video this was a bigger deal than most users noticed.

X11 was designed in the 1980s for network-transparent windows on workstations. It had no concept of a compositor, no real concept of tearing-free presentation, and no way to describe colour beyond "here are some pixels". Everything modern video needs — proper synchronisation, direct scanout, colour metadata — was bolted on.

Wayland's presentation model is explicit about frame timing and buffer handover, which gives you three practical improvements:

• No tearing by default. The horizontal split during panning that used to require configuration is simply gone.
• Direct scanout. A fullscreen video can go straight from the decoder to the display, skipping the compositor entirely. Lower latency, less power.
• Fractional scaling that works, which matters on high-DPI laptops where X11 handled it badly.

The one real remaining rough edge is screen sharing, which needed an entirely new mechanism under Wayland's security model. That mechanism now exists and works, but a very old application may still not use it.

For pure playback, Wayland in 2026 is straightforwardly better. There is no video reason to seek out X11.

HDR: The 2026 Position

This is the area that changed most recently, and where expectations should still be calibrated carefully.

HDR on Linux was effectively impossible for years, because it needs every layer to cooperate: the decoder must preserve metadata, the compositor must understand colour spaces, the driver must set the display into HDR mode, and the application must ask for it. Any layer that does not participate collapses the whole chain back to SDR.

Through 2025 and 2026 those pieces landed. Wayland protocols for colour management were finalised, compositors implemented them, and drivers gained the necessary support. Kodi 22 "Piers" — in beta since June 2026 — ships a substantial rewrite of its Linux rendering path specifically to deliver end-to-end HDR, which is a good indicator of where the platform now is. (What's in Kodi 22.)

Where that leaves you in practice:

• HDR on Linux is now possible and working on current, up-to-date systems.
• It requires recent everything — kernel, driver, compositor and player. An LTS distribution from two years ago will not have the pieces.
• It is not yet the effortless experience it is on a games console or an Apple TV.
• Support varies by desktop environment, and the situation moves quarter to quarter.

If HDR is essential to you and you want zero configuration, a dedicated device still wins today. If you run a current system and enjoy the tinkering, it works.

Distribution and Packaging Choices That Affect Playback

A few Linux-specific things that catch people out.

Codec packages. Some distributions ship without patent-encumbered codecs by default, which means media that plays everywhere else fails on a fresh install. The fix is installing the relevant extras package, and every affected distribution documents it. This is the single most common "Linux can't play video" experience and it is a five-minute fix.

Flatpak and Snap sandboxing. Sandboxed applications need explicit permission to reach the GPU device nodes for hardware decoding. Packages are generally configured correctly, but if a Flatpak build software-decodes while the native package hardware-decodes, permissions are the first thing to check.

Wayland versus X11 session. Most distributions let you pick at the login screen. If you are chasing a video problem, trying the other session is a fast and informative test.

Multiple GPUs. Laptops with integrated plus discrete graphics can end up decoding on one and displaying on the other, which is slow and confusing. vainfo reporting a different GPU than you expected is the clue.

Why Linux Is a Good Media Machine Now

Beyond the technical state, the practical case is strong:

• It runs on hardware Windows 11 rejects. For a machine whose job is video, a TPM requirement is an arbitrary reason to bin working hardware. (What to do about Windows 10's end of support.)
• Updates continue indefinitely, with no support cliff.
• No advertising or content-recognition layer in the operating system. Compared with what smart TV platforms now do, this is a real difference. (How smart TV tracking works.)
• Low idle power, so leaving a small machine running costs very little.
• Real control over what runs and what starts at boot.

The catch remains that you are the systems administrator. That is a fair trade for a lot of people and a bad one for others.

Where Tuneline Fits

Tuneline is available for x86_64 Linux through Snap and Flathub, so it installs with one command on any mainstream distribution. You bring your own M3U, Xtream or portal source; it ships with no content of its own.

Two honest boundaries. There is no ARM64 build, so it does not run on a Raspberry Pi — use Kodi, VLC or mpv there. (Pi guide.) And it is a player for streams and playlists rather than a local file opener; for a stray MKV on your disk, VLC or mpv is the right tool. (Opening MKV files.)

Linux is a first-class target here rather than an afterthought — it is one of the platforms Tuneline is built and released for on every version, alongside macOS, Windows, iPhone, iPad, Android, Android TV, Google TV and Apple TV. Free, with optional Pro (lifetime $34.99) for cloud sync.

The Bottom Line

• VA-API is the hardware decoding interface. Run vainfo to see what your GPU actually supports, and top during playback to confirm it is being used.
• Intel is the smoothest, AMD is very good, NVIDIA is the one most likely to need attention.
• Wayland improved video meaningfully: no tearing, direct scanout, working fractional scaling.
• HDR on Linux works in 2026 on current systems, but still needs recent everything and is not effortless.
• Missing codec packages on a fresh install cause more "Linux can't play video" than anything technical.
• AV1 hardware decode is the line that separates future-proof machines from ones on a clock.

Running Linux? Download Tuneline from Snap or Flathub — free, no bundled content, and the same setup on every other device you own.