Windows How-To

Enable Hardware Acceleration in Browsers on Linux

Easy-to-follow instructions for activating hardware video acceleration in Firefox, Chromium, and other Linux browsers for smoother playback and lower CPU usage.

Easy-to-follow instructions for activating hardware video acceleration in Firefox, Chromium, and other Linux browsers for smoother playback and lower CPU usage.

by Pallav Pathak

Video streaming and conferencing in browsers often strain system resources on Linux, especially when hardware acceleration is not active. Hardware acceleration offloads video decoding tasks from the CPU to the GPU, resulting in smoother playback, lower power consumption, and quieter system fans. Activating this feature requires browser-specific settings and, in some cases, additional drivers or flags, depending on your hardware.

Enable Hardware Acceleration in Firefox

Open Firefox and navigate to the configuration page by entering about:config in the address bar. This page provides access to advanced browser settings.
In the search bar, enter media.ffmpeg.vaapi.enabled. Set this preference to true to allow Firefox to use VA-API (Video Acceleration API) for hardware video decoding. VA-API is the standard interface for GPU video decoding on Linux.
For older versions of Firefox or certain distributions, you may need to set gfx.webrender.all to true. This enables WebRender, which uses GPU for page rendering. Note that in recent releases, WebRender is enabled by default.
Restart Firefox to apply the changes. For users on Fedora or distributions with similar packaging, hardware video decoding is often enabled by default for Intel and AMD GPUs. To confirm, visit about:support and check the HARDWARE_VIDEO_DECODING entry.
If you experience issues with specific codecs (e.g., VP9 or AV1 on YouTube), consider installing the enhanced-h264ify extension. This extension allows you to force YouTube to use H.264, which is more widely supported by hardware decoders, especially on older GPUs.
For NVIDIA users, hardware video decoding in Firefox may require additional steps due to limited VA-API support. Install the nvidia-vaapi-driver and set environment variables NVD_BACKEND=direct MOZ_DISABLE_RDD_SANDBOX=1 when launching Firefox. Set media.ffmpeg.vaapi.enabled to true in about:config. Restart Firefox to activate hardware decoding with NVIDIA GPUs.
Verify GPU acceleration by playing a high-resolution video and monitoring system resource usage. Tools such as intel_gpu_top (for Intel) or radeontop (for AMD) can show GPU video engine activity during playback.

Enable Hardware Acceleration in Chromium-Based Browsers

Launch your Chromium-based browser (such as Google Chrome, Chromium, Brave, Vivaldi, or Edge) with specific flags to activate hardware video decoding. These flags instruct the browser to use GPU resources for video playback.
--use-gl=desktop --enable-accelerated-video-decode --enable-accelerated-video-encode --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder

For NVIDIA GPUs, add --ignore-gpu-blocklist --enable-zero-copy to the launch flags.

You can create or edit a configuration file to make these flags persistent. For Chrome, place them in $HOME/.config/chrome-flags.conf. For Chromium, use ~/.config/chromium-flags.conf. Each flag should be on a separate line. Example:
--use-gl=desktop
--enable-features=VaapiVideoDecoder
--ignore-gpu-blocklist
--enable-zero-copy
--enable-gpu-rasterization
--canvas-oop-rasterization
Restart your browser to apply the changes. To confirm hardware video decoding is active, visit chrome://gpu and check the Video Decode status. It should read “Hardware accelerated.”
If your browser still does not use GPU decoding, ensure all necessary video codecs are installed. On Ubuntu-based systems, run sudo apt install ubuntu-restricted-extras to add proprietary codecs.
For YouTube and other streaming sites, install the enhanced-h264ify extension to control which codecs are used for playback. This is especially useful if your GPU does not support VP9 or AV1 decoding.
Some users with AMD or Intel GPUs may find that hardware acceleration works out of the box, while others may need to experiment with different flag combinations. If you see errors like VaapiVideoDecoder: failed Initialize()ing the frame pool in logs or chrome://media-internals, try updating your graphics drivers or switching to a different browser version.
On Wayland sessions, hardware acceleration in Chromium may be less reliable. Consider using X11 for more consistent results or consult your distribution’s documentation for browser compatibility with Wayland.

Enable Hardware Acceleration in Epiphany/Gnome Web

Install the necessary backend for your GPU. For AMD and Intel, install gstreamer-vaapi. For NVIDIA, install gst-plugins-bad and nvidia-utils.
Enable hardware acceleration by running the following command in a terminal:
gsettings set org.gnome.Epiphany.web:/ hardware-acceleration-policy 'always'
Restart Epiphany to activate GPU video decoding. Verify playback performance by streaming a high-resolution video and observing CPU usage.

Alternative Approach: Using External Video Players

When browser-based hardware acceleration is unreliable, consider opening videos in external players like MPV or VLC, which have robust hardware decoding support on Linux. Extensions such as Open in VLC or ff2mpv for Firefox, and Play with MPV for Chromium, allow you to send video links directly to these players. This method delivers accurate colors and the lowest CPU usage, but may not work with DRM-protected content or custom web players.

Activating hardware acceleration in Linux browsers streamlines video playback, lowers CPU usage, and extends battery life. Testing different settings and browser versions helps pinpoint the best configuration for your hardware and distribution.

Keep reading

More from Windows

All Windows guides →