How to Install Google Chrome on Linux Mint

Google Chrome helps you browse modern websites, run web applications, and sync bookmarks and passwords across devices. Common use cases include accessing Google services with native integration, debugging websites with Chrome DevTools, and running Progressive Web Apps as standalone applications. By the end of this guide, you will have Google Chrome installed from the official repository with automatic updates enabled, verified by a version check.

This guide covers two installation methods: the simplified extrepo approach that handles repository configuration automatically, and the manual DEB822 repository setup for users who prefer explicit control. Additionally, both methods provide access to four Chrome builds: Stable for daily use, Beta for preview features, Unstable (Dev) for early testing, and Canary for cutting-edge nightly builds. For a privacy-focused alternative without Google telemetry, see our guide on installing Chromium Browser on Linux Mint.

Choose Your Google Chrome Installation Method

Google distributes Chrome through their official APT repository, which you can configure using either extrepo (automated) or manual DEB822 setup. Both methods provide identical packages and automatic updates, so your choice depends on whether you prefer convenience or explicit control.

Method	Steps	Best For
Extrepo (Recommended)	4 commands	Most users; quick setup with automatic GPG key and repository handling
Manual Repository	6 commands	Users who want explicit control over GPG keys and repository configuration

Google’s repository uses a universal package format that works across all Ubuntu-based Linux Mint releases without version-specific configuration. As a result, the steps shown in this guide work identically on Linux Mint 21.x and 22.x.

For most users, the extrepo method is recommended because it handles GPG key management and repository configuration automatically with just a few commands. However, choose the manual method if you need custom repository settings or prefer to understand the underlying configuration.

Understand Chrome Build Channels

Before installing, consider which Chrome build best fits your needs. Google maintains four parallel release channels, each serving different purposes:

Build	Release Cycle	Stability	Best For
Stable	Every 4 weeks	Thoroughly tested	Daily browsing, work, and general use
Beta	4-6 weeks ahead	Minor issues possible	Previewing upcoming features before public release
Unstable (Dev)	Weekly	May have bugs	Web developers testing with latest web platform features
Canary	Daily (nightly)	Expect instability	Testing bleeding-edge features; not for primary use

For most users, the Stable channel provides the best balance of features and reliability. If you develop websites or want early access to new features, consider installing Beta alongside Stable. Each build uses separate configuration directories, so you can run multiple versions simultaneously without conflicts.

Method 1: Install Google Chrome with Extrepo (Recommended)

Extrepo is a repository management tool that simplifies adding external repositories by handling GPG keys and DEB822 configuration automatically. This method requires fewer commands and reduces the chance of configuration errors.

Install Extrepo

First, update your package index and install extrepo from the Ubuntu Universe repository:

sudo apt update
sudo apt install extrepo -y

The -y flag automatically confirms the installation prompt, which speeds up the process when you know what you want to install.

Enable Non-Free Repository Policy

By default, extrepo only enables open-source (DFSG-free) repositories. Since Google Chrome is proprietary software, you need to enable the non-free policy before adding the repository:

sudo sed -i 's/# - contrib/- contrib/' /etc/extrepo/config.yaml
sudo sed -i 's/# - non-free/- non-free/' /etc/extrepo/config.yaml

These commands uncomment the contrib and non-free policy lines in the extrepo configuration file. As a result, you gain access to proprietary repositories like Google Chrome, Microsoft Edge, and Brave.

Enable Google Chrome Repository

With the non-free policy enabled, add the Google Chrome repository and refresh your package index:

sudo extrepo enable google_chrome
sudo apt update

Extrepo automatically downloads Google’s GPG signing key and creates a properly formatted DEB822 sources file at /etc/apt/sources.list.d/extrepo_google_chrome.sources. This ensures your system can verify package authenticity during installation and updates.

Install Google Chrome

Now that the repository is configured, install your preferred Chrome build. For daily use, the Stable build is recommended:

sudo apt install google-chrome-stable -y

Alternatively, install other builds based on your needs:

