Android users have waited years for finer control over device backups. That wait appears close to ending. Code in the latest beta of Google Play Services points to toggles that let people pick exactly which categories of information travel to the cloud.
The change arrives after long frustration with an all-or-nothing system. Right now, enabling backup sends SMS and MMS messages, call history, device settings, and every app’s data in one package. Many owners never wanted the full bundle. They simply had no practical way to refuse parts of it.
Android Authority spotted the work in version 26.22.30 of Google Play Services. The new interface replaces the blunt switch with individual controls for each major data type. Turn one off and the phone stops sending fresh copies. It also removes whatever version already sits in the cloud after a confirmation dialog. The design forces a deliberate choice rather than passive acceptance.
Storage pressure makes the feature timely. Google gives every account 15 gigabytes free. Backups eat into that quota alongside photos, mail, and Drive files. Excluding a few bloated messaging apps or games that store heavy caches can stretch limited space. It also trims backup time and mobile data consumption. Both matter when users sit on metered connections or slow networks.
But the update goes beyond simple checkboxes. It builds on earlier changes that brought back detailed backup views after a controversial simplification last year. Gadget Hacks noted the restored section now uses Material 3 Expressive containers. Each category lists its current storage footprint. Users see at a glance whether messages or apps dominate the total. Transparency of that sort has been missing for too long.
App data itself presents the thorniest problem. Developers decide what their software includes in the backup stream. Some apps push only essential preferences. Others shovel in cache files, downloaded content, or temporary databases. The standard limit sits at 25 megabytes per app per user with no extra charge. Yet many titles exceed practical value long before they hit the cap. Without per-app selection, the only escape was to disable backups entirely or hunt for obscure developer options.
Google tested that deeper layer months earlier. In November 2025, Android Authority reported on strings found in Play Services version 25.44.32 beta. Those strings described individual toggles for each installed app. The planned list would sort applications by size so heavy hitters appear first. Users could then exclude one title without touching the rest. That work has not reached devices yet. The newer category-level controls may arrive first and set the stage for the app-specific follow-up.
Recent developer documentation adds context. Android’s Large Backups API, updated in March 2026, lets apps push far bigger payloads when needed. It offers per-file scheduling and prioritization for cloud-only transfers. The existence of such tools shows Google wants richer backup capabilities. At the same time, it recognizes that not every byte deserves automatic protection. Giving users veto power aligns the system with actual needs instead of blanket policy.
Privacy considerations also factor in. Some owners prefer not to store sensitive chat histories or location-linked settings in Google’s servers. Others simply want to start fresh on a new phone without carrying over years of accumulated app cruft. Selective backup supports both impulses. It reduces the digital footprint left in the cloud while preserving the safety net for important information.
Of course, implementation details still matter. Disabling a category erases prior backups of that data. The confirmation step prevents accidental loss. Yet users must understand the consequence before they tap. Support pages from Google already explain the current unified backup process. They will need clear updates once the granular options appear.
The shift reflects broader pressure on Google to give Android owners more agency. Apple’s iOS has offered per-app backup choices and iCloud storage management for years. Android’s automatic service won praise for simplicity when introduced. Over time, that same simplicity began to feel restrictive. Restoring detail without sacrificing ease represents a difficult balance. The emerging design attempts exactly that.
Rollout timing remains uncertain. Features discovered in Play Services betas sometimes ship within weeks. Others linger for months or vanish. No public announcement has confirmed the controls. Google has not commented on the code findings. Early testers on X noted the screenshots and expressed relief that the company finally addresses a long-standing complaint.
Even so, the direction looks clear. Android backup moves from opaque automation toward informed selection. Users gain the ability to decide what deserves protection and what can stay local. The change trims waste, respects storage limits, and hands control back to the person holding the phone. For an operating system that powers billions of devices, that adjustment counts as significant progress.
Further refinements may follow. Per-app toggles could land alongside the category switches. Future updates might expose even more granular choices inside individual applications. For now, the immediate gain is the ability to say no to unwanted data without abandoning backup altogether. Many will welcome the option. Some have requested it for years.
WebProNews is an iEntry Publication