Skip to content
Skip to content

The transfer manager

Start it, walk away.
It picks up again

One panel tracks every transfer: live progress, pause and resume without re-encrypting, retries, and bulk ZIP downloads.

Transfers2 active · 1 paused
q4-research.tar.zst
Encrypting · chunk 18/24
design-system.fig
Paused · 41% complete
photos-2026.zip
Downloading · decrypting
tax-documents.zip
Done

Built for big files and flaky networks

Because everything is encrypted on your device first, transfers have to be resilient. So they are.

  • Live progress & ETA

    Watch every transfer move in real time: per-file percentage, current stage, and a running estimate of time remaining.

  • Pause without losing work

    Pause an upload at a chunk boundary and walk away. The session stays intact, so nothing already encrypted is thrown out.

  • Resume where it left off

    Resuming reuses the same encryption key and skips chunks the server already has. No re-encrypting, no starting over.

  • Retry on failure

    A dropped connection doesn't mean a restart. Retry picks the transfer back up from the last confirmed chunk.

  • Bulk ZIP downloads

    Select many files and download them as a single ZIP: each one decrypted in your browser and packed locally.

  • Survives navigation

    The manager is docked once and persists as you move around the app. Browse, open files, and start more work while transfers run.

Resume that actually resumes

No re-encrypting. No re-uploading.

When you pause or hit a network hiccup, the upload stops at a clean chunk boundary and holds onto its session. Resuming reuses the very same content key, so the chunks already on the server still line up: it simply continues with the chunks that are missing.

  • Pauses at a chunk boundary, keeps the session alive
  • Resumes with the same key, already-encrypted chunks stay valid
  • Skips chunks the server already confirmed
  • Retry after a failure continues from the last confirmed chunk
How uploading works
// resuming a paused 24-chunk upload
session reused, same content key
chunk[0..17] already on server → skipped
chunk[18] encrypt → upload ✓
chunk[19] encrypt → upload ✓
…
chunk[23] encrypt → upload ✓
✓ complete, 18 chunks never re-sent

Also: device-to-device

Send a file straight to another device

Separate from the vault, zcrypt can stream a file from one device to another through a relay that stores nothing. The sender gets a six-digit code and a pairing key; the receiver needs both. The data is end-to-end encrypted with that key, so the relay only passes along ciphertext it can't read.

  • Pair with a 6-digit code
  • End-to-end encrypted, the relay only sees ciphertext
  • Nothing has to land in your vault first
Pairing code
482107
Waiting for peer…

Get started today

Move big files without babysitting them

Free and open source. Bring a storage account you already own and start your first upload in under a minute.