Beta (preview upcoming features, roughly 4-6 weeks ahead of Stable):

sudo apt install google-chrome-beta -y

Unstable (Dev) (early development builds, updated weekly):

sudo apt install google-chrome-unstable -y

Canary (nightly builds with cutting-edge features):

sudo apt install google-chrome-canary -y

You can install multiple Chrome versions simultaneously since each uses separate directories and executables. For example, having Stable for daily work and Beta for testing upcoming features is a common setup among web developers.

Verify Installation

After installation completes, confirm that Chrome is accessible from your terminal by checking the version:

google-chrome-stable --version

Google Chrome 143.0.7499.169

The version output confirms that Chrome is properly installed and ready to use. Your version may differ depending on when you run this command, as Chrome updates frequently through the APT package manager.

Method 2: Install Google Chrome with Manual Repository Setup

This method provides explicit control over the GPG key and repository configuration. Use this approach if you prefer understanding exactly what gets added to your system or need to customize the repository setup for specific requirements.

Update System Packages

Before adding external repositories, update your system packages to ensure you have the latest security patches and dependency information:

sudo apt update && sudo apt upgrade

This refreshes your package index and applies any pending updates. While upgrading is optional, it ensures your system has current certificates and tools needed for secure downloads.

Import Google Chrome GPG Key

Next, download and install Google’s package signing key. This key verifies that packages come from Google and have not been tampered with during download:

curl -fsSL https://dl.google.com/linux/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/google-chrome.gpg

This single command downloads the ASCII-armored key, converts it to binary GPG format, and saves it to the system keyrings directory. Once imported, the key remains valid for all future Chrome updates without requiring reimport.

Add Google Chrome Repository

Now create the repository configuration file using the modern DEB822 .sources format. This format provides cleaner syntax and better multi-architecture support than legacy .list files:

cat <<EOF | sudo tee /etc/apt/sources.list.d/google-chrome.sources
Types: deb
URIs: https://dl.google.com/linux/chrome/deb/
Suites: stable
Components: main
Signed-By: /usr/share/keyrings/google-chrome.gpg
EOF

After adding the repository, refresh the package index to make the new packages available:

sudo apt update

Install Google Chrome

With the repository configured, install your preferred Chrome build. For most users, the Stable build is recommended:

sudo apt install google-chrome-stable -y

If you need other builds, install them using the corresponding package names:

Beta (preview upcoming features, roughly 4-6 weeks ahead of Stable):

sudo apt install google-chrome-beta -y

Unstable (Dev) (early development builds for testing new features):

sudo apt install google-chrome-unstable -y

Canary (nightly builds with cutting-edge features):

sudo apt install google-chrome-canary -y

Warning: Beta, Unstable, and Canary builds are not recommended for production systems or primary computers. Use them only for testing new features in non-critical environments. The Stable build receives thorough testing before release and is suitable for daily use.

Verify Installation

Finally, confirm the installation succeeded by checking the installed version:

google-chrome-stable --version

Google Chrome 143.0.7499.169

Launch Google Chrome

Once installed, you can launch Google Chrome from the terminal or the application menu.

Launch from Terminal

To start Google Chrome from the terminal, use the command that matches your installed version:

google-chrome-stable

For other versions, use the corresponding command:

google-chrome-beta
google-chrome-unstable
google-chrome-canary

Launch from Applications Menu

Most users launch Chrome from the application menu. In Linux Mint, navigate through the menu to find Chrome:

Menu > Internet > Google Chrome

On first launch, Chrome prompts you to set it as the default browser and asks permission to send usage statistics and crash reports to Google. Make your privacy choices based on your preferences and click OK to continue.

You can skip signing into Chrome by clicking the X on the sign-in tab. The browser works fully without a Google account, although sync features for bookmarks, passwords, and history require signing in.

Manage Google Chrome

Update Google Chrome

Google Chrome updates automatically through the APT package manager when you run system updates. To check for and install updates manually, run the following commands:

sudo apt update && sudo apt upgrade

