See Photo Vault

Android guide

How to back up a photo vault

Updated 2026-11-19 · 7 min read

A vault solves confidentiality. It does not solve availability. Confusing them is how people lose photos that were "protected" the whole time.

Encryption makes a copy unreadable to everyone without the key. It does nothing about the phone falling in a lake, the app being uninstalled by mistake, or a folder being deleted to free up space. A vault is one copy on one device by default. That is not a backup.

What a backup has to survive

What happensDoes the vault survive it?What actually saves you
Phone lost or stolenNoA copy that was already off the phone
Phone dies, gets wet, or will not bootNoA copy that was already off the phone
App uninstalledOnly if the vault lives in a folder you ownReinstall, point at the folder, enter the recovery code
Folder deleted by mistakeNoA second copy, plus the version history of wherever it lives
PIN forgottenYes, if the code is safeThe 26-character recovery code, stored outside the phone
Recovery code lostNoNothing. The copies become noise

The first four rows are availability problems, and availability comes from copies, not cryptography.

3-2-1, translated for a phone vault

The rule is three copies, two kinds of storage, one off-site. On a phone:

A fourth rule is specific to encryption: the recovery code needs two copies, in two places, outside the phone. Three copies of ciphertext and no code is zero usable backups. Keep the code away from the drives: a stolen bag should not hold both the lock and the key.

The three export formats

Photo Vault exports in three ways, and they answer different questions.

FormatWhat you getReadable without the appRebuilds the vaultUse it for
OriginalsNormal photo, video and document files in a folder you chooseYes, any viewerNoMoving to another app, printing, editing, a readable archive
.kvenc exportEncrypted files, one per item or one bundle; each has its own key wrapped by your recovery codeNo, but the offline decryptor and the command-line tool can open itNo — items onlyA selective encrypted copy of the files that matter
Full encrypted backupOne archive of the whole vault folder, with its manifest, blobs, metadata and thumbnailsNoYes, on a new phoneMonthly snapshots and phone migration

Originals are the honest option when the point is to get files out. The app reads every file back and verifies it after writing; the report tells you which passed. A readable copy has none of the vault's protection, so put it on an encrypted disk or delete it after import.

<code>.kvenc</code> files are self-contained encrypted exports. Each has its own random file key, wrapped by a key derived from your recovery code, so one file can go to a laptop without exposing the rest. They are the right choice for "copy the ID scans and the will, not the whole library". They do not rebuild a vault, and what a .kvenc file actually is covers opening one years later.

The full encrypted backup restores a vault. It contains the structure the app reads on a phone, so it is the format for a monthly snapshot and the only one that gets you back to a working vault after a lost phone. Restore it into a clean folder and enter the recovery code.

In practice: full backup monthly, <code>.kvenc</code> for the few files you cannot lose, originals when leaving the app.

Test the restore before you need it

An untested backup is a hope. There are two levels of testing.

The full test is a restore onto a phone that has no vault. An old Android phone is enough: install the app, choose the backup archive in the restore flow, enter the code, open a few files. Do this once a year.

The cheap test catches most failures. Take one <code>.kvenc</code> to a computer, open it in the offline decryptor with the code typed from the paper copy — not copied from the phone — and confirm the file opens. That proves the file survived the copy, the code is correct, and the backup is readable without the phone that made it.

Store card reading 'Encrypted as it is written': files land in a folder you own, encrypted on the way in rather than on a server.
Encryption happens on the way in. That is why a copied folder is safe to store anywhere, and why the key has to be stored somewhere else.

Keep the code outside the phone

The recovery code is 26 characters, shown once when the vault is created, and it can be printed as a recovery card.

Losing the code makes every encrypted backup useless. The files stay on disk, complete, and nobody can open them — not you, and not us. There is no reset and no support path that recreates the key. Treat the paper copy as part of the backup, because it is.

A schedule that survives real life

A backup routine fails when it demands too much. This one is small:

Keep the last three monthly archives rather than overwriting one; a corrupted file can sit unnoticed for a month.

Where the copies go

A computer. Put the archive in a normal folder, not Downloads, where it gets cleaned up.

An external drive. Label it with the date, keep it disconnected, and store it away from the phone's usual bag. Ransomware and theft go after whatever is plugged in.

A folder your sync client watches. Only ciphertext leaves the device, which is acceptable here. Copy the archive into the folder; do not point the sync client at the live vault folder. Sync is a mirror: delete a file on the phone and the mirror follows.

The backup checklist

FAQ

Is a photo vault the same as a backup?

No. A vault protects files from being read; a backup protects them from being lost. Photo Vault keeps one folder on one phone and has no cloud service, so the second and third copies are your job.

How often should I back up a vault?

Monthly for the full archive, plus before any OS upgrade, trip, factory reset or big import. The post-import one matters most: those files have no older copy anywhere.

Can I store the encrypted backup in Google Drive or OneDrive?

Yes. The archive is ciphertext, so a sync folder only receives data it cannot read. Two cautions: keep the recovery code out of that account, and do not point the sync client at the live vault folder, because a sync mirrors deletions. This is your storage, not ours.

What is the difference between a .kvenc export and the full backup?

A <code>.kvenc</code> export contains selected items, encrypted, and opens without the vault. The full backup contains the whole vault and restores a working vault on a new phone. For moving phones, use the full backup; see how to move a vault to a new phone.

What happens if I lose the recovery code?

The encrypted copies become unreadable. The files are still there, but no PIN, reinstall or support request can open them. Recovery options explains what is possible, and the honest answer is that the code is the backup's other half.