Can't Delete Photos From Google Photos?
Google Photos won't delete, or deletes everywhere at once? Find which failure is actually yours, from SD card permissions to the wrong-account trap.
Swipe44
Photo Cleaner
Sort your photos with a swipe
Swipe44 goes through your camera roll one photo at a time.
Free · No sign-up needed
You tap delete and nothing happens. Or you get “Couldn’t delete.” Or worse: it deletes perfectly, and takes the copy off your phone at the same time.
Those are three unrelated problems, and almost every article about this hands you the same five steps for all of them. Clear the cache, restart the app, check sync, reinstall, empty the trash. That list fixes exactly one of the failures below.
So let’s work out which one is yours first.
Start here: which failure is actually yours?
Read these and stop at the first one that matches.
- You tap delete and get “Couldn’t delete,” or nothing at all happens. App-state problem, or an item Google Photos doesn’t fully own. See the “Couldn’t delete” section.
- “Delete from device” is missing or greyed out. The item isn’t confirmed backed up yet, so the app refuses to remove your only copy.
- It deleted, and then reappeared. Something else is re-uploading it. Another device, another account, or another app’s bin.
- It deleted, but no storage came back. It’s in the trash, and trash still counts.
- Only photos on the SD card refuse to delete. Removable-storage permission on Android. Different problem entirely.
- It deleted from your phone too, and you didn’t want that. That’s the designed behaviour, and it’s the next section.
Six symptoms, six causes. You almost certainly only need one section of this page.
The rule behind most of it: delete is coupled to backup
Nobody tells you this part until after it has already cost you something.
When you delete a photo inside the Google Photos app, it is removed from Google Photos and from your device. If the item was backed up, it disappears on every device signed in with backup turned on. One tap, multiple places. Google published a whole explainer in December 2025 trying to clear this up, which tells you how often it confuses people.
That single rule explains most “I can’t delete” complaints, because what the person usually means is “it deleted the wrong thing.”
The three deletes, and what each one touches
- Delete in the app (phone). Cloud copy and device copy, on every backed-up device.
- Delete from device. Local file only. The cloud copy stays. This option only appears once Google Photos has confirmed the item is safely backed up, which is why it vanishes or greys out on items still uploading.
- Delete at photos.google.com in a browser. Not cloud-only by default. Google’s help page lists “Android devices, iPhones, and iPads with Google Photos installed and backup turned on” among the places a deleted item is also removed from, and that applies to a browser delete too. It stays cloud-only if backup is switched off on those devices first.
The safe recipe for cloud-only cleanup
If you want to clear your Google Photos library but keep the photos on your phone, order matters:
- Turn backup off on every device holding copies you want to keep.
- Confirm you actually have those files locally, and ideally somewhere else too. This is the moment to back up photos before deleting, not after.
- Delete at photos.google.com in a browser.
- Empty the trash when you’re sure.
Do it in the other order and the deletion syncs down and takes your local copies with it. Turning backup back on afterwards does not undo that.
Deleted items are removed from shared albums and conversations you added them to, but they are not removed from Drive, Gmail, YouTube, or Blogger. A photo can survive your delete by living somewhere else in your Google account.
And if the real problem is that your quota is full while your phone has plenty of room, that’s a separate confusion with its own fix: Google Photos storage full but your phone is not.
When the tap does nothing: errors, greyed buttons, and SD cards
This is the app-state bucket. Work through these in order, because they’re sorted by how often they’re the answer.
1. Force-stop and reopen the app. Not just swiping it away. Settings, Apps, Google Photos, Force stop. A stale session is the single most common cause of a delete that silently does nothing.
2. Let pending uploads finish. An item mid-upload is in a half-committed state and the app will refuse to remove it. Check the sync status at the top of the Photos tab and wait for “Backup complete.”
3. Check whether it’s a Google Photos creation. Movies, animations, collages and other generated items aren’t ordinary library files and delete differently. Same for anything that arrived from Google Drive rather than your camera.
4. Clear the app cache. Settings, Apps, Google Photos, Storage, Clear cache. Do not tap Clear data or Clear storage unless you’re prepared for it: that signs you out and resets every in-app setting. Cache first, always.
5. Update the app. Delete behaviour has changed repeatedly with Android and iOS releases. An old build on a new OS is a reliable source of odd failures.
6. Sign out and back in. Last resort, and slow, but it rebuilds the sync state cleanly.
When “Delete from device” or “Free up space” is greyed out
Both of these do the same job: remove local copies of items already confirmed safely backed up. So both go quiet for the same reason.
If backup is paused, incomplete, waiting for Wi-Fi, or blocked because you’re out of quota, Google Photos considers nothing safe to remove, and reports exactly that. The app is protecting the only copy you have.
Fix the backup, then come back. “Nothing to free up” almost always means “nothing is fully backed up yet.”
The iOS one nobody writes about
Since iOS 26 there have been repeated reports, in Apple’s own developer forums and in Google’s community threads, of photo deletion failing at the system level: the confirmation dialog that’s supposed to appear never does, and the app sits there waiting for an answer that never arrives. This is reported behaviour rather than something Apple has acknowledged, and it affects any app that deletes photos, not just Google Photos.
If that’s what you’re seeing, the reported workarounds are unglamorous but effective: kill the app completely and reopen it, and if that fails, restart the phone. If deletes are failing across every photo app on your iPhone and not just this one, the fault is with the phone, not with Google Photos.
Android: SD cards, scoped storage, and the dialog you dismissed
If everything deletes fine except photos on your memory card, stop troubleshooting Google Photos. This is a permissions problem, and it has a specific fix.
Android has restricted how apps write to storage they didn’t create, and Google Photos may not be able to remove files from a removable card until you grant it access explicitly. On Android 7.0 and later:
- Open Collections.
- Tap On this device.
- Open the folder that lives on your SD card.
- Try the delete, and approve the permission prompt when it appears.
That prompt is the whole ballgame. Dismiss it once out of habit and every subsequent delete looks like a silent failure.
The system dialog that makes deletes look broken. On Android 11 and later, when an app wants to delete media it didn’t create, it can’t just do it. It has to ask the system to show you a confirmation, and if that dialog is cancelled or swiped away, nothing is deleted. No error, no explanation, no deleted photos.
This is scoped storage doing its job, and it’s why “I selected 300 photos, tapped delete, and they’re all still there” is such a common complaint. You probably dismissed a dialog. Select a small batch and watch for it deliberately.
Two more SD card realities:
- A write-protected or failing card rejects deletes quietly. If nothing at all can be removed from the card, and the card is old, suspect the hardware. Copy what you care about off it before you keep poking.
- Some files simply have to go through the phone’s own gallery app. Google’s help pages say so directly. If Google Photos won’t budge on a stubborn SD file, open Samsung Gallery or your manufacturer’s equivalent and delete it there.
Android’s habit of keeping several separate bins is a related headache, and it’s covered properly in Android storage full but nothing to delete.
It came back, or the space never came back
Two different endings to the same story, so take them in turn.
The storage didn’t move
Because the photos aren’t gone yet. They’re in the trash, still occupying your Google storage, and the space only comes back when they are permanently deleted.
Google’s help pages state that photos and videos stay in the trash for 30 days before permanent deletion, and the current pages give the same 30 days for backed-up and non-backed-up items alike. Older guidance drew a distinction between the two, so you’ll still find conflicting numbers in circulation. The reliable move is to look at the countdown label Google Photos shows on each item in the trash, since that’s the app telling you its own answer.
Either way, the step that actually reclaims quota is emptying the trash: Collections, Trash, More, Empty Trash. Everything before that is just moving the box into the hallway. Retention clocks across iPhone, Android, Samsung and Google are laid out side by side in how long photos stay in Recently Deleted.
The photo came back
Something re-uploaded it. The delete worked, and then got undone. Check these:
- A second device with backup on. Your old phone in a drawer, a tablet, a laptop with Drive for desktop. It still has the local file, it still has backup enabled, and it will cheerfully put the photo back.
- A second Google account. This one catches almost everybody. If two accounts are backing up the same folder, deleting from account A does nothing to the copy in account B. Check which account the Backup switch is actually signed into, and check whether a second account holds a duplicate library.
- Your gallery app’s own trash. Samsung Gallery and similar apps keep their own bin on their own clock. Restore something there and it re-enters the backup queue.
- Third-party sync. Dropbox, OneDrive, a manufacturer cloud, or a backup app can all repopulate a camera folder.
Deleting again before you’ve found the source is how people spend a whole evening deleting the same 400 photos.
Shared albums, Locked Folder, and the wrong-account trap
Some items refuse to delete because they were never entirely yours.
Shared albums. You can remove the items you added. You cannot remove someone else’s contributions. Only the album owner can remove a person from the album, and doing so takes their photos and comments with them. If you’re not the owner and you want out, you can leave the album, which removes your photos and comments and leaves the rest untouched.
Locked Folder. Items here are handled separately from the main library, and the rules depend on backup. With Locked Folder backup off, those items live only on the device and can be lost outright by a reset or an uninstall. With it on, they’re backed up and they count against your quota like anything else. Either way, “it won’t delete from my library” is often just “it isn’t in your library.”
The wrong account. Worth repeating on its own, because it’s the least covered cause of all. Open your profile picture in Google Photos and read the account name. Then check the Backup setting and read the account name there too. They are not always the same, and a photo you keep deleting from one account may be sitting comfortably in another.
Decide once, delete once
Look at what all of this has in common. Google Photos couples cloud, device, and multiple accounts behind one ambiguous tap, so a delete can silently do nothing, do too much, or get undone by a phone in a drawer.
That’s tolerable for one photo. It’s miserable for four thousand, which is the number most people are actually facing when they go looking for this article.
For the device side of that job, Swipe44 takes the opposite approach. It works only on the photos physically on your phone, breaking the camera roll into decks (Recents, Shuffle, or month by month) and giving you one swipe per photo: right to keep, left to mark. Duplicates are grouped on-device with perceptual hashing, so you review a cluster at once instead of hunting by eye. Marked photos collect in a pending pile you review before anything is destroyed, the batch goes through a single system confirmation, and you get a real freed-space figure at the end.
It runs entirely on-device. No account, nothing uploaded, and iCloud-offloaded originals are never downloaded just to be inspected. It won’t manage your Google Photos cloud library, and it shouldn’t pretend to. What it does is make clearing the phone itself a decision you make once instead of a tap you’re afraid of.
The rule that saves people, whichever tool they use: know which copy you’re deleting before you delete it. Turn backup off first if you want to keep the local file. Empty the trash if you want the space. Find the device that keeps re-uploading before you delete anything twice.
More on getting a camera roll under control over on the blog, or get the app and start with your worst month.
Swipe44
Photo Cleaner
Start with one month of photos
Swipe44 breaks your library into small decks and remembers every choice. After each cleanup it shows how much space you got back.
Free · No sign-up needed
Frequently Asked Questions
Why can't I delete photos from Google Photos?
There are four common causes. The item isn't finished backing up, so "Delete from device" isn't offered. It lives on an SD card that Google Photos hasn't been granted permission to write to. It's in a shared album you didn't create, so you can only remove what you added. Or the app is holding a stale sync state and needs a force-stop, a cache clear, or an update.
How do I delete photos from Google Photos without deleting them from my phone?
Turn backup off on every device where you want to keep the local copy, then delete the items at photos.google.com in a browser. Order matters: Google's help pages are explicit that a deletion is also removed from any phone or tablet that has Google Photos installed with backup turned on, browser or not. Do it in the wrong order and the deletion syncs down and removes the phone copies too, and re-enabling backup will not bring them back.
Why do my deleted photos keep coming back in Google Photos?
Something is re-uploading them. Usually a second device still signed in with backup on, a second Google account backing up the same folder, or a gallery app with its own trash that restored the file locally. Check every signed-in device before you delete again.
Why is "Free up space" greyed out or saying there's nothing to free up?
That tool only removes device copies of items Google Photos has confirmed are safely backed up. If backup is paused, incomplete, out of quota, or waiting on Wi-Fi, there is nothing it considers safe to remove, so it reports nothing to free. Let backup finish, then try again.
How long do photos stay in the Google Photos trash?
Google's help pages state 30 days, after which items are permanently deleted. Items sitting in the trash still count against your Google storage, so a delete frees no quota until the trash is emptied or the clock runs out. Each item shows its own countdown, so check that label if you're unsure.
Why won't Google Photos delete photos from my SD card?
Android requires an explicit permission grant before an app can delete from removable storage. Open Collections, then On this device, then the SD card folder, and approve the prompt when it appears. If the card is write-protected or failing, deletes will fail silently no matter what you grant, and some files have to be removed using the phone's own gallery app.
Can I delete a photo from a shared album I didn't create?
You can remove items you added yourself. Only the album owner can remove other people or their content. If you're not the owner, you can leave the album, which removes your photos and comments but leaves everyone else's in place.
Does deleting photos in Google Photos free up phone storage?
Only if the device copy is removed as well. Deleting in the app on your phone removes the local file too, which is exactly why so many people lose photos they meant to keep. Deleting on the web frees cloud quota once the trash is emptied, and it leaves your phone alone only if backup is switched off there first, since a deletion otherwise syncs down to every device with backup on.