Show one photo on iPhone without letting someone swipe through your library
Use Guided Access with touch disabled for a brief phone handoff, understand its limits and separate private files from everyday browsing.
The short answer
For a brief handoff, Guided Access can keep the iPhone in Photos and disable touch so the person cannot swipe to the next image. Restricting the phone to Photos alone is insufficient: if touch remains enabled, browsing inside Photos may still work. Set it up and test with an ordinary picture before relying on it in front of someone else.
Another simple option is to keep the phone in your hand. If you send a copy instead, you avoid handing over your library but give the recipient a file they can retain. Choose the option that matches your actual intention.
Set up the boundary before the handoff
In Settings, open Accessibility, then Guided Access. Enable it and configure its passcode. Open the photo, triple-click the side button (Home on older models), select Guided Access if asked, then turn off Touch in Session Settings or Options and start the session.
Apple notes that settings from a previous session may be reused. Verify the result instead of assuming the controls are configured correctly. Ending the session requires authentication through the Guided Access flow; follow the instructions for your iOS version. Apple also states that emergency services and Crash Detection are unavailable during Guided Access, so use it only briefly and end the session afterwards.
Run a rehearsal with harmless content
Try the exact actions you want to prevent: swipe horizontally, tap the screen, attempt to return to the library and attempt to leave the app. Confirm that you can end the session yourself. Do this before a social situation, not while another person is waiting with your unlocked phone.
This is a suggested verification procedure, not a report of a test performed on your device. Interface names and shortcut behavior can vary by version. If the result is uncertain, keep hold of the phone rather than treating an unverified setting as protection.
Choose the image as carefully as the setting
A single photograph can contain other private information: a notification in a screenshot, a document on a table, a reflection or an address in the background. Before handing over the screen, check what the image itself reveals. Disabling touch does not conceal visible pixels.
For a screenshot, crop irrelevant areas only if the result still serves your purpose. Do not assume cropping removes every hidden property when you later send a file. Read the location-sharing guide before sharing an actual copy instead of displaying it.
A handoff control is not long-term storage protection
Guided Access is a temporary interaction restriction. It does not reorganize the library or move private files into a separate vault. When you end the session, the phone returns to ordinary use. The Hidden album is another layer for reducing casual display, with its own access rules.
A vault is useful when you want selected photos, documents or notes kept behind a separate secret. It does not make an already-open screen private. Close your vault before lending the phone, and do not use the same memorable secret everywhere merely for convenience.
When sending a copy is the better option
If the person needs to zoom or examine details at their own pace, sending the intended picture may be easier than disabling every touch. Before sending, inspect the recipient, selected image count and sharing options. A copy received through a messaging app is outside your vault’s control.
The practical choice is therefore between showing an image temporarily, allowing interaction with an app, and distributing a file. Treat those as different permissions. The privacy checklist helps make this distinction a habit without changing your entire photo workflow.
Your checklist to keep
- I tested with a non-sensitive picture.
- Swiping and leaving the image are blocked as intended.
- I can end the session myself.
- I end Guided Access after the brief handoff.
Print this guide or save it as a PDF from your browser menu.
Sources and method
Descriptions of Kofrix are based on its current implementation. Planned features are distinguished from shipped features. This guide is not an independent security audit.