Practical guide · verified against the real thing
What Android backup actually covers (and what it quietly doesn't)
In one line: Google's phone backup is genuinely good and genuinely incomplete. The honest map: what's included, what needs separate arrangements, and how to prove your backup works.
Android's built-in backup is the reason most people who lose a phone lose less than they feared — and the reason some people lose exactly the thing they cared about. It is real backup, with real exclusions. This is the honest map of what's covered, what isn't, and the arrangements that close the gaps. (Why any of this matters — the cost of a phone with no backup — is documented with insurer data in the phone-death piece.)
What the Google backup covers
The device backup (Settings, then Google, then Backup — or Settings, then System, then Backup depending on the phone) captures, when enabled: contacts, calendar, Gmail (those live in the account anyway), device settings, app lists, call history, SMS text messages on most phones, photos and videos if Google Photos sync is on, and app data for apps that opted into the backup API — which is most of the big ones and by no means all apps. The restore flow works: a new or reset phone signed into the same Google account offers the backup back, and the phone reassembles itself to a recognisable degree within an hour.
What it quietly doesn't cover
Chat apps with their own backup systems. The biggest one: WhatsApp runs its own backup to Google Drive on its own schedule, under its own toggle — the Android backup does not include it, and a restore that skips WhatsApp's setup loses chats people genuinely never get over. Check the chat app's own backup screen, on its own schedule, with its own encryption option. Authenticator apps. The codes guarding your logins are deliberately hard to export; an authenticator's seeds may not survive a restore unless the app offers its own sync (several now do — turn it on, and know which of your apps have it). This is the gap that turns "phone died" into "locked out of everything" — the 2FA setup guide covers the recovery-code discipline that closes it. Anything in app-specific clouds. Notes apps, fitness history, game progress: covered only if the app syncs to its own account — and "sync" is not backup, as the sync-versus-backup piece explains; delete propagation applies to app accounts the same as to drives.
Making it actually work
Three arrangements. One: verify the master toggle is on and a backup has run recently — the settings page shows the last successful run; a backup that hasn't run since you installed everything that matters is decoration. Two: check the exclusions that apply to your actual apps — WhatsApp's toggle, the authenticator's sync, the notes app's account — each app's own screen, once. Three: do the restore rehearsal. The 3-2-1 principle (three copies, two media, one off-site) ends with "and test it", and the phone version takes ten minutes: note what the backup says it holds, factory-reset an old or spare Android if you have one (or borrow the flow mentally — the setup wizard's restore preview lists exactly what will come back). The preview alone is diagnostic gold: whatever is missing from that list is what you need to arrange separately, discovered now rather than in the worst week of the year.
Next