How to Install Google Chrome on Ubuntu Linux

Google Chrome is one of the most popular web browsers, known for its speed, security, and extensive extension library. Additionally, Chrome syncs browsing data across devices, provides powerful developer tools, and comes in three versions: the stable build for general use, the beta build for testing upcoming features, and the unstable (dev) build for developers exploring experimental features.

On Ubuntu, you can install Google Chrome using Google’s official APT repository for access to all three builds with automatic updates. Alternatively, install Chrome via Flatpak from Flathub for a sandboxed environment with stable and unstable builds. Additionally, for users seeking an open-source alternative, consider Chromium, which shares Chrome’s core codebase without proprietary components. Ultimately, this guide covers both installation methods so you can choose the best option for your needs.

Choose Your Google Chrome Installation Method

Specifically, Ubuntu offers two primary installation paths for Google Chrome, each with distinct advantages. The APT repository method provides native system integration with automatic updates through Ubuntu’s package manager, while Flatpak offers application sandboxing for enhanced isolation. Therefore, choose the method that best fits your security preferences and update workflow.

Method	Builds Available	Updates	Best For
APT Repository	Stable, Beta, Unstable	Automatic via system updates	Users who prefer native integration and all three release channels
Flatpak (Flathub)	Stable, Unstable	Manual via flatpak update	Users prioritizing sandboxed isolation or running multiple Chrome versions

The APT method is recommended for most users due to its seamless integration with Ubuntu’s update system and access to all release channels. Meanwhile, Flatpak works well when you need application isolation or already use Flatpak for other software.

Method 1: Install Google Chrome via APT Repository

Install Required Packages

To begin, before proceeding with the installation, ensure curl is installed on your system to download Google’s GPG key. Most Ubuntu installations include curl by default, but minimal or server configurations may lack it.

Then, install curl if missing:

sudo apt install curl -y

Importantly, this command safely installs curl without affecting your system if the package already exists.

Import Google Chrome APT Repository

First, import Google’s GPG key to verify the authenticity of packages from their repository. Specifically, this command downloads the key, converts it to the proper format, and stores it in Ubuntu’s modern keyring directory, ensuring APT can verify package signatures during installation and updates.

curl -fSsL https://dl.google.com/linux/linux_signing_key.pub | gpg --dearmor | sudo tee /usr/share/keyrings/google-chrome.gpg > /dev/null

Next, add the official Google Chrome repository:

echo deb [arch=amd64 signed-by=/usr/share/keyrings/google-chrome.gpg] http://dl.google.com/linux/chrome/deb/ stable main | sudo tee /etc/apt/sources.list.d/google-chrome.list

Update APT Cache After Repository Import

Afterward, update your APT package lists to include the newly added Google repository:

sudo apt update

Install Google Chrome Stable

After updating your package lists, install the stable version of Google Chrome, which provides the most tested and reliable browsing experience recommended for daily use:

sudo apt install google-chrome-stable

Install Google Chrome Beta

Beyond the stable release, the beta version provides early access to upcoming features before they reach the stable channel. However, while generally reliable, beta builds may contain bugs as Google tests new functionality with a broader audience.

Optionally, install the Google Chrome Beta build:

sudo apt install google-chrome-beta

Install Google Chrome Unstable (Dev)

For developers and early adopters, the unstable (dev) version contains the latest experimental features. However, expect potential instability, bugs, and occasional crashes as this build receives cutting-edge updates before extensive testing.

Optionally, install the Google Chrome Unstable version:

sudo apt install google-chrome-unstable

Installing beta or unstable versions will not replace your stable version. Ubuntu installs each version separately, allowing you to run multiple Google Chrome builds simultaneously for different testing or browsing needs.

Method 2: Install Google Chrome via Flatpak

Alternatively, Flatpak provides a universal package manager that runs Chrome in a sandboxed environment, isolating it from system libraries. Moreover, this approach works across Linux distributions and reduces conflicts with other software.

If you haven’t installed Flatpak yet, first follow our guide on installing Flatpak on Ubuntu.

Enable Flathub Repository

First, add the Flathub repository system-wide to access Google Chrome and other Flatpak applications:

sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

Install Google Chrome via Flatpak

Install Stable Version

Next, install the stable version system-wide for reliable daily browsing:

sudo flatpak install flathub com.google.Chrome -y

Install Unstable Version

Alternatively, install the unstable (dev) version system-wide for early access to experimental features:

sudo flatpak install flathub com.google.ChromeDev -y

Flathub does not currently offer a beta version of Google Chrome through Flatpak. Only stable and unstable (dev) builds are available.

Launch Google Chrome

CLI Methods to Launch Google Chrome

To start, launch Google Chrome from the terminal using these commands based on your installation method and version:

For APT installations, launch the stable version:

google-chrome

Similarly, launch the beta version:

google-chrome-beta

Likewise, launch the unstable version:

google-chrome-unstable

Alternatively, for Flatpak installations, launch the stable version:

