Google Android backups count toward storage cap: what changed and what to do

Google removed a long-standing exemption from its cloud storage rules this week. Starting July 7, Google Android backups count toward the storage cap on free accounts SMS messages, call history, and device settings now draw from the same 15GB shared quota as Gmail, Drive, Google Photos, and WhatsApp backups. Engadget and 9to5Google both reported the change two days ago, citing a Google spokesperson.

Google says the average storage increase is about 40MB. That's consistent with what text logs and configuration files actually weigh, and for most users it won't register. But the arithmetic isn't the story. Android backup is now fully inside the same shared pool as Gmail, Drive, Photos, and WhatsApp. For users already crowding that 15GB ceiling, this policy change is what tips them over. For everyone else, it's a reminder that their phones have been quietly uploading personal data to Google's servers for years.

Android backups count against Google storage now: what the old rules were

Until this week, Google applied an uneven accounting rule to Android backups. Photos and videos uploaded to Google Photos counted against the quota; so did photo and video attachments inside MMS messages. But SMS text content, call logs, and device configuration uploaded without touching the storage meter. That carveout is now gone, per Engadget's report two days ago.

Every data type visible in Android backup settings now counts. The newly metered categories are SMS and MMS message text, call history, and device settings, which have long included saved Wi-Fi networks and passwords, wallpaper, display preferences, and language and input configuration, according to 9to5Google. Android backup has covered this range of personal data since at least 2021, per a 9to5Google breakdown of the Backup by Google One rollout. The change is in how that data is counted, not what's collected.

The shared-storage consequence is what gives this policy its practical weight. That same 15GB free allocation already covers Drive, Gmail, Google Photos, and WhatsApp backups on Android. A full account blocks new uploads to Drive, prevents Gmail from sending or receiving, and stops Google Photos from backing up new images, per Google's support documentation. WhatsApp backups on Android have counted toward this limit for years. Android device backup joining that pool is the accounting becoming consistent at last, but it lands hardest on anyone already near the limit.

The rollout timeline and a control gap worth understanding

The policy and the new controls are not arriving together. That asymmetry matters.

The storage accounting change took effect July 7 for new Android backup users. Existing users will see it applied to their accounts over the coming months, per 9to5Google. Google has not confirmed a specific timeline by region or device model.

The new per-category toggles, which let users opt out of backing up SMS and MMS messages, call history, or device settings individually, are rolling out on a separate schedule over the coming weeks, per 9to5Google. They may not be visible on all devices yet. These sit alongside existing app-level backup controls in the device backup menu, per Engadget. The practical result: some existing users will see their quota usage change before they have the controls to do anything about it.

One behavior about those controls is worth understanding before using them. Disabling a backup category deletes the existing cloud copy of that data. But if the underlying backup settings aren't also changed, a fresh copy will reappear automatically the next time the device runs a backup cycle, per Google's support documentation. Deleting isn't a one-time action it requires disabling the category and leaving it disabled.

The restore tradeoff follows directly from this. The SMS history, call logs, and device preferences that now count against the quota are the same data that makes setting up a new or replacement phone feel complete rather than blank. Disable those categories and that data won't be available for a future restore. How-To Geek noted in May that Android backs up considerably more personal data than most users realize, and that disabling backup categories can remove that data from the device, not just from the cloud. That scope hasn't changed. Only what Google charges for it has.

Google account storage limit and Android backups: who actually needs to act

Google says the new data adds about 40MB on average, a figure corroborated by both Engadget and 9to5Google. Users well under 15GB are unlikely to notice the change. SMS history, call logs, and device settings are also the data that makes a phone transfer seamless, so disabling them to recover that space is almost always a worse trade.

Users close to the ceiling face a different picture. Gmail, Google Photos, and Drive are the likely sources of high usage, and clearing space there carries no restore risk. Check your total usage at Google's storage page before touching any backup toggles. Google's support documentation is direct about what a full account costs: no Drive uploads, no Gmail, no Photos backups. For users routinely bumping against the limit across multiple services, that's the real risk this policy change introduces.

Users who change phones frequently or rely on seamless device transfers will find the backup categories most valuable precisely when they're tempted to disable them. A missing call log or unsaved Wi-Fi password during a transfer is a minor inconvenience; losing all of them simultaneously is not.

For users who want tighter control over what Google stores regardless of quota, the new toggles offer a genuine improvement once they arrive. Disabling device settings backup carries relatively low restore risk for most people. Disabling SMS and call history backup carries a higher cost anyone turning those off should have a secondary migration plan in place first.

One other development worth noting: Engadget reported that Google began testing a reduced default free storage limit for new accounts earlier this year, cutting the maximum from 15GB to 5GB unless the user linked a phone number. That test is separate from this policy change, but it signals that Google's approach to free storage is under active review.

The users with the most urgent reason to pay attention are those already near 15GB. For them, the right sequence is: check total usage, address the larger sources of consumption first, then evaluate backup categories against the restore cost of losing them. For everyone else, this change mostly makes visible a backup process that's been running quietly in the background and, until now, outside the quota entirely.