Open chrome and go type
chrome://flagsin the address bar.
Search for “video decode”
Change “Hardware-accelerated video decode” from “Disabled” to “Enabled”
Another way to enable these flag features is creating a config file called
~/.config/chrome-flags.conf for chrome or
For example here is mine:
~ $ cat ~/.config/chromium-flags.conf --ignore-gpu-blocklist --disable-gpu-driver-workarounds --enable-gpu-rasterization --enable-accelerated-video-decode
Open Firefox and type
about:configin the address bar.
Click “Accept the Risk and Continue” (don’t worry the risk here is very minimal)
Search for “vaapi”
Change “media.ffmpeg.vaapi.enable” from false to true.
What is hardware acceleration
Hardware acceleration refers to using a GPU to render/playback video rather than the CPU.
Almost all user-facing computers these days have a GPU of some sort. Laptop CPUs often have “integrated graphics”, which means there is a portion of the chip specifically designed for graphics output. On desktops, there can also be “integrated graphics” built into the motherboard. Then there is discrete or dedicated graphics, which is an external standalone card.
Why is it disabled by default on Linux
On Windows and MacOS, hardware acceleration on browsers is enabled by default and works fine out the box, so why is this not the case on Linux?
IMO: The reasons for doing this come from the support and engineering side more than the technical implementation – which has been largely finished since 2017. There are plenty of hardware-accelerated programs that run fine on Linux, but they add much more complexity when something breaks.
Enabling this by default could definitely break video playback for some users and cause other issues that would be costly for engineers to troubleshoot/debug/fix.
As a result, these “extra features” are often hidden behind a flag and tagged as experimental, even though they are probably stable enough for the majority of users.