Nederlands
Why more people are choosing encrypted file sharing without tracking, without accounts, without ads.
| Feature | gooi.io | WeTransfer | Send | Wormhole |
|---|---|---|---|---|
| End-to-end encryption | Yes (AES-256) | No | Yes (AES-128) | Yes (AES-128) |
| Account required | No | Yes, required | No | No |
| Max file size | 5 GB | 3 GB | 10 GB | 10 GB |
| Ads | None | Yes, full-page | None | None |
| Tracking / analytics | None | Yes | None | Minimal |
| Retention (free) | 24 hours | 3 days | Configurable | 24 hours |
| CLI / agent support | Yes, native | No | Via ffsend | No |
| Multiple files | Yes (bundle) | Yes | Yes (zip) | Yes |
| Server location | Amsterdam, NL | US / EU | Varies | US |
| Server can see files | No, impossible | Yes | No | No |
| Price | Free | Free / paid | Free | Free |
WeTransfer is convenient, but your files aren't truly private. WeTransfer only encrypts files during transport (TLS) and can access them on their servers. With gooi.io, that's impossible: your browser encrypts the file with AES-256-GCM before anything is uploaded. The key is in the URL (after the # symbol) and is never sent to our server.
When you upload a file to gooi.io, your browser generates a random 256-bit key. The file is encrypted with AES-256-GCM before it's sent to the server. The key is included in the URL fragment (the part after #). Because browsers never send the fragment in HTTP requests, the key never reaches our server.
This is called zero-knowledge encryption: even if someone hacks our server, they only see encrypted data that is unreadable without the key.
gooi.io is ideal for anyone who wants to share a file quickly and securely. Whether you're sending a document to a colleague, sharing photos with family, or a developer sending files via a CLI script or bot. No registration, no hassle.