Bitwarden saves the change instantly and the other device never sees it. Or the vault opens on a new phone and looks empty. Both get called "not syncing", and they are different faults: one is a client that will not pull, the other is a client pointed at the wrong account or the wrong server.
Bitwarden keeps an encrypted copy of your vault on every device you use. Saving an item pushes it to the server straight away; the other apps pull it down when they log in, when they unlock, and periodically while they stay unlocked. That asymmetry is the whole bug: pushing almost never fails, pulling does.
The one check that halves the search
Open your web vault at vault.bitwarden.com (or vault.bitwarden.eu, or your self-hosted address) in a browser and look for the missing item.
- The item is in the web vault — the data is on the server, so exactly one client is failing to pull. Go to the client in question and work through causes 3 to 9.
- The item is missing everywhere — the save never left the device. That is not a sync problem: the extension was locked, the account was offline, or the item was saved to a collection you cannot read back. Check "All items" with every filter cleared before anything else.
Personal items in the web vault are always in sync with the server by definition — the web vault is the server-side view. Organisation items only sync to other clients every 30 minutes, which is why a shared login can lag while your own logins arrive instantly.
1. The device is pointed at the wrong server, not the wrong password
Bitwarden runs two independent clouds: bitwarden.com (US) and bitwarden.eu (EU), plus whatever you self-host. They hold separate data. Logging in at the wrong region does not error — it creates a brand new, perfectly valid, empty account, or logs you into an old one you forgot about.
The tell is an empty or stale vault that still accepts your master password. On the login screen, the Region selector (or the server URL field, in the self-hosted build) sits under the email box. On mobile it is behind the region dropdown on the account screen. Set it to the region you registered in.
# Self-hosted: is the base URL actually your server?
# Browser extension -> Settings -> About / CLI:
bw config server https://vault.example.com
bw status
# A wrong or expired certificate looks like a sync failure in the client
# and like a TLS error here.
curl -sS -o /dev/null -w '%{http_code}\n' https://vault.example.com/api/config
2. A second account with a different email
Aliases and plus-addressing hide this well: you+bitwarden@gmail.com is not you@gmail.com, and it is a separate account with a separate vault. Bitwarden's client only syncs the currently active account when you use account switching, so a device left on the other profile keeps looking stale.
Check the email printed in each app's settings and compare it character by character. If you deliberately run two accounts, switch to the one you expect before concluding anything.
3. Nothing has pulled yet — do a manual sync
"Regularly while unlocked" is not "instantly", and the interval is not something you can tune on a per-device basis in the current apps. Sync by hand first; it costs ten seconds and rules out half of this list.
| Client | Where the button is |
|---|---|
| Browser extension | Settings tab → Vault options → Sync vault now |
| Android / iOS | Settings tab → Other → Sync now |
| Desktop app | File menu → Sync vault |
| CLI | bw sync |
| Web vault | No button exists — log out and log back in |
On mobile you can also turn on Allow sync on refresh (Settings → Other), which makes the pulldown gesture on the Vaults tab trigger a sync. That is the fastest habit to build: pull down, and if the item is still absent, the cause is below.
A useful side effect: the sync button reports failure. If it errors instead of finishing silently, the cause is usually 4, 5 or 9, and the error text narrows it immediately.
4. The device clock is off, so TLS fails
Bitwarden's own troubleshooting note lists this first, and it surprises people: a wrong system time does not produce "wrong time", it produces a certificate validation failure, which the client reports as a sync error. Phones that have been offline for weeks, laptops dual-booting Windows and Linux, and VMs restored from snapshots all hit it.
Set the clock to automatic, then sync again. If the device is more than a few minutes off, the error message usually mentions certificates, SSL or handshake — treat that as a clock bug before you suspect the server.
5. A VPN, ad blocker or DNS filter is eating the connection
Bitwarden's troubleshooting page names VPNs and ad-blocker extensions as a known interference source, and it is seen almost entirely in browsers. A blocker that rewrites requests to api.bitwarden.com, a corporate proxy that inspects TLS, or a DNS filter that blackholes the API host all look like "the extension is broken".
Test in a clean profile with extensions disabled, or disable the VPN for one sync. If it works there, whitelist the API host in the blocker and move on. This is also the single most common cause on managed work laptops where a proxy is mandatory.
6. The item exists, but a filter is hiding it
A "missing" item that is actually present in a folder, a collection or a different item type is the cheapest cause to rule out and the most common false alarm. An item saved into an organisation lands in a collection; if you are not assigned to that collection, the client cannot show it — and no amount of syncing changes that.
- Clear the search box, then select All items and All vaults.
- Check the item type filter (login / card / identity / note); a new entry saved as a note is invisible under "Logins".
- For organisations: an admin must assign the collection to your account, and organisation data syncs on a 30-minute cadence.
7. The local cache is stale or corrupt
A server update that changes the API, an interrupted sync, or a crashed app can leave a client with a local database it will not refresh. The fix is to throw the local copy away and pull a clean one — log out, not lock.
Logging out deletes the device's encrypted cache; logging in rebuilds it from the server. If that device holds the only copy of something that never synced, export the vault first (Tools → Export vault), because logging out will not get it back.
# Order matters
# 1. Export the vault to a .json or .csv on the failing device
# 2. Log out (do not just lock)
# 3. Log back in, choose the right region, complete 2FA
# 4. Sync once manually, then check "Last sync" in settings
# Still empty after that? Reinstall the app / remove and re-add the
# browser extension, then log in again. On Android, also clear the
# app cache (not the app data) before reinstalling.
8. The client or self-hosted server is out of date
Current clients talk to a current API. On the official cloud everything ships together, so this is rare there. On a self-hosted install it is routine to update the clients and forget the server, or the reverse — and an outdated client fails silently on newer endpoints: login works, sync does not.
Check the version in each client's About screen, and check the server version in the admin panel. Update the server first, then the clients.
9. It is actually an outage
Bitwarden publishes status.bitwarden.com and the clients only surface a red banner during outages that the team has already acknowledged. If every device is stale at the same moment, check the status page before touching any device — and do not log out of a device during an outage if it is your only unlocked copy.
When the vault is empty on Android, it is usually autofill
"Bitwarden not showing up on Android" is a different failure with a different fix: the vault is synced, but Android's autofill framework does not offer it. Enable Settings → Autofill services → Bitwarden, then set Bitwarden as the preferred service in the same screen. On Samsung and Xiaomi builds, also exempt Bitwarden from battery optimisation, or the background service is killed between unlocks and the fill popup never appears.
What not to do
- Do not clear app data or uninstall before exporting. The local cache is the only copy of anything that has not synced; deleting it fixes the app and loses the item.
- Do not re-create the item on the second device. You will get two entries that then diverge, and one of them will be the wrong password at the worst moment.
- Do not disable 2FA to "make syncing simpler". It has nothing to do with sync and it is the thing protecting the vault you are trying to repair.
- Do not assume a deleted item comes back. Sync propagates deletion like any other change; it is the one operation you cannot undo from a device that was offline.
Frequently asked questions
How long should a sync take?
Personal items are pushed instantly and pulled on unlock or within minutes. Organisation items are documented at every 30 minutes. If an item is older than an hour behind on an unlocked client, it is a fault, not a delay.
Can I force a sync from the web vault?
No. The web vault has no sync control because it reads its state from the server on every load. If the web vault shows old data, the problem is server-side or you are looking at a different account or region.
Does logging out delete my vault?
It deletes the local copy only. The vault on the server is untouched, which is why logging back in restores everything — and why anything that never reached the server is gone.
Why does one device sync and another never does?
Because the fault is per-client. Take the failing device alone through causes 3 to 7 in order; the healthy device is the proof that the server and the account are fine.
I changed my master password and now a device will not sync. Why?
Older sessions are invalidated by a master password change. That device needs to log in again with the new password; a locked session cannot re-key itself.
Is my vault safe while it will not sync?
Yes. The local copy stays encrypted, and the server never sees your master password. The risk is the opposite direction: an unsynced device is a device whose only copy of a change is on that device.
Where this fits
Sync is the one part of a password manager you cannot test until it fails, so build the habit before it does: export monthly, keep a second device you actually log into, and store the recovery codes somewhere that is not the vault. If you are choosing a manager rather than repairing one, the password manager guide covers what the encryption actually protects, and the Bitwarden vs 1Password and KeePassXC vs Bitwarden comparisons cover the trade-offs that matter when offline access and self-hosting are in scope.
And if a login has already leaked, fixing sync is not the fix: change it, check it against a breach list with the breach check walkthrough, and make sure it is not reused.