Restore encryption state
The wrapped file key and nonce are restored only after the workspace key is unlocked.
Recovery proof / Account uploads
Interrupt the upload.
Keep the finished parts.
VaultDrop uses multipart recovery for registered files at or above 100 MiB. This page states what the code-path test proves and gives you a repeatable live test.
- Automated check
- 16 July 2026
- Recovery window
- Up to 7 days
- Match rule
- Same unchanged local file
01 / What is verified
The production recovery path, exercised without a fake progress animation.
Reject a changed file
Name, plaintext size, modification time, and expected encrypted size must match the pending session.
Ask the server what finished
The browser requests the pending session status and receives confirmed part numbers.
Queue only missing parts
Confirmed parts are counted as complete. Only absent parts receive replacement upload requests.
Complete once
After every required part is present, the browser asks the service to assemble the encrypted object.
02 / Live runbook
Repeat it before a client deadline.
- 01
Choose a safe representative file
Use a non-sensitive file larger than 100 MiB. A 250 MiB to 1 GiB file makes the recovery behavior easier to observe without creating a costly test.
- 02
Record the checksum
On macOS or Linux, run
shasum -a 256 your-file. Keep the result for the final integrity check. - 03
Start from an unlocked workspace
Create or sign in to the free workspace, unlock browser encryption, add the file, and wait until at least one upload part is complete.
- 04
Create a real interruption
Reload the page, close the tab, or briefly disconnect the network. Do not rename, edit, move, or regenerate the local file.
- 05
Reconnect the same file
Return within seven days, unlock the workspace, and select the exact same local file. VaultDrop should identify the pending session.
- 06
Observe the recovered position
The upload should continue from server-confirmed parts. It may re-upload a part that had started but was not confirmed before the interruption.
- 07
Verify the recipient result
Complete the upload, share it with a controlled test recipient, download it, and compare the SHA-256 checksum to the original.
03 / Expected failures
Recovery should stop when identity is uncertain.
The file changed
A changed name, size, or modification time prevents safe automatic matching. Start a new upload.
The seven-day state expired
The local recovery record or underlying multipart session may no longer exist. Start a new upload.
Browser storage was cleared
The browser loses the wrapped recovery material. The service cannot recreate it from plaintext because it never received plaintext key material.
The workspace remains locked
The wrapped file key cannot be restored until the account encryption key is available in the browser session.
Use the free workspace