Which Apps Can See Your iPhone Photos?

iOS gives each app one of four levels of photo access: None, Add Photos Only, Limited (only the photos you pick), or Full (your entire library plus all of its metadata). You can see and change every app’s level in Settings under Privacy & Security, then Photos. For most apps, Limited is the safer default, and Full is rarely necessary.

The short answer: four levels of access

Photo access on the iPhone isn’t a simple yes or no. Since iOS 14, Apple splits it into four distinct levels, and the gap between them is large. Knowing which one an app really has is the whole game.

• None. The app can’t touch your library at all.
• Add Photos Only. The app can save new photos to your library, but it can’t read anything already in there. Camera and scanning apps often need just this.
• Limited Access (Selected Photos). The app sees only the specific photos you hand-pick, and nothing else.
• Full Access (All Photos). The app can read your entire library and everything attached to it, whenever it likes.

Most people tap “Allow” once when an app first asks and never think about it again, which usually means handing over Full Access by reflex. The rest of this piece is about why that reflex is worth breaking, and what to do instead.

What “Full Access” really exposes

When you grant an app All Photos, you hand it more than your pictures. It can read every photo and video in your library, and it can do so at any time, including in the background when you aren’t even using the app. Along with the images themselves, it gets all the metadata baked into each file: the GPS coordinates of where a shot was taken, the exact date and time, the device used, and even the faces iOS has recognized in your library.

That combination is more revealing than most people expect. The pictures alone can be sensitive, but the location and timestamp data draws a map of where you live, work, and travel, which is exactly why stripping location data from your photos is worth doing in its own right.

There’s also no ongoing signal when an app reads your library. iOS shows a green or orange dot when something uses your camera or microphone, but a Full Access app quietly reading your photos leaves no such indicator. That isn’t a scandal, it’s just how the permission works, and it’s the reason the level you grant up front matters so much: once an app has Full Access, you won’t get a nudge each time it looks. Here is how the four levels compare.

Level	What the app can do
None	No access to your library at all.
Add Photos Only	Save new photos to your library; cannot read existing ones.
Limited (Selected Photos)	See only the specific photos you pick; cannot browse the rest.
Full (All Photos)	Read your entire library and all its metadata, at any time.

Seen side by side, the jump from Limited to Full is enormous. One shows an app a handful of pictures you chose; the other opens the whole archive.

Why Limited Access is the right default

The Selected Photos option, added in iOS 14, quietly changed what the sensible default should be. Think about why apps ask for your photos in the first place. A messaging app wants to attach one picture. A social app wants a profile photo. A form wants a copy of a document. In every one of those cases, the app needs one or two photos at a moment you choose, not standing access to your entire camera roll forever.

Limited Access fits those cases exactly. When the app needs a photo, you pick it from a chooser, the app receives just that photo, and the rest of your library stays invisible. Nothing about the experience gets worse, and the app never sees the vacation pictures, the screenshots, or anything else you didn’t hand it. The rule of thumb is simple: default new apps to Limited, and only step up to Full when an app genuinely can’t do its job without your whole library.

Which apps actually need full access

Full Access isn’t always wrong, it’s just usually unnecessary. Some apps have a real reason for it, and telling the two groups apart is easy once you ask what the app’s core job is.

• Genuinely need Full Access: a dedicated photo-management, editing, or backup app whose entire purpose is to work across your whole library. It can’t organize or back up photos it isn’t allowed to see.
• Do not need Full Access: messaging apps, social networks, shopping apps, and anything that just needs the occasional single photo. Limited covers them completely.

If an app in the second group is sitting on Full Access, that’s the first thing to change. It gained nothing from the extra permission except the ability to read everything.

Camera access is a separate permission

One point trips almost everyone up: letting an app use the camera is not the same as letting it read your photos. They are two different permissions, controlled in two different places. An app that opens a camera view to snap something new, a banking app scanning a check, a messaging app taking a quick picture, uses Camera access and can capture that one image without ever touching your existing library. If it also wants to save the result, Add Photos Only is enough.

So when an app asks for full photo access “so you can take a picture,” it’s worth a second look, because taking a new photo doesn’t require reading your library at all. Photo Library permission is only ever about the pictures you already have. Keeping the two straight means you can hand an app the camera without also handing it your archive.

How to check and change photo access

Auditing your permissions takes about a minute, and doing it every few months is a good habit. Here’s the path:

1. Open the Settings app.
2. Tap Privacy & Security.
3. Tap Photos. You’ll see every app that has requested access, with its current level shown beside it.
4. Tap any app and choose None, Add Photos Only, Limited Access, or Full Access.
5. If you chose Limited, tap Edit Selected Photos to review or trim exactly which pictures that app can see.

iOS helps here too. Every so often it shows a reminder listing the apps that currently have full library access and offers to switch them to Limited. When that prompt appears, take a moment to say yes for anything that doesn’t truly need the whole library.

The real limit of permissions

Here’s the honest part, and it’s the one most privacy checklists skip. Tuning permissions is real, worthwhile hygiene, but it has a ceiling. Every level you grant, even Limited, is still a permission on the same photo library, the one where your most sensitive pictures live right next to your lunch photos and your screenshots.

Limited Access shrinks the exposure, but the sensitive photo is still sitting in that shared library. It’s one accidental “Allow Full Access” tap away from being readable, or one over-permissioned app away, or visible to anyone who picks up your unlocked phone and opens Photos. Permissions decide who can reach into the room. They don’t move the valuables out of it. For the handful of photos that really matter, that distinction is everything, and it points to a different kind of answer.

A stronger layer: keep the sensitive photos out of the library

For the small set of photos that are genuinely private, the most robust move isn’t a better permission setting. It’s not keeping those photos in the shared library at all.

That’s the idea behind an on-device vault like Arca. When you move a photo into Arca, it’s encrypted with AES-256-GCM using a key derived from your PIN through Argon2id, and it lives in the app’s own container, separate from your Photos library. No other app can request access to it, because it simply isn’t in the library any app can see. There’s no server and no account behind it either, so the photo was never uploaded anywhere in the first place.

To be precise about the limits, as always: a vault only protects the photos you actually move into it, and you have to delete the originals from your camera roll, or the exposed copy is still sitting there for permitted apps to read. It isn’t a backup, and it can’t protect the rest of your library. What it does is take your most sensitive photos out of the permission game entirely, so no app’s access level applies to them at all. Deciding where those photos should live in the first place is the larger question we work through in where to store private photos, and for the ones you keep in the regular library, tidying up how you hide photos on iPhone is a sensible companion step.

The bottom line

Which apps can see your iPhone photos? Exactly the ones you’ve allowed, at exactly the level you granted, and that level is usually more generous than it needs to be. Open Settings, then Privacy & Security, then Photos, set most apps to Limited, and keep Full Access for the few that really manage your whole library. Then, for the photos that are truly private, take the stronger step of moving them out of the shared library and into an encrypted vault, where no permission setting can reach them.