Secure File Transfer Between Devices

Security for a file transfer comes down to two questions: is the connection encrypted, and who else can see the file along the way. Nearsend answers both directly, WebRTC’s built-in DTLS encryption, and a direct device-to-device path with no server storage in between.

The usual problem

Email attachments and many "quick share" links travel over plain HTTP uploads to a server, then sit there until someone downloads them, a window where a copy of a potentially sensitive file exists somewhere outside your control, protected only by whatever that service’s own security happens to be.

How Nearsend solves it

Nearsend transfers files over WebRTC data channels, which are encrypted end-to-end between the two connected devices using DTLS as part of the protocol itself, not an add-on. Files stream directly from sender to receiver. Nearsend’s server only relays the initial connection setup (signaling), never the file contents, so there’s nothing sitting on a server for anyone else to reach.

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 WebRTC data channels, with file contents never routed through server storage

Frequently Asked Questions

How is the transfer encrypted?

Nearsend uses WebRTC data channels, which are encrypted with DTLS as part of the protocol, the same technology behind secure video calls.

Does the file pass through Nearsend’s servers?

No, the server only helps the two devices establish a direct connection (signaling). The file itself streams device to device.

Do I need an account to send securely?

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

Is this safe to use on a public or shared computer?

Nearsend leaves nothing behind on the device after the tab is closed, since there’s no install and nothing saved to an account.

Is it safe for sensitive documents?

The connection is encrypted and the file is never stored on a server, which are the two main things to check for any file-sharing tool.

How does this compare to a password-protected zip file sent by email?

A password-protected zip still travels through email's own infrastructure and sits in both inboxes afterward. A direct transfer skips that entirely, the file never becomes an email attachment or an inbox record in the first place.

Does "secure" here mean the same thing as "encrypted"?

Encryption is the core of it, but security here also includes the fact that no third-party server stores a copy; both the transit and the absence of storage matter to the overall claim.

Does encryption slow the transfer down noticeably?

No, DTLS encryption is a standard, lightweight part of the WebRTC protocol, not an optional add-on, so it doesn't add meaningful overhead compared to sending the data unencrypted.