blixtNo “file too large”
Free is capped at 500 MB per file; every paid plan is uncapped per file. A 400 GB project file is just another transfer on a paid plan.
Honest comparison
Blixt vs WeTransfer
WeTransfer made “send a file” as easy as sending a link: the receiver needs nothing installed, and the brand is recognized in every inbox. For small one-off sends to strangers, that is hard to beat. Here is what changes when the files get big.
Side by side
The short version, in one table.
| WeTransfer | Blixt | |
|---|---|---|
| Direct transfer, no middleman cloud | No — files are uploaded to WeTransfer’s servers | Yes — machine to machine |
| Trips your data makes | Two: up to their cloud, then down to the receiver | One |
| Max file size | 2 GB free; higher caps on Pro (~$12/mo) | 500 MB per file on Free; uncapped per file on every paid plan (from $5/mo) |
| Resume after a connection drop | No — an interrupted transfer starts over | Yes — only missing verified chunks are re-sent |
| Verifiable end-to-end security | TLS in transit; you trust their servers with the file | TLS 1.3 + certificate pinning + a 6-digit SAS compared out of band + BLAKE3 |
| Copy left on a third-party server | Yes — the download link keeps working after you hit send | No — a direct transfer never rests anywhere in between |
| Works offline / on a LAN | No | Yes — LAN mode, no internet, no server |
| Install required | None — a browser is enough | Both ends for direct transfers; bCloud share links receive in a browser |
| Price | Free (2 GB) / Pro ~$12/mo | $0–$50/mo flat — direct traffic is never metered |
Fair is fair
Where WeTransfer is the better choice.
Genuinely better with WeTransfer:
- Your receiver installs nothing, ever. A WeTransfer link works for anyone with a browser. (A bCloud share link does too — but a direct Blixt transfer needs the app on both ends.)
- The brand is everywhere. An inbox trusts a WeTransfer link; a tool your client has never heard of can raise a question you don’t want to answer at 6 pm on delivery day.
- For a one-off send of a few hundred megabytes to a stranger, the free tier is frictionless — and if time doesn’t matter, entirely adequate.
Our case
Where Blixt wins.
No copy left behind
The file goes from your disk to theirs — not up to a server and down again. And no download link keeps living somewhere after you’re done.
Drops don’t reset you
A dropped connection resumes from a MAC-protected block journal. Only the missing verified chunks are re-sent.
Proof, not promises
TLS 1.3 with fail-closed certificate pinning, a 6-digit code both sides compare out loud, BLAKE3 on every chunk. You can check — not just trust.