
Google Drive for desktop ended support for backing up to Google Photos on August 10, 2026, according to Google’s current help page. If older photographs are visible but new desktop exports stopped arriving, review the replacement workflow rather than repeatedly toggling a historical Drive setting. Google now documents manual uploads and browser-based folder backup from Google Photos. Verify a new intended file before treating the transition as complete.
Key Takeaways
- Drive for desktop photo backup has a documented retirement date.
- Browser folder backup and one-time manual import serve different needs.
- Automatic folder backup requires the documented browser session to remain running.
Confirm the missing file is a new local export
Locate the actual photograph on the computer and confirm its edited appearance, filename, and folder. Check the Google account open in Photos and whether the item is already present under a different nearby version. An old library remaining visible does not establish that new desktop files continue uploading.
Google’s computer photo backup guide states the August 10 retirement date explicitly. Its historical instructions for stopping Drive folder backup should not be read as a current promise that turning the old option on restores ongoing Photos backup. This change concerns the upload route; do not infer that Google deleted previously backed-up photographs.
Choose one-time import or folder backup
For a small approved delivery, open photos.google.com and use Create and add photos > Import photos, then choose the intended files and open them. This manual action is different from monitoring a folder for future files. Keep the source files until their presence and version are verified.
For ongoing folder backup, the same documented menu offers Back up folders. Choose the intended folders and review the browser’s permission request. Google documents this automatic route for a Chromium browser such as Chrome or Edge. Select a deliberate project destination rather than exposing unrelated client folders just because they share a parent directory.
The article says the Google Photos tab must remain open or the Photos Web App must remain running for automatic folder backup to continue. Closing that session can therefore explain why later exports did not arrive. A successful first upload does not establish continuous unattended backup while the required session is closed.
Respect unsupported source containers
Google says this browser backup method does not support directly backing up an Apple Photos Library. Do not select the library package and assume its internal organization will become a compatible photo folder. Use a documented supported route for that library and verify the individual files intended for your project.
Also distinguish this Photos backup transition from provider access inside another editor. The Google Drive thumbnail access guide concerns a separate application workflow. Seeing a file in Drive, seeing it in Google Photos, and selecting it inside an editor are different observations.
Verify the replacement and retain the project
Choose one newly exported photograph as a transition check. In Google Photos, open its information and confirm the backup status, intended account, and correct version. Record any displayed error instead of deleting the local original while an upload is unresolved. This is a proposed acceptance check, not a backup completed for this article.
Retain real local sources where your project requires them, using the offline file check. Add finished exports to the project asset retention plan. Close the transition only after the current upload route, running-session requirement, and a newly delivered file have been accounted for.
Related tasks
- My Archive Shows Every Photo. Why Are Some Unavailable Offline?
- How to Archive Imagild Assets Before the 90-Day Storage Window Ends
- Why Are My Google Drive Photos Blank in Photoroom's Picker?
Sources and scope
- Google Photos: Back up photos and videos on your computer: August 10, 2026 Drive for desktop backup retirement, browser folder backup, manual imports, Chromium requirement, running-tab condition, and Apple Photos Library limitation.
Based on complete supplied capture 017, including its explicit retirement date and replacement workflows, reviewed October 29, 2026. No account setup or backup test was performed. Current browser folder backup is distinguished from historical Drive settings.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.