Skip to content

Chromium Google Sync Not Working on Raspberry Pi? What to Do

Chromium on Raspberry Pi can sign in to Gmail and other Google websites. Its built-in browser profile cannot use Google's private Chrome Sync service. Choose below according to the data you want to use on another device.

Choose what you want to do

The Chrome installation steps target a 64-bit Raspberry Pi OS Trixie desktop. Run terminal commands on the Pi. For a 32-bit OS, choose the Chromium or Firefox routes. Google documents native Chrome's Linux ARM64 support in its platform announcement. Chrome for ARM64 Linux

Sign in to Google websites in Chromium

Open Gmail or Drive in a normal Chromium window, choose Sign in, and complete your Google Account login. Open another page from that service to check that you remain signed in. Google may ask for multi-factor authentication or an account security check.

If the website keeps returning to its login page, check that cookies are allowed for that service and that the Pi's date and time are correct. A browser-wide cookie clear signs you out of other sites, so inspect the affected site's settings first.

For browser bookmarks, passwords, history, or tabs on another device, use the matching route above. Those data have separate account settings.

Can Chromium sync with a Google Account?

Google restricted its private Chrome APIs for third-party Chromium builds on 15 March 2021. The old /etc/chromium.d/oauth2-client recipes and copied GOOGLE_DEFAULT_CLIENT_ID or GOOGLE_DEFAULT_CLIENT_SECRET values do not provide a supported way to restore that access. The original announcement explains the restriction. Chromium announcement

Install Chrome ARM64 for Google Sync

If Chrome is already installed, go directly to sign-in and the two-device check.

Check your Raspberry Pi before downloading

Confirm that both the CPU userspace and Debian package architecture are 64-bit ARM:

1
2
3
4
uname -m
dpkg --print-architecture
getconf LONG_BIT
cat /etc/os-release

For the ARM64 package, the expected results are aarch64, arm64, and 64. A Raspberry Pi with a 64-bit processor can still be running a 32-bit OS, so checking only the board model is not enough.

Download google-chrome-stable_current_arm64.deb

Use a fresh folder so you can identify this download. Stop at any failed command and use the Chrome ARM64 installation error guide before continuing.

1
2
3
4
5
6
7
8
chrome_download_dir=$(mktemp -d "$HOME/chrome-download.XXXXXX")
cd "$chrome_download_dir"
curl --fail --location --connect-timeout 15 --max-time 180 \
  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

Before installing, check that Package is google-chrome-stable and Architecture is arm64. The version changes as Chrome is released. A failed download, invalid archive, or mismatched architecture needs diagnosis before installation.

Install it with APT so dependencies are resolved:

sudo apt update
sudo apt install ./google-chrome-stable_current_arm64.deb

Verify Google Account data on two devices

Launch Chrome from the desktop menu or, as your normal desktop user, run:

google-chrome-stable
  1. Open Chrome's profile controls and sign in to the intended Google Account.
  2. Open the account's saved-data settings and choose the data you want to use across devices. History and open tabs have their own setting.
  3. Create a disposable bookmark, such as this guide, in Chrome on the Pi.
  4. Check that it appears in Chrome on another device using the same account, then remove the test bookmark when finished.

If it does not appear, compare the account and saved-data settings on both devices. Follow any account prompts, including an existing sync passphrase or organisation policy. Google's current instructions describe the sign-in and data controls. Chrome account sign-in

After installation, the Google repository configuration normally allows future Chrome updates through regular system upgrades. Verify the installed package and repository files with:

apt policy google-chrome-stable
ls /etc/apt/sources.list.d/ | grep -i chrome

If the ARM64 download returns 404 or another error

Do not substitute the AMD64 package. google-chrome-stable_current_amd64.deb targets x86-64 computers and will not run natively on Raspberry Pi OS ARM64.

Use one of these supported fallback patterns instead:

  1. Continue using the Raspberry Pi OS Chromium package.
  2. Synchronise bookmarks with an extension such as Floccus.
  3. Synchronise passwords with a cross-platform password manager.
  4. Use Firefox and Firefox Sync for whole-browser synchronisation.
  5. Recheck Google's official Chrome download page rather than using packages from an unknown mirror.

