The Hidden album offers built-in concealment and authentication while keeping photos in your Photos library. A separate vault may add its own credential, storage and organization, but its encryption and recovery depend on the specific app. PhotoVault: Encrypt & Compress adds encrypted local archives; the app is not yet a verified replacement for your originals.

Start with the problem you want to solve

If you only want a few pictures out of the normal Photos grid, the built-in Hidden album may already meet your needs. If you want a separate archive and a different way to organize or compress media, consider an additional app.

If your concern is forensic access to a stolen device or someone who can copy app files, evaluate the actual encryption design. A polished lock screen cannot answer that question.

The built-in option

Hidden is locked by default on iOS 16 and later. It removes selected items from ordinary library views, albums and the Photos widget, without moving them out of the Photos library. With iCloud Photos enabled, their hidden status follows them across your devices.

Hiding is not an instruction to stop syncing or to create a separate backup. Review your Photos and Apple Account settings before assuming an image exists only on one phone.

Hidden does not mean unencrypted iCloud storage

Apple encrypts iCloud Photos in transit and on its servers under standard protection. Advanced Data Protection, where available and enabled, extends end-to-end encryption to Photos. Some metadata and sharing exceptions remain; for example, Shared Albums do not receive that protection.

Advanced Data Protection disables iCloud web data access by default. If you enable web access, trusted-device approval can provide temporary access to the relevant keys. A comparison that treats every hidden photo as freely readable from a browser misses these account settings.

A vault’s local gallery, its own cloud service and iCloud device backups are separate storage paths. Keeping an imported copy outside iCloud Photos does not by itself prove that it never enters any backup.

What the current Photo Vault source adds

The reviewed source includes password, pattern and device-authentication options, a separate local gallery, collections and export controls. Device authentication permits the phone passcode as fallback. The gallery password and pattern are separate credentials, but they do not derive the archive encryption key.

New archives use AES-GCM protection with a random installation key held in the device’s Keychain; existing archives must migrate successfully. This replaces the earlier storage design. The key is device-bound, and copying archive files alone is not a verified way to restore them on another phone.

PhotoVault: Encrypt & Compress 1.0 runs on iPhone and iPad (iOS/iPadOS 26+) with AES-256-GCM local archive encryption and Secure Share (.pvsecure) export; always verify exported backups independently. New Photo Vault Lossy imports store compressed media with separate encrypted metadata, without whole source files. Still-image exports reconstruct JPEG or PNG files; existing retained originals remain exportable. ZIP archives and sharing remain in development; keep important originals outside this build.

A practical decision checklist

  • Need selected images out of everyday browsing? The built-in Hidden album may be sufficient.
  • Need access independent of the phone passcode? Check every unlock and recovery option, including biometric fallback.
  • Need original-file preservation? Verify the exact imported resource against its exported bytes; a preview alone cannot establish fidelity.
  • Need access after losing or replacing the phone? Require a documented, tested recovery path and the credentials or keys it needs.
  • Need unchanged files for printing or editing? Retain independent originals; a smaller archive is not proof of equivalent quality.

Sources & further reading

Keep exploring