The short comparison
| Question | Hidden Album | Encrypted vault |
|---|---|---|
| Removes items from the ordinary Photos view | Yes | Yes, after a successful import and deliberate removal of the source |
| Requires authentication to open | Locked by default on current iOS versions | Uses the vault's own access control |
| Keeps the photo inside Apple Photos | Yes | No, for the app-managed protected copy |
| Syncs through iCloud Photos | Yes, when iCloud Photos is enabled | Depends on the vault's separate backup design |
| Encrypts the managed file with a vault-specific key | No separate vault key | Yes, when the vault is implemented as described |
| Protects a photo while it is open onscreen | No | No |
What the Hidden Album does well
Apple says a hidden photo leaves the Library, ordinary albums, and the Photos widget. The Hidden collection is locked by default and can be removed from view in Photos settings. This is convenient, built in, and often enough to prevent accidental exposure while someone browses an otherwise unlocked phone.
The album still belongs to the Photos library. If iCloud Photos is on, the hidden state synchronizes to other devices using the same Apple Account. A hidden item can also be managed through iCloud.com. Hiding is therefore not the same as moving the file into a separate, app-controlled encrypted container.
What an encrypted vault changes
An encrypted vault imports a copy into storage controlled by the vault app, encrypts the content with a key, and requires vault access before decrypting it for display. With pattern-locked vaults, NullVault is designed so that a pattern addresses a particular vault instead of opening a visible master list.
That distinction matters on a locked vault: someone who can inspect stored files should find ciphertext rather than an ordinary image. It does not make the app installation, storage allocation, or every trace of use invisible. Read the security architecture for the intended boundary.
Authentication is not the same as encryption
Face ID, Touch ID, a device passcode, or an app pattern decides when an interface should unlock. Encryption decides whether the stored bytes are intelligible without the required key. A product can have a convincing lock screen but leave the underlying files readable, so look for a clear explanation of both controls.
The reverse is also important: well-encrypted storage can still be exposed after a legitimate unlock. Once a photo is rendered, a person can see the screen, another camera can photograph it, and a compromised operating system may observe plaintext.
Which should you use?
Use the Hidden Album when your main goal is convenience and reducing casual discovery inside Photos. Use an encrypted vault when you want a separate protection boundary, independent locking, controlled exports, or backup that is distinct from the Photos library.
You may use both during a careful transition, but avoid losing track of duplicates. After importing into a vault:
- Verify the complete item opens after locking and unlocking the vault.
- Decide whether the original should remain in Photos.
- Check iCloud Photos, Recently Deleted, shared albums, messages, and other devices before assuming a second copy is gone.
- Confirm your recovery plan before deleting anything irreplaceable.
Important limits
Neither option proves physical erasure from flash storage. Neither protects content already exported elsewhere. Neither defeats spyware, an untrusted keyboard or accessibility service, a camera pointed at the screen, or coercion to unlock the device.
For a complete workflow, continue with how to hide private photos safely and who can see your encrypted photos.
Primary platform reference
Apple documents current Hidden Album behavior in Hide photos on your iPhone, iPad, Mac, or Apple Vision Pro.
Guide reviewed: 12 September 2026.