Skip to content

Update or Uninstall Google Chrome ARM64 on Raspberry Pi

Google Chrome on 64-bit Raspberry Pi OS is updated through APT, not by replacing browser files manually. Check the installed architecture, package candidate, and Google repository before repairing an update. When uninstalling, decide separately whether to preserve the local Chrome profile and whether to keep Google's APT repository.

Quick answer

Run sudo apt update, inspect apt policy google-chrome-stable, then use sudo apt install --only-upgrade google-chrome-stable. To remove only the application, use sudo apt remove google-chrome-stable; the profile under ~/.config/google-chrome is separate. Never install the AMD64 package on Raspberry Pi OS ARM64.

Check the installed package and architecture

1
2
3
4
5
dpkg --print-architecture
dpkg-query -W -f='${Package}\t${Version}\t${Architecture}\n' \
  google-chrome-stable
google-chrome-stable --version
apt policy google-chrome-stable

Expected package architecture is arm64. If the OS reports armhf, do not force-install the ARM64 package; the userspace is 32-bit even if the Raspberry Pi CPU supports 64-bit instructions.

Update Chrome with APT

Google's Linux documentation directs Linux users to update Chrome with the system package manager. Refresh package metadata, show the candidate, and upgrade only Chrome:

1
2
3
sudo apt update
apt policy google-chrome-stable
sudo apt install --only-upgrade google-chrome-stable

Close and reopen Chrome after the package update, then verify:

1
2
google-chrome-stable --version
dpkg-query -W -f='${Version}\n' google-chrome-stable

The browser's Help → About Google Chrome page can show version and restart status, but APT remains the update mechanism on Linux. See Google's Chrome update instructions.

Check whether the Google repository is active

Installing Google's Linux package normally adds a repository so APT can receive future releases. Inspect effective sources without printing unrelated credentials:

1
2
3
grep -RhsE '^[[:space:]]*(deb|URIs:).*dl\.google\.com' \
  /etc/apt/sources.list /etc/apt/sources.list.d/ 2>/dev/null
apt-cache policy google-chrome-stable

Interpret apt policy carefully:

Result Meaning Next action
Installed and candidate versions differ Update is available Use apt install --only-upgrade
Installed equals candidate APT sees no newer package Restart Chrome and check again later
Candidate is (none) Repository or package metadata is unavailable Inspect APT errors and repository files
Package architecture is not arm64 Wrong package or OS architecture Stop and verify before reinstalling

Do not paste an unknown signing key or repository line from a forum. A browser processes passwords, cookies, and session tokens, so repair it only from Google's package or documented repository configuration.

Fix apt update or repository errors

Capture the complete error first:

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

Common cases include a disabled source, an expired or missing signing-key configuration, a proxy/DNS failure, or a repository entry left by a partial installation. Follow the Chrome ARM64 installation error guide for architecture, dependency, keyring, sandbox, and startup failures.

If package identity is uncertain, download the current official ARM64 file and inspect it before installing:

1
2
3
4
5
curl -fL https://dl.google.com/linux/direct/google-chrome-stable_current_arm64.deb \
  -o google-chrome-stable_current_arm64.deb
dpkg-deb -f google-chrome-stable_current_arm64.deb \
  Package Version Architecture Maintainer
sudo apt install ./google-chrome-stable_current_arm64.deb

Continue only when the file reports package google-chrome-stable and architecture arm64. Do not substitute google-chrome-stable_current_amd64.deb.

Preserve the Chrome profile before repair

Bookmarks, local history, extensions, cookies, and settings normally live under:

1
~/.config/google-chrome

Package removal and profile removal are different operations. Before troubleshooting a suspected corrupt profile, close Chrome and move the directory to a timestamped backup:

1
2
3
pkill -x chrome 2>/dev/null || true
mv "$HOME/.config/google-chrome" \
  "$HOME/.config/google-chrome.backup-$(date +%Y%m%d-%H%M%S)"

Start Chrome to create a clean profile. If the problem remains, the profile was probably not the cause. Keep the backup until bookmarks and required local data have been verified; do not publish or casually share it because it can contain sensitive session data.

Uninstall Chrome but keep the profile

Close Chrome, then remove the package:

1
sudo apt remove google-chrome-stable

Google's Linux uninstall instructions also identify google-chrome-stable as the Debian package name. apt remove does not normally delete the user profile directory. Confirm package state and retained data separately:

1
2
dpkg-query -W google-chrome-stable 2>/dev/null || true
test -d "$HOME/.config/google-chrome" && echo "Chrome profile retained"

Use sudo apt purge google-chrome-stable only when you also want package-level system configuration removed. It still should not be treated as a command to erase personal browser data.

Decide whether to keep the Google repository

Keeping the repository is useful when Chrome may be reinstalled. If you intend to return permanently to Chromium, inspect which file owns the Google source:

1
2
grep -Rls 'dl\.google\.com' \
  /etc/apt/sources.list /etc/apt/sources.list.d/ 2>/dev/null

Review the exact file before disabling or removing it. Do not delete all APT source files or keyrings. After any repository change, run sudo apt update and ensure unrelated repositories still work.

Return to Chromium or Firefox

Install the replacement before removing local Chrome data:

1
2
3
4
sudo apt update
sudo apt install chromium
# or
sudo apt install firefox

Export bookmarks or verify Google Account synchronization before switching. Chrome and Chromium use different profile directories, and Chromium cannot use Google's private Chrome Sync APIs. For browser capabilities and measured performance, see the Chrome ARM64, Chromium, and Firefox comparison.

FAQ

Does Chrome update itself on Raspberry Pi OS?

Chrome's package is updated through APT on Linux. Installing Google's package normally configures its repository, while the browser may ask for a restart to activate the installed version.

Why does apt policy show no candidate?

APT cannot currently obtain a package from an enabled compatible source. Inspect sudo apt update, the Google repository entry, OS architecture, DNS, proxy, and system time before reinstalling.

Does uninstalling Chrome delete bookmarks and passwords?

Removing the Debian package and deleting the user profile are separate. Preserve ~/.config/google-chrome and confirm synchronized data before deleting anything.

Can I downgrade Chrome with an old .deb?

Avoid random archives and unsupported downgrades. Old browsers may contain known security vulnerabilities, and profile formats can change. Repair the official repository or reinstall its current ARM64 package.

Can Chromium reuse the Chrome profile directly?

Do not point Chromium at the live Chrome profile. Export or synchronize supported data, then let Chromium create its own profile.