Can I download a file straight into the vault?
Yes — choose the vault as the destination when you start the download. It runs on the normal engine, so it continues in the background and resumes after an interruption, and the queue shows a masked row. The file is encrypted into the vault the first time you unlock it after the transfer finishes.
Reviewed 30 July 2026
A download that has to wait for you to unlock the vault would be a download that never runs in the background, so it does not wait. The transfer lands in a staging area that is outside the vault catalogue, and locking or unlocking the vault has no effect on it — the lock is a door in the interface, not a brake on the engine.
In the download queue the row is masked: a generic title and a vault icon, with the usual progress, pause and resume. When you next open the vault, whatever finished is encrypted and filed, and the staging area is emptied.
One limit worth stating
To be able to resume after a network drop or a reboot, the queue database has to keep the address it is downloading from. That address is not visible anywhere in the app, but it is on disk in the clear until the file is taken into the vault. Encrypting the queue row itself is on the list; until then, the honest description is that an in-flight download carries its origin with it.