How to install Chrome browser on Debian 13 Trixie Linux

Installing Google Chrome on Debian 13 is similar to setting it up on Ubuntu or other distributions. However, with the right approach, you can have it running smoothly in minutes. As a Linux system administrator who has deployed Chrome across multiple Debian workstations and servers, I present a detailed tutorial on every possible way to install Chrome on Debian.

Quick Answer

One-line Chrome Install Command (via .deb file)

For those who need Chrome installed immediately, here’s a one line command that is the fastest method in this tutorial. It will download the Chrome Debian binary and immediately execute it for installing, you just need to provide the user password, when the terminal asked for that.

wget -q -O chrome.deb https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb && sudo apt install ./chrome.deb

One-line Repo + APT Install (Auto-updating)

For automatic updates through APT:

wget -qO- https://dl.google.com/linux/linux_signing_key.pub | gpg --dearmor | sudo tee /usr/share/keyrings/google-chrome.gpg >/dev/null && echo "deb [arch=amd64 signed-by=/usr/share/keyrings/google-chrome.gpg] https://dl.google.com/linux/chrome/deb/ stable main" | sudo tee /etc/apt/sources.list.d/google-chrome.list >/dev/null && sudo apt update && sudo apt install -y google-chrome-stable

---

Why Chrome Isn’t in Debian Repositories

Why you can’t simply run sudo apt install google-chrome helps explain the installation process we’ll follow.

Licensing Restrictions (Closed Source)

Debian’s central repositories adhere strictly to the Debian Free Software Guidelines (DFSG), which means they only include open-source software. Google Chrome contains proprietary components, including the integrated Flash player (legacy), particular media codecs, and Google’s update mechanism. These closed-source elements make Chrome incompatible with Debian’s philosophical stance on free software.

Difference Between Chrome and Chromium

Many Debian users confuse Chrome with Chromium, which IS available in Debian’s repositories. Chromium is the open-source foundation of Chrome, lacking Google’s proprietary additions, such as automatic updates, specific codecs, Flash support, and Google service integration. While Chromium works well for many users, Chrome offers better compatibility with services like Netflix, Google Meet, and specific enterprise applications that specifically check for Chrome’s user agent and features.

Methods to Install Google Chrome on Debian 13

Method 1: Official APT Repository (Recommended)

If you don’t want to go with a single command discussed in the beginning of the article or in case it is not working then here are the steps in the detial. This method ensures that you always have the latest Chrome version, complete with automatic security updates. I recommend this approach for most users, especially on production systems where security patches are critical.

Step 1: Add Google Signing Key

First, download and add Google’s GPG key to verify package authenticity:

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

This command downloads Google’s public key and converts it to the GPG format Debian expects. The key goes into /usr/share/keyrings/ following Debian’s current best practices for third-party repository keys.

Step 2: Add Google Repo to sources.list.d

Create a new repository source file:

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

This adds Google’s Chrome repository to your system. The signed-by parameter links this repository to the GPG key we just added, ensuring all packages from this source are verified.

Step 3: Update and Install

Update your package list and install Chrome:

sudo apt update
sudo apt install google-chrome-stable

The installation typically takes 30-60 seconds, depending on your internet speed. Chrome will automatically configure menu entries and file associations during the installation process. Once done go to Applications and search for Google chrome to launch it.

---

Installing Beta & Dev Versions (only for developers)

For developers or early adopters, Google offers beta and development versions:

# For Beta version (more stable than Dev, updated weekly)
sudo apt install google-chrome-beta

# For Dev version (cutting edge, updated multiple times weekly)
sudo apt install google-chrome-unstable

You can install multiple versions simultaneously—they won’t conflict as they use different directories and configuration paths.

Fixing Repo/GPG Key Errors

If you encounter “NO_PUBKEY” errors, the signing key may have changed:

# Remove old key
sudo rm /usr/share/keyrings/google-chrome.gpg

# Re-download current key
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo gpg --dearmor -o /usr/share/keyrings/google-chrome.gpg

# Update package lists
sudo apt update

For “Repository does not have a Release file” errors, ensure your sources.list entry exactly matches the format shown above, including the architecture specification.

---

Method 2: Download & Install .deb File

This method works well for offline installations or when you need a specific Chrome version.

Step 1: Download .deb File (GUI & CLI Options)

Using the command line:

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

Alternatively, visit https://www.google.com/chrome/ in Firefox and click “Download Chrome,” selecting the 64–bit .deb option.

Step 2: Install Using APT or DPKG

The modern approach using APT (handles dependencies automatically):

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

