Install Google Chrome on Fedora 43/42/41/40 [Guide]

Google Chrome is the most widely used web browser, and installing it on Fedora is straightforward once you know the proper steps. This guide walks you through adding the official Google repository, installing Chrome via DNF, verifying the installation, and tuning it for best performance on Fedora 43, 42, 41, or 40.

Original content from computingforgeeks.com - post 115

Prerequisites

Before you begin, make sure you have:

A working Fedora 43, 42, 41, or 40 installation with a desktop environment
A user account with sudo privileges
An active internet connection

Step 1: Add the Google Chrome Repository

Google maintains an official YUM/DNF repository for Chrome. Adding it ensures you receive updates through the standard Fedora package manager. Create the repo file:

sudo tee /etc/yum.repos.d/google-chrome.repo <<'EOF'
[google-chrome]
name=Google Chrome
baseurl=https://dl.google.com/linux/chrome/rpm/stable/x86_64
enabled=1
gpgcheck=1
gpgkey=https://dl.google.com/linux/linux_signing_key.pub
EOF

This creates a repository definition pointing to Google’s stable channel for 64-bit RPM packages. The GPG key is included so DNF can verify package signatures automatically.

Step 2: Install Google Chrome

With the repository in place, install the stable version of Chrome:

sudo dnf install -y google-chrome-stable

DNF will pull in any required dependencies, import the GPG key on first use, and install the browser. If you want the beta or development builds instead, replace google-chrome-stable with google-chrome-beta or google-chrome-unstable.

Step 3: Verify the Installation

Confirm that Chrome installed correctly by checking its version:

google-chrome --version

You should see output similar to:

Google Chrome 131.0.6778.85

You can also launch Chrome from the terminal to check that it opens without errors:

google-chrome &

If the browser window appears, you are good to go.

Step 4: Set Chrome as the Default Browser

Fedora ships with Firefox as the default browser. To switch the system default to Chrome, use the xdg-settings command:

xdg-settings set default-web-browser google-chrome.desktop

Verify the change:

xdg-settings get default-web-browser

The output should return google-chrome.desktop. Chrome will also prompt you to set it as default on its first launch if it detects another browser is configured.

Step 5: Managing Chrome Profiles

Chrome profiles let you maintain separate browsing environments – useful if you share a machine or want to keep work and personal browsing apart. To manage profiles:

Click the profile icon in the top-right corner of the Chrome window.
Select Add to create a new profile.
Choose a name, color theme, and optionally sign in with a Google account.

Each profile gets its own bookmarks, history, extensions, and saved passwords. Profile data is stored under ~/.config/google-chrome/. If you need to launch Chrome with a specific profile from the terminal, use:

google-chrome --profile-directory="Profile 1"

Step 6: Enable Hardware Acceleration

Hardware acceleration offloads rendering tasks to your GPU, improving performance for video playback and graphics-heavy pages. To check its status, navigate to:

chrome://gpu

Look for the Graphics Feature Status section. If items show as “Software only,” hardware acceleration may be disabled. To enable it:

Go to Settings – System.
Toggle Use graphics acceleration when available to on.
Relaunch Chrome.

On Fedora with Mesa drivers (Intel, AMD), hardware-accelerated video decode may require additional configuration. Visit chrome://flags and enable the following flags for VA-API support:

chrome://flags/#enable-accelerated-video-decode

After toggling the flag, relaunch Chrome and check chrome://gpu again to confirm the changes took effect.

Chrome on Wayland vs X11

Fedora defaults to Wayland on GNOME. Chrome supports Wayland natively, but there are situations where you might want to control this behavior. Check which display server you are running:

echo $XDG_SESSION_TYPE

If the output is wayland, Chrome should automatically use the Wayland backend in recent versions. To force a specific backend, launch Chrome with the --ozone-platform flag:

# Force Wayland
google-chrome --ozone-platform=wayland

# Force X11 (via XWayland)
google-chrome --ozone-platform=x11

To make this permanent, edit the Chrome desktop file or create a local override at ~/.config/chrome-flags.conf:

echo "--ozone-platform=wayland" > ~/.config/chrome-flags.conf

Wayland provides smoother scrolling and better HiDPI support. However, if you experience screen sharing issues in video calls, switching to X11 can help as some applications still handle X11 screen capture more reliably.

Useful Chrome Flags

Chrome flags let you enable experimental features or fine-tune behavior. Access them at chrome://flags. Some flags worth knowing on Fedora:

#enable-parallel-downloading – Splits downloads into multiple streams for faster transfers.
#smooth-scrolling – Enables or disables animated scrolling.
#enable-quic – Enables the QUIC protocol for faster connections to supported servers.
#enable-gpu-rasterization – Offloads page rasterization to the GPU.

Be cautious with flags – they are experimental and can cause instability. If Chrome behaves oddly after changing flags, reset them all by clicking Reset all at the top of the flags page.

Chromium as an Alternative

If you prefer an open-source browser without Google’s proprietary components, Chromium is available in the Fedora repositories:

sudo dnf install -y chromium

Chromium shares Chrome’s rendering engine and supports most of the same extensions, but it lacks built-in Flash (deprecated), automatic updates from Google, and certain media codecs. For most system administration tasks, Chromium works just as well. The main difference for everyday use is that some DRM-protected streaming services may not work in Chromium without additional codec packages.

Keeping Chrome Updated

Since we added the official repository, Chrome updates arrive alongside regular system updates:

sudo dnf upgrade --refresh

To update only Chrome:

sudo dnf upgrade google-chrome-stable

Uninstalling Google Chrome

If you decide to remove Chrome, uninstall the package and clean up the repository:

sudo dnf remove google-chrome-stable
sudo rm /etc/yum.repos.d/google-chrome.repo

To also remove your profile data, bookmarks, and cached files:

rm -rf ~/.config/google-chrome
rm -rf ~/.cache/google-chrome

Verify the removal:

rpm -q google-chrome-stable

The output should confirm the package is not installed.

Conclusion

Installing Google Chrome on Fedora takes just a few commands once you add the official repository. With the repo in place, DNF handles all future updates automatically. Taking a few minutes to configure hardware acceleration, Wayland settings, and useful flags gives you a faster, more polished browsing experience on Fedora. And if you ever want a fully open-source option, Chromium sits right there in the default repositories.