Hardware video acceleration in Web browsers
Introduction[edit | edit source]
Hardware accelerated video makes it possible for the video card to decode/encode video, thus offloading the CPU and saving power.
This article gives detail on enabling hardware video acceleration in browsers used in Linux. This article details them for Firefox and Chromium, but similar instructions apply to other browsers based on the above two.
Firefox[edit | edit source]
Firefox currently supports hardware acceleration on both x11 and Wayland. This is tested on Firefox 96 (nightly). The following settings need to be changed in
media.ffmpeg.vaapi.enabled true gfx.webrender.all true media.ffvpx.enabled false
In addition, while running X11, Firefox should be launched with variable
MOZ_X11_EGL=1 . Also, users should ensure that vaapi is available by installing/running
vainfo in terminal. In cases where GPU only supports h.264 decode, its beneficial to install h.264ify.
- both 30fps/60fps or higher videos play smoothly at resolutions supported by GPU decoder.
- CPU usage is significantly reduced while playing videos
- The color of videos appears washed out. (0,0,0) is mapped to (16,16,16) and (255,255,255) to (235,235,235). Bug 1726186 (Fixed on Firefox 96+!)
- Nvidia users out of luck (for now)
Chromium[edit | edit source]
Chromium also supports hardware acceleration in x11 and Wayland. This too was tested in chromium-dev 97. To enable it, first set
disabled. Then launch chromium with the following flags:
--use-gl=desktop should not be required in Wayland, but the wiki editor couldn't get it to work without it. Also h.264ify will be required as stated above.
- both 30fps/60fps or higher videos play smoothly at resolutions supported by GPU decoder, unless Vulkan backend is enabled through flags. However there is little reason to enable it for now
- Videos are played color accurately
- CPU usage reduction is minimal. I could not observe significant improvement in reduction of CPU load or improved battery life ( on different machine) despite confirming that hardware video acceleration was working while playing videos
- Nvidia users out of luck again
Google chrome and other flavors[edit | edit source]
Same should work for google chrome (and other chromium-based browsers like Brave, Vivaldi, edge etc.)
There is a config file for google chrome located at $HOME/.config/chrome-flags.conf (if file does not exist, create it), where you can put flags that chrome should start with by default (because starting browser with parameters sometimes can be hard/pain).
Nvidia GPUs[edit | edit source]
For full GPU acceleration with Nvidia GPUs it's required to set 2 additional flags:
Optimizing performance[edit | edit source]
For better performance it is recommended to set 2 additional flags:
Epiphany/Gnome Web[edit | edit source]
Based on GTKwebkit, it provides another option for users that may be not as powerful as chrome or Firefox, but still fairly usable for modern web. To enable hardware accelerated video, first install
gstreamer-vaapi for AMD/Intel GPUs or
nvidia-utils for Nvidia GPUs. Then run:
gsettings set org.gnome.Epiphany.web:/ hardware-acceleration-policy 'always'
- both 30fps/60fps or higher videos play smoothly at resolutions supported by gpu decoder
- Videos are color accurate
- Works for Nvidia users
- Good reduction in CPU usage
- Lack of extensions
- No simple way to limit video codec to h.264, hence older GPUs will lack hardware video acceleration in most videos with codecs other than h.264
Alternatives[edit | edit source]
VLC and MPV both support proper hardware accelerated video in Linux. They can be set to launch when a video is played in a browser. This can be done in Firefox with Open in vlc or ff2mpv extension or other similar extensions. Similarly for chromium, Play with MPV or Play with VLC or similar.
- CPU utilization better than Firefox and chrome
- Videos are played with accurate colors
- Works for NVIDIA users
- Many sites with DRM (such as most paid streaming services) and those using custom video players may not work.