Use these procedures as task-oriented reference. They describe public capabilities and verification steps, not private implementation. UI labels can vary by version.
Keep a separate backup and choose a small varied photo batch.
Include detailed photos and a screenshot with small text.
Create and reopen the verified archive.
Export sample frames and compare detail, orientation and visible information.
If byte-exact files are required, test originals-package restoration separately.
Count archive, retained package and remaining Photos originals before interpreting savings.
You know which output is lossy, which originals remain restorable and how storage is used.
A decoded frame is not byte-exact. The current site says uninstalling removes the local originals package; do not rely on the archive video alone for exact restoration.
Identify whether an image representation or the exact original file is required.
Open the valid archive and choose a small sample.
Use frame export for reconstructed images.
Use the documented originals restoration only when the local package exists.
Check filenames, dates and special media properties that matter to your use case.
Preserve the archive and verified backup before larger changes.
The restored output matches the kind of preservation you need.
Photos/iCloud synchronization and local package storage are different. Do not transfer assumptions from another PhotoVault product.
Record app/version, device/OS, selected mode, input conditions and the smallest failing step. Distinguish expected behavior from the observed result. Use synthetic examples and omit credentials or private records.
Documentation index · Capabilities and limits · Support and sources