New Photo Vault Lossy imports use compressed image samples, so reconstructed JPEG or PNG exports are not byte-exact originals. Existing archives with retained source files still export those resources. For exact preservation, keep the original independently and compare the complete exported resource with it; visually similar output is a different requirement.
Define what you need to preserve
“No quality loss” can mean three different things. Decide which one matters before comparing apps.
| Requirement | Meaning | Useful check |
|---|---|---|
| Identical original file | Exactly the same bytes, including embedded metadata. | Compare the original and exported file byte for byte or with a cryptographic file hash. |
| Identical decoded pixels | The image samples remain unchanged, although the file container or metadata may differ. | Compare decoded images using the same orientation and color interpretation. |
| Acceptable appearance | Changes are acceptable at your intended viewing or print size. | Inspect detailed areas, shadows, gradients and video motion at the size you will use. |
Build a small round-trip trial
Keep untouched originals outside the vault. Use disposable copies representing your library: a detailed still, an edited image and a video with sound. Add a Live Photo or another special format only if preserving that format matters to you.
Record the app version, import setting and export option. Import the copies, close and reopen the app, then export to a separate folder. Do not overwrite the source while testing.
Compare what came back
Check file count and format first. Then compare dimensions, video duration and audio. Inspect capture dates, location and any other metadata you need; a correct-looking thumbnail cannot establish that these survived.
An identical file hash is strong evidence that this particular exported file matches the original bytes. A different hash establishes that the files differ, but does not by itself tell you whether the change is visible, metadata-only or harmful. Use the more specific checks above to understand it.
For paired or multi-part media, check the whole item. One exported still is not proof that motion, sound or editability survived. A successful sample also does not prove every item in a large library will export correctly.
Test backup separately from export
Export and recovery answer different questions. After a successful export trial, test the app’s documented recovery route with disposable copies while keeping the original device and files. Verify the restored items again.
Record any paid-plan requirements and limits. Do not erase the only working copy to discover whether a restore or subscription-dependent export works.
Where Photo Vault fits
New Lossy HEVC imports no longer embed whole original image or movie files alongside the encoded media. Pictures are reconstructed for export; needed movie, audio and Live Photo tracks remain in the archive. Existing retained source resources survive append and deletion compaction and continue to use the original-resource export path.
Tests covered JPEG and PNG reconstruction, all eight EXIF orientations, dates, GPS including altitude, camera information, IPTC and custom XMP. Captured public metadata is retained independently in the encrypted index; what can be embedded in an exported file depends on ImageIO and its format. These checks do not establish exact RAW sensor, animation or original HDR/depth preservation.
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. The reported tests include reconstructed Live Photo pairing accepted by PhotoKit and unchanged video/audio samples across append and compaction. They do not prove every Photos edit or private library attribute survives, and no Photos-library insertion was performed during this QA.
The intended physical iPad was unavailable for installation and launch. ZIP, sharing and portable recovery are not established by these tests. The device-bound key remains a recovery limitation: keep independent originals when exact preservation matters.