Google Chrome has following notable built-in features over Chromium:
- Widevine EME for e.g. Netflix, also available via AUR.
- Flash player, also available via . (will be removed in December 2020)
- Native client (NaCl). (will be removed in June 2021)
See List of applications/Internet#Blink-based for other browsers based on Chromium.
- 1 Installation
- 2 Configuration
- 3 Tips and tricks
- 4 Troubleshooting
- 4.1 Fonts
- 4.2 WebGL
- 4.3 Incorrect HiDPI rendering
- 4.4 Password prompt on every start with GNOME Keyring
- 4.5 Chromecasts in the network are not discovered
- 4.6 Losing cookies and passwords when switching between desktop environments
- 4.7 Hang on startup when Google Sync enabled
- 4.8 Chromium asks to be set as the default browser every time it starts
- 4.9 Video decoding corruption or distortion
- 5 See also
There are several packages available to install Chromium with:
- — stable release;
- AUR — development release;
- AUR — nightly build;
- Hardware video acceleration support enabled; AUR — stable release with
- Wayland support enabled. AUR — stable release with
Google Chrome packages:
- AUR — stable release;
- AUR — beta release;
- AUR — development release.
To set Chromium as the default browser and to change which applications Chromium launches when opening downloaded files, see default applications.
Chromium uses Network Security Services for certificate management. Certificates can be managed in
Widevine Content Decryption Module plugin
Widevine is Google's Encrypted Media Extensions (EME) Content Decryption Module (CDM). It is used to watch premium video content such as Netflix. It is automatically installed when using Google Chrome.
To install it for Chromium, install the AUR package. Make sure Allow sites to play protected content is checked in
Force GPU acceleration
--ignore-gpu-blacklist --enable-gpu-rasterization --enable-native-gpu-memory-buffers --enable-zero-copy
Additionally the flag
--disable-gpu-driver-bug-workarounds may need to be passed to prevent GPU workaround from being used. Flags in
chrome://gpu should state "Hardware accelerated" when configured and available.
Hardware video acceleration
Before trying VA-API support in Chromium be sure to:
- Install correct VA-API driver for your video card and verify VA-API has been enabled and working correctly, see Hardware video acceleration;
- Install Unofficial user repositories#archlinuxcn; AUR or get compiled version from
- One may need to #Force GPU acceleration as Chromium uses a GPU blacklist by default;
chrome://gpuVideo Decode field.
To check if it's working play a video which is using a codec supported by your VA-API driver (vainfo tell you which codecs are supported) go to
chrome://media-internals/ and check video_decoder field:
- Hardware accelerated: MojoVideoDecoder, GpuVideoDecoder;
- In-software decoding: VpxVideoDecoder, FFmpegVideoDecoder.
PDF viewer plugin
Chromium and Google Chrome are bundled with the Chromium PDF Viewer plugin. If you don't want to use this plugin, check Open PDFs using a different application in
Flash Player plugin
Flash Player is automatically installed when using Google Chrome.
To install it for Chromium, install the package.
Make sure Flash is allowed to run in
Tips and tricks
See the main article: Chromium/Tips and tricks.
Font rendering issues in PDF plugin
To fix the font rendering in some PDFs one has to install the reported on the chromium bug tracker by an Arch user.package, otherwise the substituted font causes text to run into other text. This was
Font rendering issues of UTF characters
UTF characters may render as boxes (e.g. simplified Chinese characters). Installingwill allow for the characters to be rendered as expected.
Tab font size is too large
Chromium will use the GTK settings as described in GTK#Configuration. When configured, Chromium will use the
gtk-font-name setting for tabs (which may mismatch window font size). To override these settings, use
There is the possibility that your graphics card has been blacklisted by Chromium. See #Force GPU acceleration.
If you are using Chromium with Bumblebee, WebGL might crash due to GPU sandboxing. In this case, you can disable GPU sandboxing with
optirun chromium --disable-gpu-sandbox.
chrome://gpu/ for debugging information about WebGL support.
Chromium can save incorrect data about your GPU in your user profile (e.g. if you use switch between an Nvidia card using Optimus and Intel, it will show the Nvidia card in
chrome://gpu even when you're not using it or primusrun/optirun). Running using a different user directory, e.g,
chromium --user-data-dir=$(mktemp -d) may solve this issue. For a persistent solution you can reset the GPU information by deleting
Incorrect HiDPI rendering
Chromium will automatically scale for a HiDPI display, however this may cause an incorrect renderend GUI.
--force-device-scale-factor=1 may be used to overrule the automatic scaling factor.
On Wayland, theAUR package will automatically scale based on the configured scale of each monitor.
Password prompt on every start with GNOME Keyring
Chromecasts in the network are not discovered
You will need to enable the Media Router Component Extension in
If you see the message
Failed to decrypt token for service AccountId-* in the terminal when you start Chromium, it might try to use the wrong password storage backend. This might happen when you switch between Desktop Environments.
Hang on startup when Google Sync enabled
Try launching Chrome with
--password-store=basic or another appropriate password store.
Chromium asks to be set as the default browser every time it starts
If you are using KDE and have once set Firefox as the default browser (by clicking the button inside Firefox), you might find Chromium asks to be set as the default browser every time it starts, even if you click the "set as default" button.
Chromium checks for this status by running
xdg-settings check default-web-browser chromium.desktop. If the output is "no", it is not considering itself to be the default browser. The script
xdg-settings checks for the following MIME associations and expect all of them to be
x-scheme-handler/http x-scheme-handler/https text/html
To fix it, go to System settings > Applications > Default applications > Web browser and choose Chromium. Then, set the MIME association for
$ xdg-mime default chromium.desktop text/html
Finally, update the MIME database:
$ update-mime-database ~/.local/share/mime