Google Enables Document Backup to Drive in Stable Play Services 26.26 Release

Google has rolled out automatic document backup from Android devices to Google Drive in the stable version of Google Play Services 26.26. The feature, which the company prepared for nearly a year, adds a new Documents option in Settings on Pixel phones under Accounts and backup. It remains disabled by default to avoid uploading the Downloads folder without user consent. Once enabled, supported files including PDF, DOC, PPT, XLS, ZIP and even APK files are copied to a new Android backups folder on Drive, with separate subfolders created for each device. The backup consumes storage quota and offers no automatic two-way sync, requiring manual cleanup when disabled. Traces of the capability first appeared in August 2025, followed by an official mention in February 2026 and beta testing before the current stable deployment.

AntiMalwareTranslated from Russian

Read at source

Google has finally activated automatic backup of documents from Android smartphones to the cloud. The feature, prepared by the company for almost a year, is now distributed in the stable version of Google Play Services 26.26.

On Pixel devices a new “Documents” item appears in the path Settings → Accounts and backup → Google Backup. By default the option stays turned off, so Google does not automatically feed Drive with the contents of the Downloads folder.

After activation, documents are uploaded to a newly created Android backups folder on Google Drive. Inside this folder a separate directory is created for each smartphone. Supported formats include PDF, DOC, PPT, XLS, ZIP and others; even APK files located in the downloads directory are included.

Users pay for the convenience with storage space: copies occupy quota in Google Drive. The settings page allows checking remaining capacity, freeing space or purchasing additional storage.

Disabling the backup does not delete already uploaded files, so manual cleanup of the Drive folder is required. Full synchronization is also absent: changes made on the device are not reflected in the cloud copy and vice versa.

First traces of the function were discovered in August 2025. In February 2026 Google officially mentioned it in a Play System update. The capability later appeared in the beta channel of Play Services and has now reached the stable build.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Other

Mail.ru Reduces Lifetime 1TB Cloud Storage Promo to Standard 8GB Quota for Select Users
Kimi K3 Open Model Surpasses Closed AI Leaders with Million-Token Context and 896 Experts
Innostage Completes Functional Testing of PT NGFW 1.10.3 Across 156 Criteria