How to Install Google Chrome on Debian 13, 12 and 11

Google Chrome brings Google account sync, Widevine media playback, proprietary codecs, Chrome Web Store compatibility, and Google’s current browser channel to Debian desktops. To install Google Chrome on Debian 13 (Trixie), Debian 12 (Bookworm), or Debian 11 (Bullseye), add Google’s signed APT repository, install the google-chrome-stable package, then keep Chrome updated with normal APT upgrades.

Chrome is not part of Debian’s default repositories, so sudo apt install google-chrome-stable only works after the Google source is configured. Google’s Chrome download page also offers a 64-bit .deb package for Debian and Ubuntu, but the repository method is the cleaner repeatable path because APT verifies the repository metadata and handles future updates.

Google Chrome for Debian is available only for 64-bit amd64 systems. Google does not publish an arm64 Debian package or an official Chrome Snap. Flathub lists com.google.Chrome, but current Flathub metadata does not show Google verification, so Google’s Debian package is the vendor-published path for Chrome on Debian.

Install Google Chrome on Debian with APT

This method adds Google’s APT repository in DEB822 format and installs the stable Chrome package from that source. It works on Debian 13, 12, and 11 on amd64 hardware.

Check Debian Architecture for Chrome

Confirm the system architecture before adding the repository:

dpkg --print-architecture

amd64

Continue when the output is amd64. If the system reports arm64, i386, or another architecture, use Chromium on Debian or Firefox on Debian instead.

Install Google Chrome Repository Tools

Install the packages needed to download the signing key with the curl command and write the APT source securely:

sudo apt update
sudo apt install ca-certificates curl gpg -y

The commands need sudo because they write to system package-manager paths. If your account cannot use sudo yet, add the account to sudoers before continuing.

Related help: add a user to sudoers on Debian.

Import Google’s APT Signing Key

Create the keyring directory, then download Google’s Linux package signing key and convert it to APT’s binary keyring format:

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

Optional verification shows Google’s current Linux package signing authority fingerprint:

gpg --show-keys --with-fingerprint /usr/share/keyrings/google-chrome.gpg

pub   rsa4096 2016-04-12 [SC]
      EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796
uid           Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>

Add the Google Chrome APT Source

Add Google’s Chrome repository as a DEB822 .sources file. The Architectures: amd64 line prevents APT from requesting unsupported 32-bit package indexes on multiarch systems:

printf '%s\n' \
  'Types: deb' \
  'URIs: https://dl.google.com/linux/chrome-stable/deb/' \
  'Suites: stable' \
  'Components: main' \
  'Architectures: amd64' \
  'Signed-By: /usr/share/keyrings/google-chrome.gpg' | sudo tee /etc/apt/sources.list.d/google-chrome.sources > /dev/null

Google’s package also manages this same google-chrome.sources file after installation. Current packages use DEB822 format, not the older google-chrome.list file used by older tutorials.

Verify the Google Chrome Package on Debian

Refresh APT metadata and confirm the stable Chrome package is available from Google’s repository:

sudo apt update
apt-cache policy google-chrome-stable

google-chrome-stable:
  Installed: (none)
  Candidate: 148.0.7778.96-1
  Version table:
     148.0.7778.96-1 500
        500 https://dl.google.com/linux/chrome-stable/deb stable/main amd64 Packages

The Candidate line confirms APT can see Chrome from Google’s repository. The exact version changes as Google publishes new stable releases.

Install Google Chrome Stable on Debian

Install the stable Chrome package:

sudo apt install google-chrome-stable -y

Check the installed browser version:

google-chrome-stable --version

Google Chrome 148.0.7778.96

Chrome is now installed and registered with the desktop application menu. The package may also install dependencies such as wget or fonts-liberation when your Debian release does not already include them.

Install Google Chrome from Official DEB Download on Debian

Google’s Chrome browser packages page lists a 64-bit .deb installer for Debian and Ubuntu. Use this route when you specifically want the official download-file workflow; after installation, the package creates the same Google APT source for updates.

If you skipped the repository setup above, install curl before downloading the package:

sudo apt update
sudo apt install ca-certificates curl -y

The official download URL always points to the current stable amd64 package:

Download the package:

curl -LO https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

Inspect the package metadata before installing it:

dpkg-deb -f google-chrome-stable_current_amd64.deb Package Version Architecture

