Rename a File Inside a Vault with vault mv
vault mv renames a stored file, or moves it to another folder, without re-encrypting the contents. This guide covers both uses and the two ways it can refuse.
The route
Jump straight to the step you need, or tick off Done means at the end.
Allow about five minutes. You need a key and a stored file. It changes the vault, so it takes an exclusive lock briefly.
1. Rename in place
$ vault mv work/2026/report.pdf work/2026/q3-report.pdf
$ vault rename work/2026/report.pdf work/2026/q3-report.pdfrename is an alias. Arguments are the old name then the new one.
2. Move to another folder
$ vault mv work/2026/q3-report.pdf archive/q3-report.pdfThe new name may sit in a different folder. File contents are not re-encrypted, so it is quick whatever the size.
3. Know when it fails
Safety boundary
It fails if the new name already exists, or is not a valid vault path. Nothing changes on failure. Use vault list to look for a clash first.
4. Confirm
$ vault list archiveRelated: vault-rm(1) to delete, vault(1) for shared options.
Done means
- The old name is gone and the new one shows in
vault list. - No existing file was clobbered, because
mvrefuses to. - The right passphrase was used, since a decoy identity renames only its own files.