If you are here, the trash is empty and the photos are not in it. The honest answer comes first: once the retention window has passed, Google cannot restore them. That is Google's own position, not our interpretation. But that does not mean every copy of the photo has ceased to exist, and the copies that survive live somewhere other than Google's servers.
The window is 60 days, or 30, and the difference matters
Google's support documentation sets out two different periods, and almost every article you will read quotes only the first.
Backed up photos and videos you delete stay in the trash for 60 days before being permanently deleted.
If the photos and videos were not backed up, they are permanently deleted after 30 days.
So the deadline depends on whether backup was switched on for those items. People who had backup off often assume they had 60 days when they actually had 30. If you are counting days since deletion and hoping you are inside the window, check which case applies to you before concluding you are too late, or too early.
Google is equally direct about what follows: photos and videos that were permanently deleted cannot be restored. There is no hidden appeal, no support ticket that reverses it, no second-tier trash.
Why recovery software cannot help with the cloud copy
This is worth stating plainly, because a great deal of advice on this topic is quietly dishonest about it.
Data recovery software works by reading storage media you physically control and reconstructing files whose directory entries were removed but whose data blocks have not yet been overwritten. A phone's internal memory, an SD card, a USB stick, a hard drive.
Google's servers are not media you control. No recovery tool can reach them, whatever its marketing says. If a product claims it recovers photos deleted from a cloud account past the retention window, that claim does not survive contact with how either the software or the cloud works.
There is one real exception, and it is the most promising avenue below: if a copy also existed on your device or SD card and was deleted there, that is an ordinary local recovery job, and software genuinely applies.
What is actually still worth trying
Work through these in order. They are ranked by how often they succeed.
1. The device's own storage, if sync was off. If backup and sync was not enabled, the phone's copy was independent of the cloud. It may still be sitting in the device's camera folder, or be recoverable from internal storage or the SD card because deleting a file marks its space reusable rather than erasing it immediately. Stop taking new photos on that device first: every new file risks overwriting the data you want.
2. Another device that synced the same account. A tablet, an old phone still logged in, or a computer running Drive for desktop or Backup and Sync may hold a copy that has not reconciled with the deletion, particularly if it has been offline. Check it before connecting it to the network.
3. A Google Takeout archive you made earlier. If you ever exported your data, the archive contains the photos as they were at export time. People forget they did this.
4. Wherever you shared the photo. This is the most underrated route. If you sent it in WhatsApp, Telegram, email, Slack or a group chat, or posted it, a separate copy exists in that conversation or service, entirely untouched by the Google deletion. The same applies to shared albums and partner sharing: the other person's library may still hold it.
5. Your own backups. A computer backup, an external drive, or a previous phone-to-computer transfer. If the photos ever passed through a machine you back up, look there.
For the local copy: scan the phone storage or SD card
Applies only to the device or memory card case above, where the file was deleted from storage you control. It cannot reach photos held on Google's servers, and nothing can once the window has closed.
What to do differently from here
The uncomfortable lesson in this situation is that a single cloud library is not a backup. It is one copy, synchronised. When something is deleted, sync faithfully propagates the deletion everywhere, which is precisely what it is designed to do.
A copy only counts as a backup if it is independent: on separate media, not automatically mirroring the deletions of the original. That is what would have made this recoverable, and it is the one change worth making today.
If you want the fuller version of that principle, our 3-2-1 backup strategy guide sets out how many copies to keep and where.
Keep an independent copy so this cannot repeat
An independent local backup does not mirror a deletion made in a cloud library, which is the specific failure described in this guide.
The bottom line
After the window, Google cannot restore the photos and no software can retrieve them from Google's servers. That part is settled, and pretending otherwise wastes time you could spend on the routes that work.
What remains is genuinely worth an hour: the device copy if sync was off, another signed-in device, an earlier Takeout export, and above all anywhere you shared the photo, since that copy was never Google's to delete.
Retention periods and the statement that permanently deleted items cannot be restored are taken from Google's published Photos support documentation, checked at the time of writing. Policies change, so verify the current wording for your account. We have not tested recovery against Google's servers and make no claim that any tool can do so. Commercial links carry the rel="sponsored nofollow" attribute; an affiliate commission may apply at no extra cost to you.
Recover photos & messages from your phone → EaseUS MobiSaver
iOS & Android · photos, contacts, chats · free scan
