Google Chrome has following notable built-in features over Chromium:
- Flash player, also available via .
- Widevine EME for e.g. Netflix, also available via AUR.
- Native client (NaCl). Support for native client (NaCl) has been dropped from Chromium packages since version 54, see FS#51511.
See List of applications#Blink-based for other browsers based on Chromium.
- 1 Installation
- 2 Configuration
- 3 Tips and tricks
- 4 Troubleshooting
- 4.1 Fonts
- 4.2 Force GPU acceleration
- 4.3 WebGL
- 4.4 Incorrect HiDPI rendering
- 4.5 Password prompt on every start with GNOME Keyring
- 4.6 Chromecasts in the network are not discovered
- 4.7 Losing cookies and passwords when switching between desktop environments
- 4.8 Hang on startup when Google Sync enabled
- 5 See also
There are several packages available to install Chromium with:
- – stable release.
- AUR – development release.
- AUR – nightly build.
- VA-API support, for configuration see #Hardware video acceleration. AUR, AUR – packages 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.
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
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
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
Chromium uses Network Security Services for certificate management. Certificates can be managed in
Hardware video acceleration
Accelerated video decoding using VA-API is available on AUR and AUR.
- Verify VA-API has been enabled and working correctly.
- One may need to #Force GPU acceleration as Chromium uses a GPU blacklist by default.
- globally (all applications will be affected):
- or app-specific adding the variable to
chromium.desktopdesktop entry editing the
Exec=allow_rgb10_configs=false chromium %U
/usr/share/applications/and then modify the one locally at
To use hardware video acceleration:
- enable both
--enable-accelerated-mjpeg-decodeas arguments or append them to the persistent configuration.
--disable-gpu-driver-bug-workarounds has been tested and confirmed to remove video freezes (especially when watching in fullscreen).
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
Force GPU acceleration
To force GPU acceleration, enable the flags:
chrome://flags or append to the persistent configuration. 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.
For Native GpuMemoryBuffers the flag
--enable-native-gpu-memory-buffers needs to be pass or some optimizations (like the zero-copy rasterizer) will use software rendering. The flag isn't available under
chrome://flags and must be passed as a persistent flag or directly from the command line.
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.
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.