Package: google-chrome-stable
Version: 148.0.7778.96-1
Architecture: amd64

Install the local file with APT so Debian can resolve dependencies from your enabled repositories:

sudo apt install ./google-chrome-stable_current_amd64.deb -y

The leading ./ matters. Without it, APT treats the filename as a repository package name and may return an “Unable to locate package” error.

After the .deb install finishes, use the same version check, update commands, and removal steps shown in the APT sections. The package writes /etc/apt/sources.list.d/google-chrome.sources and /usr/share/keyrings/google-chrome.gpg for future updates.

Install Google Chrome Beta, Dev, and Canary on Debian

Google’s repository also provides beta, dev, and canary packages. Install these only when you need early browser builds for testing; stable remains the right package for daily browsing.

Install the beta channel:

sudo apt install google-chrome-beta -y

Install the dev channel, packaged as google-chrome-unstable:

sudo apt install google-chrome-unstable -y

Install the canary channel:

sudo apt install google-chrome-canary -y

Each channel installs as a separate application and can run beside the stable package. Check installed channel versions with their matching launcher commands:

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

Google publishes release details on the Chrome Developer Release Notes page and the Chrome Release Blog.

Launch Google Chrome on Debian

After installation, Chrome appears in your desktop environment’s application menu. On the default Debian GNOME desktop:

1. Click Activities in the top-left corner.
2. Type Chrome in the search field.
3. Click the Google Chrome icon.

Terminal launches also work from a graphical session:

google-chrome-stable

If you installed additional channels, use their separate commands:

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

Complete Google Chrome First Launch Setup on Debian

Chrome shows several optional prompts the first time it opens. None of these prompts are required for basic browsing.

Handle the Chrome Keychain Password Prompt

On desktop systems with GNOME Keyring or another secret service, Chrome may ask you to set or enter a keychain password. The keychain stores saved passwords, cookies, and authentication tokens more securely than plain profile files.

• Enter a password to enable secure credential storage.
• Cancel the prompt if you do not want Chrome to use the desktop keychain.

This prompt appears only on systems with a graphical desktop environment and a secret service. Minimal server installations usually do not show it.

Set Google Chrome as Default Browser on Debian

Chrome may ask whether it should become your default browser. Choose Set as Default when you want links from other applications to open in Chrome, or dismiss the prompt to keep the current default browser.

Choose Chrome Usage Statistics Settings

Chrome offers to send usage statistics and crash reports to Google. Leave the box unchecked to opt out, or enable it if you want to share diagnostics.

Sign In or Skip Chrome Sync

Signing in syncs bookmarks, history, passwords, extensions, and settings across devices. It is optional; close the sign-in tab or continue without an account if you want a local-only browser profile.

Customize Chrome Appearance

Chrome may suggest themes or appearance options after setup. These choices affect only the browser profile and can be changed later from Chrome settings.

Update Google Chrome on Debian

The Google APT source updates Chrome through the same package-manager workflow as the rest of your Debian system. This applies whether you added the repository manually or installed Google’s official .deb package.

Update all available packages, including Chrome:

sudo apt update
sudo apt upgrade

Update only the stable Chrome package:

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

Replace google-chrome-stable with google-chrome-beta, google-chrome-unstable, or google-chrome-canary to update another installed channel. For unattended desktop or server patching, see configure unattended upgrades on Debian.

Uninstall Google Chrome from Debian

Remove Chrome packages before deleting the APT source. This order keeps package names resolvable while APT handles the uninstall.

Remove Chrome Packages from Debian

Purge every Chrome channel you installed:

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

APT reports packages that are not installed and removes the ones present on your system.

Remove the Google Chrome APT Source

Remove the current DEB822 source, old legacy source files, and the Google keyring:

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

Refresh APT and verify the package is no longer available from a configured source:

sudo apt update
apt-cache policy google-chrome-stable

When no Google source remains, apt-cache policy prints no package candidate for google-chrome-stable.

Remove Chrome Profile Data

The next commands permanently delete Chrome profiles, bookmarks, saved passwords, extensions, cookies, and browsing history stored in your home directory. Back up any profile directory you want to keep before deleting it.

