How to send a file without uploading it anywhere

Almost every way you send a file works the same way underneath: the file goes up to a server first, sits there, and then comes back down when the other person clicks. That round trip is where the friction lives. You wait for the upload, the service caps how big the file can be, it keeps a copy on someone else's computer, and half the time one of you needs an account. For a lot of files, none of that is necessary. You can send it directly instead.

What "without uploading" actually means

A peer-to-peer transfer moves the file straight from your browser to the other person's browser over an encrypted channel (the same WebRTC technology that carries video calls). The bytes go device to device. A small server is involved for exactly one thing: helping the two browsers find each other with a short code, and then it steps out of the way. The file itself never lands on it. There is nothing to upload, so there is nothing to store, nothing to expire, and no size limit to hit.

That last point surprises people: a 40 GB video moves the same way a photo does, because there is no upload step to cap. The only real ceiling is how long you both leave the page open.

How to do it with Direct Send

Link in Seconds has this built in as Direct Send, at /transfer. It sits beside the normal upload flow rather than replacing it, because the two solve different problems. Here is the whole thing:

1. Open Direct Send and drop in the file you want to send. Nothing uploads, so the file stays on your device.
2. Share the link or QR code you get back. Paste the link into a chat or email, or let the person scan the QR from across the room.
3. They open it in their browser. As soon as both pages are open, the two devices connect.
4. The file transfers directly, device to device. On the same Wi-Fi it moves at local-network speed, because that is literally the path it takes.

No account for either side, no install, no waiting for an upload bar to fill before you can even share the link.

When it's the right tool, and when it isn't

Direct Send trades permanence for privacy and size, and that trade is real. Because nothing is stored, the file exists only while you are both connected. That makes it perfect for some things and wrong for others.

Reach for Direct Send when

• You're both at your devices right now, on a call, at a desk, or in a meeting.
• The file is too big for email or a normal upload cap.
• You'd rather the file never sat on anyone's server, including ours.
• You're moving something between your own phone and laptop.

Use a normal hosted link when

• The receiver isn't online right now, or you don't know when they'll open it.
• You want the file to still be there next week, or to send it to a whole group.
• You need view tracking, a password, or a QR that keeps working after you've closed the tab.

For any of those, upload it and get a permanent hosted link instead, a clean lisview.com/… address that holds the file for whoever opens it later, which is exactly what Direct Send deliberately does not do. There's a fuller walk-through in share files online, and if the file is headed to an inbox, send large files via email covers that path.

One honest catch: a direct connection needs both browsers open at the same time, and a few networks (strict office firewalls, some VPNs) block direct connections entirely. When that happens, Direct Send tells you rather than spinning, and a normal upload link works everywhere.

Is it actually private?

Mostly, and it is worth being precise about how. The file travels directly between the two browsers and is never stored on our servers. Every piece of it is encrypted in your browser with AES-GCM, on top of the encryption WebRTC already uses, and decrypted in theirs. The encryption key is derived from the short transfer code, and our server does see that code, because it is how the two browsers find each other. So this is not end-to-end encryption in the strict sense: the protection comes from the file never touching our storage, from the code only working while your tab is open, and from the transfer expiring after 30 minutes.

The practical caveat is that whoever holds the link can receive the file, so treat it like any other share link and send it over a channel you trust. If you need tighter control over what a recipient can do, a hosted view-only file share lets people see a file without being able to download it.

The short version

• Uploading first is optional, since a peer-to-peer transfer skips it entirely.
• The file goes browser to browser, so there's no size cap and no server copy.
• Both people have to be online at once, and nothing persists afterward.
• When you need it to last, upload it and share a normal hosted link instead.