Or using dpkg (requires manual dependency resolution):

sudo dpkg -i google-chrome-stable_current_amd64.deb
# If dependencies are missing:
sudo apt --fix-broken install

Using GDebi for GUI Users

GDebi provides a graphical interface for .deb installation:

sudo apt install gdebi
# Then right-click the .deb file and select "Open with GDebi Package Installer"

When to Prefer This Method

Choose direct .deb installation for air-gapped systems without internet access, when you need a specific Chrome version for compatibility testing, or in environments where adding external repositories is prohibited by policy. Remember that you’ll need to download and install updates manually.

---

Use Gnome Softwware to install Chrome on Debian 13 -Graphical Installation (GUI Steps)

For users who prefer graphical interfaces, Debian 13’s GNOME environment streamlines the process.

Step 1: Open Firefox and navigate to google.com/chrome. Click “Download Chrome” and select “64-bit .deb (For Debian/Ubuntu).”

Step 2: Once downloaded, open your file manager and navigate to the Downloads folder.

Step 3: Double–click the downloaded .deb file.

Step 4: GNOME Software (or KDE’s Discover) will open automatically.

Step 5: Click “Install” and enter your password when prompted.

The software center handles all dependencies automatically, making this the most user-friendly approach for desktop users.

---

Chrome for Servers & Headless Use

Server installations require special consideration since most Debian servers lack graphical interfaces. Chrome can run headless for automated testing, web scraping, or PDF generation.

Install Chrome without X11 dependencies:

sudo apt install google-chrome-stable --no-install-recommends

Run Chrome in headless mode:

google-chrome --headless --disable-gpu --dump-dom https://example.com > output.html

For Selenium or Puppeteer automation, install Chromedriver:

# Check your Chrome version first
google-chrome --version

# Download matching Chromedriver
wget https://chromedriver.storage.googleapis.com/LATEST_RELEASE_$(google-chrome --version | grep -oP '\d+' | head -1)/chromedriver_linux64.zip

# Extract and install
unzip chromedriver_linux64.zip
sudo mv chromedriver /usr/local/bin/
sudo chmod +x /usr/local/bin/chromedriver

Post-Installation Configuration

After installation, several configurations are available to optimize Chrome’s performance and usability on Debian 13.

To set Chrome as your default browser, open Chrome and navigate to Settings → Default browser → Make default. Alternatively, use the command line:

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

Auto–updates are enabled automatically when the package is installed via the repository method. Verify update configuration:

apt policy google-chrome-stable

For streaming services like Netflix or Amazon Prime, Widevine DRM needs activation. Chrome typically prompts you automatically when visiting these sites. If not, navigate to chrome://settings/content/protectedContent and ensure “Allow sites to play protected content” is enabled.

Hardware acceleration significantly improves performance, especially for video playback. Check acceleration status at chrome://gpu/. If features show as “Software only,” install the necessary Mesa drivers:

sudo apt install mesa-va-drivers mesa-vdpau-drivers

Sign in to Chrome with your Google account to sync bookmarks, passwords, and extensions across devices. This synchronization occurs automatically once configured, ensuring a consistent browsing experience across platforms.

Troubleshooting

Despite careful installation, issues can arise. Here are solutions to common problems I’ve encountered over the years of Chrome deployments.

When Chrome won’t launch, sandbox permissions are often the culprit. The error “The SUID sandbox helper binary was found, but is not configured correctly” indicates permission problems:

# Fix sandbox permissions
sudo chmod 4755 /opt/google/chrome/chrome-sandbox

Missing libraries prevent Chrome from starting, particularly on minimal Debian installations:

# Install common missing dependencies
sudo apt install libxss1 libappindicator3-1 libindicator7 libasound2 libgconf-2-4 libnspr4 libnss3 libpango1.0-0 fonts-liberation

If Chrome crashes after a Debian upgrade, graphics drivers often need updating:

# Reinstall graphics drivers
sudo apt install --reinstall xserver-xorg-video-all

# Clear Chrome's shader cache
rm -rf ~/.config/google-chrome/ShaderCache

To downgrade Chrome when a new version causes problems:

# List available versions
apt list -a google-chrome-stable

# Install specific version
sudo apt install google-chrome-stable=119.0.6045.123-1

# Prevent automatic updates
sudo apt-mark hold google-chrome-stable

Chrome Debian Uninstallation

For complete Chrome removal, including all configuration:

# Remove Chrome and its repository
sudo apt purge google-chrome-stable
sudo rm /etc/apt/sources.list.d/google-chrome.list
sudo rm /usr/share/keyrings/google-chrome.gpg