rm -rf ~/.config/google-chrome ~/.config/google-chrome-beta ~/.config/google-chrome-unstable ~/.config/google-chrome-canary
rm -rf ~/.cache/google-chrome ~/.cache/google-chrome-beta ~/.cache/google-chrome-unstable ~/.cache/google-chrome-canary
rm -f ~/.local/share/applications/google-chrome*.desktop

Troubleshoot Google Chrome Issues on Debian

Fix Unable to Locate google-chrome-stable

If APT cannot find google-chrome-stable, the Google repository is missing, disabled, or not refreshed yet. Confirm the source file exists, then refresh APT:

ls -l /etc/apt/sources.list.d/google-chrome.sources
sudo apt update
apt-cache policy google-chrome-stable

If the file is missing, repeat the signing-key and source-file steps from the APT install method. If you downloaded the .deb file, install it with sudo apt install ./google-chrome-stable_current_amd64.deb, including the leading ./.

Fix Google Chrome GPG Key Errors on Debian

A missing or outdated keyring can produce a signature error during apt update:

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 32EE5355A6BC6E42

Reinstall the signing key, then refresh APT:

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

Fix Duplicate Chrome Repository Warnings on Debian

Older Chrome installs, legacy tutorials, or previous extrepo setups can leave multiple source files for the same Google repository. APT may report duplicate targets or a Conflicting values set for option Signed-By error.

List Chrome-related source files:

ls -la /etc/apt/sources.list.d/*google*chrome* /etc/apt/sources.list.d/extrepo_google* 2>/dev/null || echo "No Chrome repository files found"

A duplicate warning can look similar to 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.sources:1

Remove legacy entries and recreate one clean DEB822 source:

sudo rm -f /etc/apt/sources.list.d/google-chrome.list /etc/apt/sources.list.d/extrepo_google_chrome.sources
printf '%s\n' \
  'Types: deb' \
  'URIs: https://dl.google.com/linux/chrome-stable/deb/' \
  'Suites: stable' \
  'Components: main' \
  'Architectures: amd64' \
  'Signed-By: /usr/share/keyrings/google-chrome.gpg' | sudo tee /etc/apt/sources.list.d/google-chrome.sources > /dev/null
sudo apt update

Fix i386 Architecture Notices from Chrome Repository

Debian systems with 32-bit multiarch enabled may ask Google’s repository for an unsupported i386 index:

N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://dl.google.com/linux/chrome-stable/deb stable InRelease' doesn't support architecture 'i386'

Limit the Chrome source to amd64 again:

printf '%s\n' \
  'Types: deb' \
  'URIs: https://dl.google.com/linux/chrome-stable/deb/' \
  'Suites: stable' \
  'Components: main' \
  'Architectures: amd64' \
  'Signed-By: /usr/share/keyrings/google-chrome.gpg' | sudo tee /etc/apt/sources.list.d/google-chrome.sources > /dev/null
sudo apt update

The notice is harmless, but adding Architectures: amd64 keeps APT output clean. Chrome package upgrades may regenerate the source file, so repeat this fix if the notice returns.

Fix Missing Chrome Libraries on Minimal Debian Systems

APT should install Chrome dependencies automatically. If a local .deb install was interrupted and Chrome reports missing shared libraries, repair dependencies first:

error while loading shared libraries: libatk-1.0.so.0: cannot open shared object file

sudo apt --fix-broken install

If the browser package remains incomplete, reinstall stable Chrome:

sudo apt install --reinstall google-chrome-stable

Run Google Chrome in Headless Mode on Debian

Chrome needs a graphical session for normal interactive use. For automation tasks such as printing a page to PDF, use headless mode instead of trying to open the desktop browser on a server console:

google-chrome-stable --headless --print-to-pdf=output.pdf https://example.com

Google Chrome vs Chromium on Debian

Chromium is the open-source browser project that Chrome is built from. Google Chrome adds Google’s proprietary sync integration, bundled media components, branded release channels, and Google’s own APT repository. If you want a browser available from Debian or Flathub without Google’s proprietary package, install Chromium on Debian instead.

Conclusion

Google Chrome is now installed on Debian with APT-managed updates from Google’s signed repository. Stable is the best channel for daily browsing, while beta, dev, and canary are separate packages for testing upcoming changes. For other browser choices, compare Firefox on Debian, Brave Browser on Debian, Vivaldi on Debian, Microsoft Edge on Debian, or Opera Browser on Debian.