Scalable, zero-trust file transfer for serious work.

No. Files travel directly between computers over an encrypted channel. ZettaSend's servers facilitate the initial connection and may relay already-encrypted packets if a direct P2P path is blocked — but they never see, store, or process your file contents. No one except you and your recipient will ever see the contents of your files.

Yes — both machines need to be on for the duration of the transfer. But ZettaSend makes this painless: it automatically prevents your computer from sleeping while a transfer is active, so you can step away without worry. You can also limit the transfer speed to keep your network usable for other work, and if you need to close the app or shut down entirely, just resume from the exact same byte next time. No progress lost.

On the Team plan with audit logging enabled, the following metadata is recorded: who sent what, to whom, when, and from which IP address. File names and sizes are included in the audit manifest. File contents are never logged or transmitted to our servers. The audit trail is cryptographically signed by both parties and stored for 90 days.

Cloud storage — even zero-knowledge — still stores your (encrypted) files on their servers. You're trusting that their encryption is unbreakable and their infrastructure is secure. ZettaSend doesn't store your files at all. They travel directly between machines and are never written to any server. There's nothing to breach because there's nothing stored.

No. ZettaSend uses direct peer-to-peer connections, but every transfer is fully encrypted end-to-end with mTLS. Transfers require explicit acceptance from the recipient — no unsolicited files. The Team plan adds cryptographic audit trails signed by both parties. It is a managed tool, not an open peer network.

WeTransfer works fine for smaller files, but it requires you to upload your data to their servers first. Your files sit on their infrastructure until the recipient downloads them. There is a 200 GB cap, no pause/resume, and no audit trail. For routinely transferring large or sensitive files, the cloud round-trip is a trust and efficiency problem.

Browser-based solutions rely on browser memory and a persistent connection. They cannot pause and resume, struggle with files beyond a few gigabytes, and require uploading to a server. ZettaSend is a native desktop application that handles network interruptions gracefully and resumes from the exact byte — with no server in the middle.

Short network flickers — under a few minutes — are handled automatically. For longer outages, you can manually resume the transfer later. It picks up exactly where it left off, byte for byte.

No. ZettaSend is fully zero-config. It works out of the box on Windows, macOS, and Linux. No admin rights needed to install, no port forwarding required, no server to maintain.

Yes. Only paying users need to create sessions. Recipients can join for free — no account or subscription required. Once connected, both parties can freely send and receive files.

No. You can send any combination of files and folders without zipping. The folder structure is preserved on the recipient's end.

On the Team plan, every transfer is cryptographically signed by both parties using ECDSA P-256 and recorded in an immutable audit trail: who sent what, to whom, from which IP, and exactly when. Logs are retained for 90 days and are exportable as CSV. If anyone tampers with the records, the signatures become invalid.

Yes. Team plan administrators can set a custom logo and company name in workspace settings. This branding appears in session invite emails and within the transfer interface, giving external clients a consistent, professional experience.

ZettaSend is a native desktop application for Windows, macOS, and Linux. Installers use Velopack — no admin rights needed.

ZettaSend always attempts a direct P2P connection first. If that fails due to restrictive network environments like symmetric NAT, it falls back to our secure relay servers. The relay forwards already-encrypted packets — it never sees your file contents. A warning is shown when the relay is in use.