Private File Sharing Between Devices

Most "free" file-sharing tools ask for an account, keep a copy of what you send, or both. Nearsend was built around the opposite default: no account, and nothing stored anywhere but the two devices involved.

The usual problem

Sharing a file usually means trusting a third party with a copy of it, an email attachment sitting in two inboxes, a cloud link that stays live indefinitely, or an account you had to create just to send one file. Even when a service says it deletes files "eventually," that’s still a window where a copy exists somewhere you don’t control.

How Nearsend solves it

Nearsend pairs two devices directly and streams the file over an encrypted WebRTC connection straight from sender to receiver. There’s no account tied to the transfer, no copy left on a server, and no shareable link that keeps working after the fact, once the transfer ends, there’s nothing left behind to manage or revoke.

How to do it

Open Nearsend on both devices, Go to nearsend.app in any modern browser on the sending and receiving device; no app to install.
Pair them, Scan the animated QR code, enter the 6-digit PIN, or say the voice phrase to connect the two devices directly.
Send your files or folder, Drop files or a full folder onto the page, or pick them from the file browser. They stream straight to the other device.

Why it works well here

No app to install, runs in the browser on both devices
No account or sign-up required
Works across Windows, macOS, Linux, Android, iOS, ChromeOS, and HarmonyOS
Files stream directly device-to-device; nothing is stored on a server
DTLS-encrypted connection with no copy retained on any server after the transfer

Frequently Asked Questions

Does Nearsend keep a copy of what I send?

No. Files stream directly between the two devices and are not stored on a server.

Do I need to create an account to share privately?

No; no account, email, or phone number is required.

Is the connection encrypted?

Yes, transfers use WebRTC data channels, which are encrypted with DTLS by design.

Can someone else access the file later through a link?

No shareable link is created, the file only goes to the specific device you paired with during the transfer.

Who can see what I’m sending?

Only the two paired devices. Nearsend’s server helps them connect but doesn’t see the file contents.

Does private mean anonymous?

Not quite the same claim, basic network metadata like an IP address is still visible to the signaling infrastructure that helps two devices connect, the same as for any website. "Private" here specifically means no account, no stored copy, and no persistent history.

Is this a good fit for sharing something with someone I don't know well?

Yes, in the sense that no persistent account or profile ties the exchange to either of you afterward, though basic caution about who you're actually pairing with still matters, the same as with any file exchange.

What makes this more private than a typical cloud-share link?

A cloud-share link creates a stored copy that keeps existing, and often keeps working, after the moment you intended it for, a direct transfer leaves nothing behind once it completes.

Is there a log I can check afterward to confirm what was sent?

Nearsend doesn't keep one, that's the same trade-off as not storing the file: nothing persists to check later, on either the sending or receiving side.