Why this is not another transfer service

Four things this does that a link-and-a-bucket cannot, and an honest table of how it stands against the usual answers. The numbers about other services come from their own pages, on the date given, with the links to check them.

1. Send it once, to everyone

The people receiving a file trade the pieces between themselves rather than each pulling the whole thing from you. Your upload is the bottleneck in every transfer you have ever done; this is the part that removes it.

Measured on the development machine: 20 GB sent to two people uploaded 20 GB once and delivered 40 GB. With five people the gap is wider still, and it grows with every person you add.

Nobody has to trust anybody for this to be safe. Every 4 MB block carries a SHA-256 from the original sender, so a piece that came from another receiver is checked against the sender’s own hash before it is written. A peer that sends a bad block is caught on the first one and stops being asked.

2. Nothing is stored anywhere

There is no bucket, no database and no expiry date, because there is nowhere for a file to sit. The server hands two browsers enough information to find each other and never sees a byte of what they then send.

That is also why we set no size limit — in Chrome and Edge a file goes straight to disk however big it is, and other browsers hold up to 512 MB in memory — and why there is no download link. A link to a file would mean a file sitting somewhere, and there is not one. It is why both people have to be there at the same time, too — the honest cost of the same decision.

The one thing the application writes to your disk is a resume note, if you ask for one: the file name and which parts have arrived, so a 20 GB download survives a closed tab. Leaving the room deletes it. The server, for its part, keeps one line of numbers per day for its status page — how busy it was, never who made it busy.

3. Checked before it is sent, and again when it lands

Every file is examined before it leaves: the real file type as opposed to the extension, the name, code embedded in documents, what is inside archives, and whether it is signed. You see that report and decide whether to send — for every file, not only the alarming ones.

The person receiving sees the verdict before accepting, not after. The report travels with the offer, along with the first four kilobytes, and their browser reads those four kilobytes itself — so a sender who says "holiday photo.jpg" about a Windows executable is caught by the receiver’s own reading rather than by their good faith.

This is triage, not an antivirus. There is no malware database here and nothing is ever run. The best score it can give is 95 out of 95, and that ceiling is deliberate: no check of this kind can tell you a file is safe.

4. One button erases it everywhere

Burn disconnects the room, wipes what is in memory on every machine in it, kills the code so it cannot be rejoined, and deletes the offline copy of the application from the other browsers too.

What somebody has already saved to their own disk stays on their disk — nothing can reach into another computer and take a file back, and any product that claims otherwise is lying to you. Everything else goes.

5. Against the usual answers

Free plans, read from each service’s own pages on 2026-09-22. Anything that could not be verified from a primary source was left out rather than guessed at.

Sources: WeTransfer · Wormhole · PairDrop.

The row that matters most is the second one. Everything else follows from it: no server holding the file is why we set no size limit, no expiry and no link — and why both of you have to be there at once.

Last reviewed: 2026-09-27

About · FAQ · Terms · Privacy · Accessibility · Cookies · What’s new

Obleevo is developed by The House of Brendrof. Proprietary software, free to use.

Back to Obleevo