How to Install Google Chrome on Fedora 41+ Using DNF5

Google Chrome has been my go to browser for as long as I can remember. It is fast, it stays out of my way, and everything I do online just works, whether that is checking email, hopping between Google Docs and Sheets for work, or keeping dozens of tabs open without my laptop fan spinning up. If you are running Fedora 41 or newer, you are also on DNF5, Fedora’s modern package manager, and here is the good news: getting Chrome installed is surprisingly quick once you know the steps.

I remember my first time doing this on a fresh Fedora install. I spent longer than I would like to admit figuring out that the repository had to be enabled before the install would even find the package. So this guide is written the way I wish someone had explained it to me back then, plain and simple. In a few minutes, you will have Chrome installed, launched, and set as your default browser.

🛠️ Prerequisites

Before we get into the fun part, let us make sure everything is ready. These checks take less than a minute, and they save you from confusing errors a few steps down the road.

• You’re using Fedora 41 or later. This guide relies on DNF5, which ships as the default package manager on Fedora 41 and newer. If your system is older than that, some of the commands will look a bit different, so it is worth double checking your version first.
• You have sudo privileges. Installing software touches system wide settings, so your user account needs admin rights. On most Fedora installs, the account you created during setup already has them, but it is good to confirm before you start.
• Your system is connected to the internet. Chrome is downloaded from Google’s servers rather than Fedora’s mirrors, so a stable connection is required for the package to come through.
• DNF5 is installed. As mentioned above, it is the default on Fedora 41+, so in most cases there is nothing to set up here. You can confirm it quickly with dnf --version if you are curious.

📦 Step-by-Step Installation

1. Enable the Google Chrome Repository

Here is the part that tripped me up the first time. Fedora cannot include Chrome in its own repositories for licensing reasons, so before we can install anything, we need to tell DNF about Google’s official repository and switch it on. The good news is that Google maintains this repository carefully, which means you get clean, official packages and automatic updates alongside the rest of your system.

sudo dnf config-manager setopt google-chrome.enabled=1

Let us break down what this command actually does. config-manager is DNF5’s built in tool for managing repository settings, setopt lets us change a specific option, and this line flips the enabled flag for the google-chrome repo from off to on. One of the nicest things about DNF5 is that config-manager is included by default, so on a stock Fedora 41 system there is no extra plugin to hunt down.

📝 Tip: If dnf config-manager isn’t available on your system, you are likely on an older DNF release. Install the plugin with:

sudo dnf install dnf-plugins-core

2. Install Google Chrome

With the repository live, the actual installation is a one liner:

sudo dnf install google-chrome-stable

DNF5 will reach out to Google’s repository, resolve the dependencies, and show you a summary of what it is about to install. You will be asked to confirm before anything touches your system, which is a handy safety step. On a decent connection, the whole download usually finishes in under a minute, and DNF5’s faster metadata handling makes the process noticeably snappier than the older DNF4.

By installing google-chrome-stable, you get the current stable release, which is what most people want. Google also keeps two other channels if you ever feel adventurous:

✅ You can also install other variants:

• google-chrome-beta for testing upcoming features.
• google-chrome-unstable for bleeding-edge updates.

A quick word of advice from someone who has been there: stick with the stable channel unless you specifically need to test something. Beta and unstable builds update often and can occasionally break in ways that are really annoying when you just want to get work done.

3. Launch Chrome

Installation is done, so let us open it. From the terminal, you can launch Chrome in the background with:

google-chrome-stable &

The & at the end lets the command run in the background, so your terminal stays free for other things. If terminals are not your style, that is totally fine too. Chrome will show up in your application launcher under “Internet”, or you can simply press the Super key and type “Chrome” to find it. Either way, you should be greeted by the familiar Chrome window within a couple of seconds.

🔐 Optional: Set Chrome as Default Browser

Chrome is great, but it only becomes your default browser if you tell your desktop environment that. If you want every link you click anywhere on your system to open in Chrome, run:

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

This tells the XDG desktop standard which browser should handle links, and it is a small step that makes a surprisingly big difference. Nothing is more annoying than clicking a link in your email app and having it open in a browser you did not mean to use. If you ever want to switch back, open your system settings and look for the Default Applications section, where you can pick any browser you have installed.

🧩 Troubleshooting

Even with a clean guide, things can occasionally go sideways, and I have definitely been there. Here are the two issues I have run into most often with this exact setup, along with the fixes that worked for me.

GPG key errors? Sometimes DNF refuses to trust the repository because Google’s signing key is missing from your system’s keyring. This usually happens on fresh installs or when the key has changed upstream. Fixing it is straightforward, just import the official key again:

sudo rpm --import https://dl.google.com/linux/linux_signing_key.pub

After that, run the install command from Step 2 once more, and DNF should accept the packages without complaint.

Missing repo? If DNF tells you that the repository does not exist, the repo file may not have been picked up properly on your system. In that case, you can add the repository manually and point DNF straight at Google’s RPM repository:

sudo dnf config-manager --add-repo https://dl.google.com/linux/chrome/rpm/stable/x86_64

Once the repo is added, you can double check that it is enabled by running the command from Step 1 again, then try the installation a second time.

🧪 Bonus: Verify Installation

Once everything is installed, it feels good to confirm that it actually worked. Checking the version is the fastest way:

google-chrome-stable --version

You should see something like Google Chrome 1xx.0.xxxx.xx printed back at you. The exact number depends on when you install, since Chrome updates itself regularly, but if a version appears, congratulations, you are all set. You can also check from inside the browser at chrome://settings/help, which will even tell you whether an update is available.

🧼 Uninstalling Chrome

Plans change, and maybe someday Chrome is not what you need anymore. Removing it is just as easy as installing it:

sudo dnf remove google-chrome-stable

DNF will ask for confirmation, then cleanly remove the package and anything that came along with it. Note that this removes the browser itself but keeps the repository entry on your system, which is actually convenient if you think you might come back someday. If you would rather remove the repo as well, you can delete the google-chrome.repo file from /etc/yum.repos.d/ yourself.

🧠 Final Thoughts

There you have it. With Google’s official repository and Fedora’s modern DNF5, installing Chrome takes just a few commands and about a minute of your time. It is one of those tasks that looks intimidating the first time, but once you have done it, you will realize how simple it really is.

Whether you are a developer testing web apps, a student juggling Google Classroom and Docs, or someone who simply wants a fast browser that syncs your tabs and passwords everywhere, Chrome is a solid choice, and now it is happily living on your Fedora machine.

Thanks for reading, and enjoy your new browser. If you run into any hiccups, the troubleshooting section above covers the two most common ones, and I will keep this guide updated whenever something changes.