How do I share a folder of screenshots without sharing my whole photo library?

Sharing 30 screenshots of a recipe collection or 50 screenshots of receipts without exposing your entire photo library is a workflow that Apple's Photos app makes harder than it needs to be. The three available paths each have tradeoffs around privacy, recipient experience, and ongoing sync.

## Option 1: iCloud Shared Albums (built-in, but leaks)

Photos → tap "+" in the Albums tab → New Shared Album. Add 30 screenshots, invite recipients by Apple ID or email. Apple's <a href="https://support.apple.com/guide/security/cloudkit-end-to-end-encryption-sec3cac31735/web">CloudKit security guide</a> documents that Shared Albums are encrypted in transit but not end-to-end encrypted — Apple can technically decrypt them under subpoena, unlike your private library when Advanced Data Protection is on. Recipients can save any photo to their personal library with two taps, and there is no audit log.

## Option 2: Export to Files, share the folder

• Photos → select screenshots → tap the share icon → "Save to Files".
• Create a new folder in iCloud Drive titled "Recipes for Mom" or similar.
• Long-press the folder → Share → set permissions to "View only" or "Can make changes".
• Send the share link.

This is the most controlled option. Recipients see only what's in the folder, the folder can be revoked at any time, and there is no path back to your library. Files supports end-to-end encryption under Advanced Data Protection.

## Option 3: AirDrop a one-shot bundle

For in-person sharing — passing a stack of receipts to your accountant — multiselect the screenshots in Photos and AirDrop them as a batch. The recipient saves them to their device. Zero cloud trace, but no ongoing sync.

## Option 4: A dedicated screenshot organizer with folder sharing

Apps like Némos treat folders as first-class objects with their own ACLs. A "Recipes" folder in Némos can be shared as a CloudKit Shared Database with read-only or read-write permission to specific Apple IDs. Per the <a href="https://developer.apple.com/documentation/cloudkit">CloudKit framework documentation</a>, the shared database is isolated from the private database — there is no way for a recipient to traverse from the shared folder back to your full library. Sharing is revocable instantly. The folder concept also keeps the original screenshots in your library if you want them, or moved out if you don't.

## Why the Photos app makes this hard

Apple's Photos app uses a flat library model: every photo belongs to one container, with smart albums as live filters and shared albums as out-of-band copies. There is no concept of a private folder that hides from your main timeline. This is a deliberate design choice — the iOS Photos team has historically prioritized simplicity over org-chart-style hierarchies — but it means that "share these and only these" is a multi-step export workflow.

## Recommended pattern by use case

• One-time sharing of 5-30 screenshots: export to Files, share folder link.
• Ongoing sharing with family (vacation pics): Shared Album. Accept the limitations.
• Sensitive screenshots (financial, medical): export to Files with Advanced Data Protection on, share read-only link, set link to expire.
• Recurring workflow (every Sunday, share weekly receipts with accountant): dedicated organizer app with folder ACLs.

## Bottom line

There is no single-tap "share this album only" button in Apple Photos. The best built-in workflow is multiselect → Save to Files → share the folder with view-only permission. For recurring folder-level sharing, a screenshot organizer with native CloudKit Shared Database support handles it cleanly.