Avoid random third-party .deb files. A browser handles passwords, cookies, and session tokens, so package origin matters.

Keep Chromium and sync bookmarks

Floccus can synchronise bookmarks through Nextcloud, WebDAV, Google Drive, or another supported backend.

  1. Export your existing bookmarks and retain that backup while setting up sync.
  2. Install Floccus from the browser's extension store.
  3. Choose a backend and create a dedicated sync folder.
  4. Configure the same account and folder on your other browsers, checking each browser's local folder selection.
  5. Use one bookmark sync service for that folder on each browser to avoid conflicting updates.
  6. Run a manual sync on one device before enabling automatic sync everywhere.

Check the bookmark route: create one disposable bookmark in the chosen folder on the Pi, sync that profile, and check the same folder on your other browser. Keep the export until you have checked for missing or duplicate bookmarks.

Floccus also offers a separate open-tabs mode. Its guide calls that mode experimental and notes that duplicate tabs can occur. Start with bookmark-folder syncing if that is your goal. Browser history, cookies, and passwords need their own solutions. Floccus setup and tab-sync guide

Keep Chromium and sync passwords

A dedicated password manager is usually a cleaner option than trying to restore Chromium's retired Google API integration.

  1. Install the official extension from your chosen password manager.
  2. Enable multi-factor authentication on the vault account.
  3. Import passwords only after checking the import file and destination account.
  4. Delete unencrypted CSV exports after verifying the migration.
  5. Test autofill on non-critical accounts first.

Do not place a vault password, OAuth secret, or recovery code in a shell script or Chromium configuration file.

Use Firefox Sync instead

Firefox supports its own account-based synchronisation on Raspberry Pi OS:

sudo apt update
sudo apt install firefox

Open Firefox, select the menu, sign in to your Mozilla account, and choose the data types to synchronise. Make a disposable bookmark and check it on another signed-in Firefox device. Use the same account on both devices. Firefox Sync setup

Troubleshooting

dpkg: error processing archive ... package architecture (arm64) does not match system (armhf)

Your Raspberry Pi OS userspace is 32-bit. Reinstall with a 64-bit Raspberry Pi OS image if your board supports it, or use the Chromium/Firefox alternatives above.

curl: (22) The requested URL returned error: 404

The package is not currently available at that endpoint. Do not remove -f or install an HTML error response as though it were a Debian package. Use a fallback and check again later.

Chrome installs but will not start

Run it from a terminal to capture the error:

google-chrome-stable
journalctl --user -b --no-pager | tail -100

Confirm the system architecture and free disk space:

dpkg --print-architecture
df -h /

Use the Chrome startup and dependency error guide to interpret the message before choosing a repair command.

Signing into Gmail does not enable browser sync in Chromium

Website sign-in and browser-profile sign-in are separate. Signing into a Google website inside Chromium does not restore the private Chrome Sync API.

FAQ

Can Chromium on Raspberry Pi sync directly with a Google Account?

No. The Raspberry Pi OS Chromium build does not have supported access to Google's private Chrome Sync APIs. Use official Google Chrome when a compatible ARM64 package is available, or synchronise through another service.

Is Google Chrome ARM64 available for Raspberry Pi now?

Yes. Google's official download endpoint provides an ARM64 Debian package. Check its Package and Architecture fields as shown above before installation, and follow the download-error steps if the request fails.

Does changing OAuth client IDs re-enable Chromium Sync?

No supported configuration does this. Old guides that export GOOGLE_API_KEY, GOOGLE_DEFAULT_CLIENT_ID, or GOOGLE_DEFAULT_CLIENT_SECRET describe a retired workaround.

Can I install the AMD64 Chrome package with emulation?

It is technically possible to experiment with x86 emulation, but it adds complexity and performance overhead and is a poor choice for a security-sensitive daily browser. Prefer a native ARM64 browser.

How do I check that an update is available?

Use apt policy google-chrome-stable and apt list --upgradable. Install browser security updates promptly through sudo apt full-upgrade.

Donate