Where do iPhone web downloads go? Files, Photos and browser storage

A file you download or save from a website on an iPhone ends up in one of three places. Through Safari's download flow, it goes to the Files app. Saved with Save to Photos, it goes to your Photos library. Kept by the website itself, it goes into the browser's storage for that site, which no app on your phone shows you. The gesture decides, not the file: the same picture can go to any of the three, depending on whether you tap a download link, touch and hold to save it to Photos, or let a web app such as a PWA Lock vault keep it. The first two can sync through iCloud; the third stays in one browser on one device and can vanish without asking. Here is what each does, and where a PWA Lock vault fits.

Where do Safari downloads go?

Apple's answer is short: if you download a file onto your iPhone from the internet, you can find it in your Downloads folder in the Files app. Apple's article on finding downloads, linked in the sources below, gives two routes to it:

1. Open the Files app, tap Browse, tap iCloud Drive, then open Downloads.
2. If you have just downloaded something in Safari, tap the Downloads button next to the search field, then Downloads.

Notice where that folder sits: under iCloud Drive. If iCloud Drive is on, a Safari download is a cloud file from the moment it lands. Apple describes the default; if your phone's download location has been changed, Safari's Downloads list still shows what you downloaded.

What goes to Photos, and what iCloud Photos does with it

Save to Photos does what it says: the image or video joins your Photos library, not the Downloads folder, and becomes a photo like any other, visible to any app you have allowed to access your photos.

With iCloud Photos on, that library is synced. Apple's article on hiding photos says so in passing: photos you hide on one device are hidden on your other devices too. A photo saved from a web page syncs the same way, so unless iCloud Photos is off, expect it to reach your other devices and your iCloud storage.

For photos already in the library, Apple documents the Hidden album: touch and hold a photo or video, tap Hide, then confirm, and it moves to the Hidden album, which in iOS 16 and later is locked by default and requires authentication to open. Hiding is not deleting: the item is still in your library and, with iCloud Photos, still synced. PWA Lock does not touch your photo library; it cannot hide or remove existing photos or cloud copies, as What PWA Lock protects, and what it does not says.

What is browser storage, and why can you not see it?

Websites can keep data on your phone without creating a file you can see. Cookies are the familiar kind; modern sites also use larger stores, including one built for whole files, which MDN calls the origin private file system: private to the origin of the page and not visible to the user like the regular file system.

It belongs to one website in one browser

Other sites cannot read it, the Files app does not list it, and another browser has its own copy. On an iPhone there is one more split: a web app added to the home screen keeps its own cookies and storage, separate from Safari, so a file kept in a Safari tab is not there in the same site's home-screen app. Home-screen web app vs Safari tab explains the split.

The browser can evict it

Browser storage is best-effort by default: in MDN's words, it persists as long as the origin is below its quota, the device has enough storage space, and the user does not delete it through the browser's settings. Under storage pressure, browsers delete the least recently used sites first. WebKit's storage policy post lists its triggers (the overall quota exceeded, the device short of space, or a site not interacted with for some time) and puts the quota at up to 60% of disk space for a browser app or home-screen web app, so space is rarely the limit; durability is. Safari adds a rule of its own, described in WebKit's tracking prevention post: a site you have not interacted with in seven days of Safari use has its script-written data deleted, though home-screen web apps count their own days of use and are not expected to lose data this way.

Clearing website data deletes it

Clearing a website's data removes everything the site stored, files included; for the origin private file system MDN says simply that clearing storage data for the site deletes it. There is no trash to recover from. Before clearing website data: protect your local web-app files is the checklist to run first.

Where does a PWA Lock vault fit?

We make PWA Lock, so read this section knowing who wrote it. Each app you lock with PWA Lock can have a vault, a local store for its downloads, turned on by setting a vault passcode when you add the app (the iPhone setup guide shows the form). With a vault passcode set, downloads started inside the locked app, from a download link or the site's own script, are written to the vault instead of the Files app or the browser's downloads. Downloads continue while you move between the app's pages, but may not finish if iOS suspends or closes the app, so keep it open for a large file.

The vault is the third destination above: the origin private file system of the locked address, in that browser, on that device, with every property just described. It is local: nothing is uploaded to PWA Lock's servers, backed up or shared between devices, and the installed app and Safari each have their own vault. It is not encrypted by PWA Lock: the lock password gates the vault page, but anyone who can unlock the device and the app can reach the files. It can be evicted, since PWA Lock does not ask the browser for persistent storage, and clearing website data deletes it for good.

What the vault can do

To open it, perform the vault passcode on the lock page and enter the lock password, or tap the Vault button PWA Lock adds to the unlocked app. The vault lists your files with previews and a viewer for images, videos and PDFs. Each file has three actions: Rename, Save and Delete. Save hands a copy to the browser as an ordinary download (in Safari, the Downloads folder above) while the vault keeps its own; Delete is permanent, after a confirmation. Add files copies files you pick from your device into the vault, and the originals stay in Photos or Files, because PWA Lock never removes anything from those apps. There is no bulk export: files are saved out one at a time.

What the vault does not catch

Only downloads count. Touch and hold an image and choose Save to Photos, and it goes to Photos as usual: that is an iOS action, not a download. When the vault cannot take a file (another domain the app cannot read, not enough storage, or a browser without such storage), PWA Lock says so and hands the download to the browser instead. Without a vault passcode, downloads in a locked app are ordinary browser downloads.

The three destinations compared

Before you rely on any of them

• Decide the destination before you tap: a download link goes to Files, or to the vault in a locked app with a vault passcode; Save to Photos always goes to Photos.
• Know your iCloud settings, since both Files and Photos can be cloud destinations.
• Treat browser storage as temporary: keep a second copy of anything you cannot lose, and copy files out before clearing website data or removing a home-screen app (our sources do not say what removal does to its storage, so assume the worst).
• Deleting in one place deletes one copy; a file that has been in Files, Photos and a vault exists three times.
• If you need encryption, recovery or automatic backup, none of the three provides it, and neither does PWA Lock. How to choose a private file app for your iPhone explains what to look for.