Do my files pass through or get saved on any server?

No. Nearsend is strictly a peer-to-peer (P2P) platform. The signaling server is only used to exchange temporary session tokens and WebRTC handshake coordinates. Once connected, your files, text, and clipboard stream directly between your devices via WebRTC DataChannels in 64KB encrypted chunks.

How does the Voice Pairing work securely?

When you generate a voice pairing phrase, the host device creates an ephemeral 3-minute token. When spoken on the guest device, browser speech recognition converts the acoustic phrase into the token. The server validates the match and immediately triggers an explicit confirmation prompt on the host device before any connection is allowed.

Does Nearsend work across different operating systems?

Yes! Nearsend works seamlessly across any modern web browser — Windows, macOS, Linux, Android, iOS, iPadOS, and ChromeOS. No native apps or software installations are required.

Is there a file size limit on Nearsend?

Because transfers stream directly via WebRTC without hitting a central server memory limit, you can send files ranging from kilobytes to multi-gigabyte videos. Nearsend incorporates backpressure flow control to ensure smooth transmission without exhausting device RAM.

A Quick Checklist Before You Send a Large File

October 4, 2026

Large transfers are exactly where small oversights turn into a wasted twenty minutes. A sixty-second check beforehand avoids most of it.

1. Confirm it's actually the file you mean to send

Obvious, but the single most common real mistake. A quick check of the filename — and a preview, if it's a document or image — is worth it, especially for anything with version numbers or similarly-named files nearby.

2. Check both devices' power and screen settings

A transfer that outlives your laptop's sleep timer or your phone's screen lock is asking for a stall. For a genuinely large file, turning off sleep and screen-lock on both ends for the duration is worth the extra step.

3. Pick a stable network over a fast-looking one

A strong Wi-Fi signal indicator isn't the same thing as a stable connection. Given a choice between flaky public Wi-Fi and a slower but steady mobile connection, steady wins for a large, uninterrupted transfer.

4. Decide files vs. one archive upfront

Sending a folder as individual files, rather than zipping it into one archive first, means a hiccup only costs you that one file's retry — not the whole batch starting over from zero.

5. Know roughly how big 'large' is for your connection

There's no universal size limit on a direct transfer, but the honest expectation-setter is your own upload and download speed — a file that feels instant on office fiber can be a real wait on mobile data, and that's normal, not a sign something's wrong.