Alternatively, if you want to update only Chrome without affecting other packages, use the following command:

sudo apt update
sudo apt install --only-upgrade google-chrome-stable

This targeted approach is useful when you need the latest Chrome version immediately but want to delay other system updates.

Uninstall Google Chrome

To remove Google Chrome packages when you no longer need them, use the following command. The --purge flag removes configuration files along with the package:

sudo apt remove google-chrome-stable --purge
sudo apt autoremove

Running autoremove ensures that any dependencies installed specifically for Chrome that are no longer needed by other applications are also removed from your system.

If you installed multiple versions, remove each one separately using the corresponding package name:

sudo apt remove google-chrome-beta --purge
sudo apt remove google-chrome-unstable --purge
sudo apt remove google-chrome-canary --purge
sudo apt autoremove

Remove Google Chrome Repository

After uninstalling Chrome, remove the repository configuration to stop receiving update notifications for a package you no longer use.

If you used the extrepo method:

sudo extrepo disable google_chrome
sudo rm -f /etc/apt/sources.list.d/extrepo_google_chrome.sources

If you used the manual repository method:

sudo rm /etc/apt/sources.list.d/google-chrome.sources
sudo rm /usr/share/keyrings/google-chrome.gpg

Finally, refresh your package index to apply the repository changes:

sudo apt update

Remove User Data (Optional)

After uninstalling Chrome, you can optionally remove your personal data to complete the cleanup.

Warning: The commands below permanently delete your Google Chrome user data including bookmarks, saved passwords, browsing history, cookies, extensions, and settings. Export any data you want to keep before proceeding. This action cannot be undone.

To remove user configuration and cache directories for the Stable build:

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

If you installed Beta or Unstable versions, they use separate directories that also need removal:

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

Troubleshooting Google Chrome Issues

Duplicate Repository Warnings

When installing multiple Chrome versions (stable, beta, unstable, canary), each installation package may create its own legacy repository file. This causes duplicate source warnings when running apt update:

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

This happens because Google’s installer sometimes creates legacy .list files even when you configured .sources files. While the warnings are harmless, they clutter your terminal output.

First, check which repository files exist on your system by listing all files starting with “google-chrome” in the sources directory:

ls -la /etc/apt/sources.list.d/google-chrome*

Example output showing duplicate .list files alongside the modern .sources or extrepo file:

-rw-r--r-- 1 root root  189 Jul 10 10:00 google-chrome-beta.list
-rw-r--r-- 1 root root  189 Jul 10 10:00 google-chrome-unstable.list
-rw-r--r-- 1 root root  189 Jul 10 10:00 google-chrome.list
-rw-r--r-- 1 root root  250 Jul 10 10:00 google-chrome.sources

To fix this issue, remove the duplicate legacy .list files and keep only your .sources file or the extrepo-managed file:

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

Next, update the package list and verify the warnings are gone:

sudo apt update

The .list files may reappear after Chrome updates or reinstallations. If you see duplicate warnings again, simply remove the .list files again with the same command. Your .sources file (or extrepo configuration) provides all necessary repository information.

Restore Missing Repository Configuration

If you accidentally deleted your repository configuration and Chrome no longer receives updates, recreate it using either the extrepo or manual method described earlier in this guide.

To quickly verify whether your repository is working correctly, run the following command:

apt-cache policy google-chrome-stable

If the output shows a candidate version from dl.google.com, your repository is configured correctly:

google-chrome-stable:
  Installed: 143.0.7499.169-1
  Candidate: 143.0.7499.169-1
  Version table:
 *** 143.0.7499.169-1 500
        500 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages

If instead the output shows “N: Unable to locate package,” your repository configuration is missing or incorrect. Follow the installation steps again to restore it.

Conclusion

You now have Google Chrome installed with automatic updates from the official repository. The browser supports extension installation, cross-device sync when signed in, and DevTools for web development. For enhanced privacy, consider installing Chromium from the official repositories, or explore alternatives like Microsoft Edge or Tor Browser for different use cases.