No upload. No cloud storage. No account needed to receive a link.
Here's what happens when you send a file.
Your file never waits on a server. It streams as soon as the other side connects.
Any size. It's read off disk in small chunks, so memory use stays flat from 4 MB to 400 GB.
A one-time link, one of your own machines, or a Peeza on the same network.
Direct when the network allows it. Otherwise through a blind relay. Encrypted all the way.
If a transfer can't go direct, our server forwards encrypted data it has no key for. One exception: when you ask for it. You trust our servers in two places: the web page that decrypts in a browser and a new device's first key.
WeTransfer, SwissTransfer and Dropbox upload your file to a server, keep it, then send it down. Peeza skips the server.
Everyone else
Peeza
One hop. They receive while you send. No upload wait, no size cap, no copy left on someone else's hard drive.
| Peeza | WeTransfer (free) |
SwissTransfer | Dropbox (Basic) |
|
|---|---|---|---|---|
| Max per transfer | PeezaNo limit | WeTransfer3 GB | SwissTransfer50 GB | DropboxCapped by 2 GB of storage |
| Monthly cap | PeezaNone on direct transfers | WeTransfer10 transfers, or 3 GB total, per 30 days | SwissTransferNone published | Dropbox— |
| Where your file sits | PeezaNowhere. It streams device to device. | WeTransferTheir servers, ~3 days | SwissTransferTheir servers, up to 30 days | DropboxTheir servers, indefinitely |
| Can they read your files? | PeezaNo. The key never reaches us (one exception) | WeTransferYes. They hold the keys. | SwissTransferYes. Encrypted at rest, but they hold the keys. | DropboxYes. Their terms allow scanning your files. |
| They start receiving | PeezaAs you send. No upload to wait for. | WeTransferAfter your upload finishes | SwissTransferAfter your upload finishes | DropboxAfter your upload finishes |
| Link expiry | PeezaOne-time. Gone once used, or after 48 hours. | WeTransfer3 days | SwissTransferUp to 30 days | DropboxUntil you delete it |
| Send to your own machines | PeezaYes. Queued if they're offline. | WeTransferNo | SwissTransferNo | DropboxSync only |
No direct path? Strict NATs and corporate firewalls can block one. Then a blind relay forwards the encrypted bytes and stores nothing. Direct transfers are never metered. Relayed traffic has a free monthly allowance with an account.
Terms change. In July 2025, WeTransfer briefly gave itself machine-learning rights over uploaded files. Two weeks of backlash reversed it. We can't read your files (within these limits), so there's nothing to grant.
Figures checked July 2026 against each vendor's published plans: WeTransfer, SwissTransfer, Dropbox. Out of date? Tell us and we'll fix it.
Yes. Files go device to device, end-to-end encrypted, and are never stored in the cloud. We can't read them, with one exception, when you ask for it. You trust our servers in two places: the web page that decrypts in a browser and a new device's first key. We do see metadata: IP addresses, sizes and timing. For a connected account, also file names in your dashboard and teams (what the relay sees). IP addresses stay in memory, never on disk, never logged. We use them to connect devices, to rate-limit, and for up to 15 minutes when you connect a new device. Details: privacy policy.
End-to-end, always. Each share gets its own AES-256-GCM key, made on your machine. It travels in the link, or sealed to the receiving device. We don't receive it (one exception, when you ask for it). If a transfer can't go peer-to-peer, our relay forwards encrypted bytes it has no key for. Details on the tech page.
No. Files stream off disk in small chunks. A photo and a video project of several hundred gigabytes work the same.
For links, yes. The file goes straight from your machine to theirs, so both must be running. Sends to your own machines are queued and delivered when the target is back online.
For a link that stays up for a month: SwissTransfer. For a synced folder: Dropbox, or Resilio to stay peer-to-peer. Peeza gets a file to a person: fast, whole, no copy left behind.
Free, no account needed. Direct transfers are never metered. Relayed traffic has a free monthly allowance with an account. Numbers on the relay page.
Sending a file needs no account. An account unlocks what needs to know who you are: sending to your own machines, the web remote control, and the free monthly relay allowance. We're not after your data. There's no Peeza password: you connect with Google, Microsoft, Apple or GitHub. We keep your email address and the devices you connect. If you use teams, also the teams and the names of files shared there (full list). Connected or not, your files stay end-to-end encrypted (within these limits).
Yes, and it sends between them in any direction. iPhone, iPad and Android are on the way.
AirDrop only works between Apple devices in the same room. Peeza works across Mac, Windows and Linux, over the internet or on your own network. On the same network it transfers directly, with no internet or account needed.
Me and a few friends, mostly me. I'm Eric, a recording and mixing engineer in Montreal, after three decades leading complex, secure software for enterprises. Peeza is four years of hard work and prototyping, sped up lately by advances in tech. Every way I had to send a session was miserable, so I built the one I wanted. And more :)
Free, no account needed — Mac, Windows and Linux. iPhone and Android in public beta.