Save Photos From a Shared Album on iPhone
Saving a photo out of a shared album on an iPhone goes through the iOS share sheet: tap Save, then choose Files, Photos or whatever else you keep things in. In a mobile browser the file comes down the moment you tap. Either way what lands is the original the sender uploaded, at its full pixel dimensions.
Why a download can do nothing at all inside an app
A phone app that is really a website in a shell has no Downloads folder behind it, and that one missing piece breaks the most ordinary thing a page can do.
When a web page hands your browser a file, the browser knows where to put it. On a Mac it goes to Downloads. In Safari on an iPhone it opens and iOS offers to keep it. The page never has to know any of this. An app built as a shell around a website has no such browser: the view it renders in is a single tab with nothing underneath it, so a file handed over the same way has nowhere to go. It does not fail loudly. The tap just does nothing, which is why the honest description of the old behaviour is that the button appeared to be ignored.
The way out is the share sheet, the panel that slides up when you tap the square with an arrow in it anywhere in iOS. It accepts a file from a web view, and from there the photo can go to Files, to Photos, to AirDrop or to any app you have installed. There is one catch, and it is the reason saving takes two taps instead of one: iOS only opens the sheet during a tap you just made, and that permission expires in a couple of seconds. Fetching a 12 megapixel original over hotel wifi takes longer than that. So the photo is fetched first, and the sheet opens on a second tap once the file is already in hand.
Viallo is a private photo sharing platform built around links rather than accounts: whoever you send an album to opens it and looks at it, with no signup in the way, and the photos sit in storage at the size they were taken with nothing scanning them. Its iPhone and Android apps are shells around that same web app, which is why the saving story above is a phone story rather than a Viallo story - it is what every app of that shape has to solve.
What happens when you tap save
Four things you might be holding, four slightly different routes to the same file:
| Where you opened the album | What the tap does | Where the photo ends up |
|---|---|---|
| Viallo app on iPhone or iPad | Fetches the photo, then opens the share sheet on your next tap | Wherever you pick: Files, Photos, AirDrop, another app |
| Safari or Chrome on an iPhone | Opens the file straight away, no second tap | Files, or your camera roll through the share icon |
| Any browser on Android | An ordinary download | The Downloads folder, and the gallery picks it up |
| Mac or Windows browser | An ordinary download | Your Downloads folder |
In the app, the two taps are labelled for what they are. The first one starts the fetch and a card appears in the album telling you how far along it is. When the file is ready the card says "Tap Save, then choose where to keep it" and grows a Save button, and that button is the one that opens the sheet. If you change your mind and swipe the sheet away, nothing is lost: the photo stays prepared, so tapping Save again opens the sheet without downloading anything twice.
Saving more than one photo at once
Select several photos and they arrive as one zip file. The archive is built on your own device, in the page, and it is built in store mode, which means the photos go in whole. A zip is a container here and not a compressor: a 38 MB file goes in at 38 MB and comes out the other side byte for byte the same.
Photos come down three at a time, and one that stumbles is retried once before it counts as failed, which is the difference between a batch that finishes and a batch that dies on a single dropped connection. The card in the album counts them as they land, and it sits in the page above the grid rather than floating over your photos.
There is a ceiling, and it is worth knowing before you select an entire summer. Because the zip is assembled in memory on the device, the total is capped at roughly 600 MB of originals on a phone and 1 GB on a desktop. At four megabytes a photo that is about 150 pictures from a phone camera, or a couple of dozen raw files. Past the cap you get told to select fewer and go in batches, which is a better outcome than a tab that runs out of memory, reloads, and leaves you with nothing.
What you get is the file the sender uploaded
Every photo in a Viallo album is stored three ways: a thumbnail for the grid, a display copy for the lightbox, and the original exactly as it arrived. Saving fetches the third one. The picture you end up with is not a re-encode of a preview, and it is the same file whether you are the owner or someone who followed a link.
That is worth spelling out because it is not what most sharing does. An iCloud Shared Album serves photos at up to 2048 pixels on the long edge, so what an Android friend saves off the web link is a resized copy and not the shot. WhatsApp re-encodes on the way in. If a Google Photos library was backed up in storage saver quality, the compression already happened before anyone pressed download, and no amount of downloading gets the original back. Our guide to sharing photos in full resolution walks through which services keep the pixels and which quietly do not.
What travels with the file is whatever the original carried, which for a phone photo usually includes the camera, the timestamp and, unless it was stripped before upload, the coordinates. We measured how much of that survives a round trip through two public platforms in which photo metadata survives a download, and the short version is that platforms drop it field by field rather than all at once.
What other services hand a viewer
The question behind "can they save it" is usually two questions: what does the person on the other end have to sign up for, and how long do they have before the link stops working.
| Service | What the viewer needs | What a saved photo is | How long the link lasts |
|---|---|---|---|
| Viallo | The link, nothing else | The original file | Until the owner revokes it or its expiry date passes |
| Google Photos shared album | The link to look; a Google account to join in | Whatever was uploaded, storage saver re-encode included | Until the owner stops sharing |
| iCloud Shared Album | The public link, or an Apple ID to contribute | Up to 2048 pixels on the long edge | Until the owner deletes the album |
| WeTransfer | The link, nothing else | The original file, as a zip | 7 days free, 28 days on Pro |
| The app and your number | A re-encoded copy | As long as the chat survives |
For getting a hundred untouched files to a client this week, WeTransfer is the better choice because it does exactly one job and does not ask the recipient for anything. For photos a family should still be able to open next spring, it is the wrong tool, and the reason is in the last column rather than anything to do with quality. If the recipient having to make an account is the thing you are trying to avoid, we compared the ways to share photos without an account in detail.
When the owner has turned saving off
Not every album is meant to be taken away, and the person who made the link decides. On a view-only link, saving can be switched off: the Save buttons are simply not there, and the grid stops offering the long-press and right-click menus that would otherwise get you the image.
The switch only exists on view-only links, which is deliberate rather than an oversight. Anyone you have invited to add their own photos to an album can obviously also keep the ones already in it, so hiding a button from a contributor would be theatre.
And it is worth being blunt about what turning it off does and does not achieve. It removes the easy path. It cannot stop a screenshot, and nothing that shows someone a photograph ever can. It is a way of saying "these are for looking at" to people who will respect that, which covers most albums and none of the hard cases. The trade-offs are laid out in our piece on view-only photo sharing.
If a save is not working
- Check whether the album shows a Save button at all. If it does not, the owner has turned saving off for that link, and no amount of retrying will change it.
- In the app, wait for the card to say the photo is ready, then tap Save. The first tap fetches, the second one opens the sheet.
- If you are saving a batch and it stops with a size warning, select fewer photos. The cap is around 600 MB on a phone.
- If a link opened inside a chat or a social app and nothing at all happens, open it in Safari or Chrome instead. In-app browsers are the same kind of environment as the one described at the top of this page.
Frequently Asked Questions
What is the best way to save a whole shared album to an iPhone?
Select the photos in the album and save them as one zip rather than tapping through them individually. Viallo builds that zip on the device in store mode, so the files inside it are the originals rather than re-encoded copies, and it caps a phone batch at about 600 MB so the browser tab does not run out of memory. An iCloud Shared Album is the wrong comparison here, since it serves photos at up to 2048 pixels on the long edge whatever you do with them.
How do I save one photo from a shared album without an account?
Open the link, tap the photo, and use the save control in the top bar. Viallo asks viewers for nothing at all, so there is no signup between the link and the file, and the photo you get is the one the sender uploaded. Google Photos will let you look at a shared album from a link too, but joining it, saving into your own library and adding photos of your own all want a Google account.
Is it safe to save photos from a link someone sent me?
Saving an image is about as safe as browsing is, since what arrives is a picture file rather than anything that runs. The thing worth knowing is what rides along inside it: a photo straight off a phone usually carries the time it was taken and often the coordinates, so a file you then forward carries those onward too. Strip the metadata before resharing if the location matters.
What is the difference between saving from the app and saving from Safari?
Only how many taps it takes and where the file lands. Safari can write the file itself, so one tap does it; the app has to hand the file to the iOS share sheet, so you tap once to fetch and once to save. The bytes are identical either way, because both are fetching the same stored original rather than a copy made for the screen.
Why did nothing happen when I tapped download?
Almost always because the page was open inside an app rather than in a real browser - an in-app browser from a chat or a social feed has nowhere to put a file, and the tap dies silently. Opening the same link in Safari or Chrome fixes it immediately. In the Viallo app itself this was the behaviour until September 2026, when saving moved to the iOS share sheet.