How to Revoke a Shared Photo Link, and What It Cannot Undo
Revoking a shared photo link switches it off on the server, so the next person who taps it gets nothing. Every major platform can do this, and on most of them it takes under a minute. What none of them can do is reach the copies that already left: a saved download, a screenshot, and the thumbnail a chat app cached when the link was still live. Revoking is a stop, not a recall, and knowing which of those two you need is the whole decision.
What Revoking a Photo Link Actually Does
A share link is a lookup. The long string of characters at the end of the URL is a key into a record on the server, and that record is what decides whether anything comes back. Revoke the link and the record is marked dead. The URL still exists, in the sense that it is still sitting in whatever message you sent it in, but it now resolves to nothing.
This is why revocation is instant and why it is total for anyone who has not opened the album yet. There is no cache to wait out on the album itself and no propagation delay to worry about. The link either points at a live record or it does not.
It is also why revocation cannot be selective about people. A link does not know who is holding it. If you sent one link to fourteen people and you want thirteen of them to keep access, revoking is the wrong instrument - you want a second link for the thirteen, and then the first one killed. More on that below.
How to Revoke a Shared Photo Link on Each Platform
The control is never called the same thing twice, which is most of why people cannot find it. Here is where it actually lives.
Google Photos
- Open the shared album and tap the three-dot menu.
- Choose Options.
- Turn off Share, or delete the link if the album shows one.
Turning the link off and back on generates a new one, so the old URL stays dead. Google Photos has no setting that stops people saving from a shared album while it is live, so anything anyone wanted is already in their library by the time you get here.
iCloud
Apple has two mechanisms and they revoke differently. An iCloud Link - the temporary one you get from the share sheet - is killed by opening the item, tapping share again and choosing Stop Sharing. It also expires on its own after 30 days, which is short enough that many people never need to revoke it at all.
An iCloud Shared Album is different: it has subscribers rather than a link, so you remove the person from the album, or delete the public website link if you turned one on. Deleting the album removes it for everyone at once, including the photos, so check what else is in there first.
Dropbox and Google Drive
- Open the sharing settings on the folder or file.
- Find the existing link in the list of people and links.
- Delete the link, or set the access back to the owner only.
Both keep working the same way afterwards for anyone you shared with by name. Deleting a link does not remove a named collaborator, and removing a collaborator does not kill a link. They are two separate lists and you have to clear both.
WeTransfer
A free WeTransfer expires on its own after seven days and cannot be pulled back early from the free tier, which is worth knowing before you use it for anything you might regret. Paid plans let you delete a transfer, which takes the download page down immediately.
Which Platforms Let You Take a Link Back, and How Fast
| Platform | Can you revoke? | Where the control lives | Other links survive? |
|---|---|---|---|
| Viallo | Yes, per link | Share panel, on the link's own row | Yes |
| Google Photos | Yes, one link per album | Album menu, Options | N/A - one link only |
| iCloud Link | Yes, or wait 30 days | Share sheet, Stop Sharing | Yes |
| iCloud Shared Album | Per subscriber | Album, People list | N/A - subscribers, not links |
| Dropbox | Yes, per link | Share dialog, link settings | Yes |
| WeTransfer (free) | No, expires in 7 days | N/A | N/A |
Three Things Revoking Does Not Undo
This is the part worth being honest about, because the word "revoke" promises more than any product in this category delivers.
Downloads that already happened. A file that reached someone else's device is theirs now. Nothing you press afterwards travels down the wire and deletes it. If your album allowed downloads and the link was live for a week, assume the photos exist somewhere else.
Screenshots. The same, but worse, because there is no setting anywhere that prevents one. Every product that implies otherwise is selling a feeling.
Link previews already sitting in a chat. When you paste a share link into WhatsApp, iMessage or Slack, the app fetches a preview image and stores it with the message. Revoking stops the server handing out any new preview - a revoked Viallo link returns a locked response with no photo attached - but the thumbnail already rendered in that thread belongs to the messaging app, and whether it refreshes is the messaging app's decision, not yours.
So the honest ordering is: decide what a link may do before you send it, because that is the only moment you have real control. Turning downloads off on a view-only link is the setting that actually changes what is possible, and it has to be set at the beginning.
Revoking One Link Without Breaking the Others
The common mess is an album with one link that went everywhere. You post it in a family group, forward it to a colleague, drop it in a thread with people you barely know, and then one of those audiences has to go. With a single link there is nothing to do but kill it and re-send to everyone else, which is a small social disaster.
Viallo is a private photo sharing platform where an album can carry several links at once, each with its own settings, and each with its own revoke control on its row in the share panel. Viewers open any of them in a browser with no account and no app, the photos stay at full resolution with no compression applied, and the files are stored on servers in the European Union. Revoking one link leaves every other link on that album working, which is what makes "one link per audience" a workable habit rather than a fussy one.
Two other things revoke separately in Viallo, and people miss them. Sharing an album with a named person is its own kind of access with its own removal control, so killing every link does not remove them. And a profile link, the one that shows all your albums behind a single address, is revoked from its own screen rather than from any album.
When an Expiry Date Is the Better Move
Revoking is something you remember to do. Expiry is something you do not have to remember, and for most of the situations people worry about it is the better tool: a link sent to a client, a one-off gallery for an event, anything where you already know roughly when the reason for sharing runs out.
Viallo links have no expiry unless you set one - the field sits on the link and reads Never until you pick a date, and you can clear it back to Never later. After the date passes the link stops resolving on its own, exactly as a revoked one does. Dropbox offers the same thing on paid plans. Google Photos does not offer it at all, which is the single strongest argument for not using a Google Photos album link for anything time-limited.
If you are choosing between the two, the question is whether the end date is knowable. How long shared photo links last on each platform covers the defaults, and the ways to send photos to someone without an account is the better starting point if the problem is really the audience rather than the clock.
Frequently Asked Questions
What is the best way to take back a photo album you already shared?
Revoke the link itself rather than deleting the album, so the photos survive and only the access dies. Viallo puts a revoke control on each link's row in the share panel, so an album shared four different ways loses only the one you pick. Google Photos can also do it, from the album menu under Options, but it has a single link per album, so revoking it cuts off everyone at once.
How do I stop a Google Photos link from working?
Open the shared album, tap the three-dot menu, choose Options, and turn sharing off. The URL stops resolving straight away, and turning sharing back on later produces a different link rather than reviving the old one. Anyone who already saved photos from the album keeps their copies, because Google Photos has no way to block downloads while a link is live.
Is it safe to assume nobody can see the photos after I revoke?
Safe for anyone who had not opened the link, and not safe for anyone who had. Revoking stops the server answering, so a Viallo link that is revoked returns nothing at all, not even the preview image a chat app would normally show. It cannot reach a file someone downloaded or a screenshot they took, so treat those as gone.
What is the difference between revoking a link and setting it to expire?
Revoking is immediate and manual; expiry is scheduled and happens whether or not you remember. The end result on the link is identical, so the choice is really about whether you know the end date in advance. Dropbox and Viallo both let you set an expiry date on a link, while Google Photos shared albums have no expiry setting of any kind.
I sent one link to about thirty people. Can I cut off just one of them?
Not with that link, no - a link has no idea who is holding it, so revoking it removes everyone. The workable version is to make a fresh link, send it to the twenty-nine you still want, and then revoke the original. It is worth doing the reverse next time and giving each audience its own link from the start.