flatpak run com.google.Chrome

Similarly, launch the unstable version:

flatpak run com.google.ChromeDev

GUI Method to Launch Google Chrome

Alternatively, to open Google Chrome using the GUI, follow these steps:

1. Click on ‘Activities’ located at the top-left corner of your screen.
2. Next, click ‘Show Applications,’ typically represented by a grid of dots at the screen’s bottom-left corner.
3. Finally, look for ‘Google Chrome’ among the applications. If you have multiple versions installed, they will be listed as ‘Google Chrome (Stable),’ ‘Google Chrome (Beta),’ and ‘Google Chrome (Unstable).’ Click on the one you wish to launch.

Additional Google Chrome Commands

Update Google Chrome

After installation, Google Chrome receives automatic security and feature updates. With APT installations, Chrome updates integrate seamlessly with Ubuntu’s standard system updates, whereas Flatpak installations require manual update commands or respond to desktop notifications.

To update everything with APT, including Chrome, run:

sudo apt update && sudo apt upgrade

Alternatively, to update only Google Chrome:

sudo apt update && sudo apt upgrade google-chrome-stable

Similarly, for Flatpak installations, update all Flatpak applications including Chrome:

sudo flatpak update

Additionally, to automate Chrome updates along with other system packages, consider configuring Unattended Upgrades for automatic security and software updates.

Remove Google Chrome

Remove via APT

First, remove the Google Chrome stable version:

sudo apt remove google-chrome-stable

Alternatively, remove Google Chrome beta:

sudo apt remove google-chrome-beta

Similarly, for the unstable version:

sudo apt remove google-chrome-unstable

Optionally, remove the Google Chrome repository:

sudo rm /etc/apt/sources.list.d/google-chrome.list

Remove via Flatpak

Similarly, remove Google Chrome stable:

sudo flatpak uninstall com.google.Chrome

For the unstable version:

sudo flatpak uninstall com.google.ChromeDev

Fix APT Duplicate Repository Warnings

When you run sudo apt update, you may encounter duplicate repository warnings if multiple Chrome versions were installed. Chrome automatically adds its own repository file during installation, so installing stable, beta, and unstable versions creates multiple files pointing to the same repository.

The warning looks like this:

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:1 and /etc/apt/sources.list.d/google-chrome-beta.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/google-chrome.list:1 and /etc/apt/sources.list.d/google-chrome-unstable.list:1

While harmless, these warnings clutter your update output and signal redundant configuration.

Check for Duplicate Repository Files

First, verify if you have multiple Google repository files:

ls -1 /etc/apt/sources.list.d/google*

If you see multiple files, the output shows the duplicates:

/etc/apt/sources.list.d/google-chrome.list
/etc/apt/sources.list.d/google-chrome-beta.list
/etc/apt/sources.list.d/google-chrome-unstable.list

Each Chrome version creates its own repository file, but all three files contain identical repository entries pointing to the same source. APT only needs one file since the repository serves all Chrome versions (stable, beta, unstable) from a single location.

Remove Extra Source Lists

Remove all Google Chrome repository files to start fresh:

sudo rm /etc/apt/sources.list.d/google*

This command removes every file in /etc/apt/sources.list.d/ starting with “google,” clearing all duplicate entries. The glob pattern (google*) matches google-chrome.list, google-chrome-beta.list, and google-chrome-unstable.list in one operation.

Re-Add Google Chrome Repository

Next, recreate a single repository file that serves all Chrome versions:

echo deb [arch=amd64 signed-by=/usr/share/keyrings/google-chrome.gpg] http://dl.google.com/linux/chrome/deb/ stable main | sudo tee /etc/apt/sources.list.d/google-chrome.list

This creates one consolidated repository file. The repository includes all Chrome versions (stable, beta, unstable) even though the entry references “stable main” in its configuration line.

Update Package Lists

Finally, update APT to verify the warnings disappeared:

sudo apt update

You should see clean output without duplicate repository warnings. APT now references a single Google Chrome repository while maintaining access to all installed versions.

Closing Thoughts

Google Chrome installs on Ubuntu through two primary methods: the official APT repository for native system integration with automatic updates across stable, beta, and dev builds, or Flatpak from Flathub for sandboxed isolation with stable and unstable versions. Both approaches maintain browser security and deliver the latest features reliably. For users prioritizing privacy, consider Brave Browser, a Chromium-based alternative with built-in ad blocking and enhanced privacy protections.

Useful Links

For quick reference, here are some useful links related to using Google Chrome:

• Chrome Web Store: Visit the Chrome Web Store to explore and download various extensions and themes for Google Chrome.
• Chrome Web Store Extensions: Browse the extensive collection of extensions available on the Chrome Web Store to enhance your browsing experience.
• Chrome Web Store Themes: The Chrome Web Store offers a wide range of themes to customize the appearance of your browser.
• Google Chrome Community Support: Join the Google Chrome community support forum to ask questions, share solutions, and get help from other Chrome users.