FAQ

After one download, the file is destroyed and the link becomes useless. If recipient verification is enabled, the correct one-time code is required before download; repeated wrong attempts destroy the file.

No. One VitalSend, one download. Use a sharing service for multi-recipient distribution.

Repeated wrong code attempts destroy the file. After the single successful download, forwarded links cannot be used again.

Not necessarily. VitalSend can deliver access to the recipient on your behalf, without revealing the sender.

Sender identification is optional. Features that create traces (such as receipts or payment details) are clearly marked.

No. Files are destroyed after delivery or retention timeout. No history persists.

Yes. VitalSend currently supports transfers up to 200 GB. Support for transfers up to 1 TB is in active development.

Large transfers support resumable upload and download. If a transfer is interrupted, it can be resumed without starting over.

You can start an upload in one location and resume it later from another network, on the same device.

VitalSend provides sufficient backend capacity for large transfers. In practice, transfer speed is determined by the sending and receiving environments.

For very large files, the limiting factors are typically the sender’s CPU and memory (due to client-side encryption), as well as available network bandwidth. The same applies on the receiving side during decryption, though decryption is usually less resource-intensive.

VitalSend is designed for correctness and finality rather than raw throughput.