# Remove user data (optional - this deletes bookmarks and settings!)
rm -rf ~/.config/google-chrome
rm -rf ~/.cache/google-chrome

Alternatives to Chrome

While Chrome dominates the browser market, several alternatives might better suit your needs.

Chromium offers near-identical functionality without Google’s proprietary components. Install it simply with sudo apt install chromium. You’ll miss some media codecs and automatic updates, but gain better privacy and full open-source compliance.

Firefox, Debian’s default browser, prioritizes privacy and customization. It’s already installed on most Debian desktop systems and receives regular security updates through official repositories. Firefox’s container tabs and extensive privacy controls make it popular among security-conscious users.

Brave blocks ads and trackers by default while maintaining Chrome compatibility. Vivaldi offers extreme customization options, and Opera includes a free built-in VPN. Here’s a quick comparison:

Browser	Based On	Key Feature	Best For
Chrome	Chromium	Google integration	General use, streaming
Chromium	–	Open source	FOSS enthusiasts
Firefox	Gecko	Privacy controls	Privacy-focused users
Brave	Chromium	Built-in ad blocking	Ad-free browsing
Vivaldi	Chromium	Customization	Power users

---

Enterprise & Mass Deployment

Large-scale Chrome deployments require additional planning. Google provides an enterprise repository with extended support:

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

Apply Chrome policies via JSON configuration:

# Create policy directory
sudo mkdir -p /etc/opt/chrome/policies/managed

# Example policy file
sudo tee /etc/opt/chrome/policies/managed/chrome-policies.json <<EOF
{
  "HomepageLocation": "https://company.com",
  "DefaultBrowserSettingEnabled": true,
  "PasswordManagerEnabled": false
}
EOF

For unattended installation across multiple systems, we can can create a script using the follwing code:

#!/bin/bash
# Silent installation script
export DEBIAN_FRONTEND=noninteractive
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | gpg --dearmor -o /usr/share/keyrings/google-chrome.gpg
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/google-chrome.gpg] https://dl.google.com/linux/chrome/deb/ stable main" > /etc/apt/sources.list.d/google-chrome.list
apt-get update -qq
apt-get install -qq -y google-chrome-stable

Security & Privacy Considerations

Chrome collects browsing data for Google services, including search queries, visited sites, and usage patterns. Review privacy settings at chrome://settings/privacy. Consider disabling “Help improve Chrome’s features and performance” and “Make searches and browsing better” for enhanced privacy.

Chrome’s sandbox provides excellent security isolation. Verify it’s working:

google-chrome --print-sandbox-status

For additional security, integrate with AppArmor:

sudo apt install apparmor-utils
sudo aa-enforce /etc/apparmor.d/usr.bin.google-chrome-stable

Manage extensions carefully—they can access significant data. Regularly audit installed extensions at chrome://extensions/ and remove unused ones. Enable “Ask where to save each file before downloading” in settings to prevent drive-by downloads.

Debian Version-Specific Notes

While this guide focuses on Debian 13 (Trixie), users of other Debian versions should be aware of specific considerations.

Debian 11 (Bullseye) users might encounter older library versions. Install the backports repository for updated dependencies:

echo "deb http://deb.debian.org/debian bullseye-backports main" | sudo tee -a /etc/apt/sources.list
sudo apt update
sudo apt -t bullseye-backports install libseccomp2

Debian 12 (Bookworm) occasionally has Wayland compatibility issues with Chrome. If experiencing graphical glitches, force X11 mode:

# Edit desktop file
sudo sed -i 's/^Exec=/Exec=env GDK_BACKEND=x11 /' /usr/share/applications/google-chrome.desktop

Appendix: Useful Commands

Keep these commands handy for Chrome management and troubleshooting.

Check installed version:

google-chrome --version

Verify repository configuration:

apt policy google-chrome-stable

Launch with debugging output:

google-chrome --enable-logging --v=1

Check Chrome’s internal pages:

• chrome://flags/ – Experimental features
• chrome://gpu/ – Graphics acceleration status
• chrome://extensions/ – Manage extensions
• chrome://settings/ – Main settings
• chrome://version/ – Detailed version information

Clear Chrome cache from the terminal:

rm -rf ~/.cache/google-chrome/Default/Cache/*

FAQs

Conclusion

For installing Google Chrome on Debian 13, the repository method remains my recommendation for most users—it ensures you receive security updates promptly and simplifies system maintenance. However, the flexibility to install via .deb packages proves invaluable for offline systems or when specific version requirements are needed.