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.

Peer-to-Peer vs Client-Server: How File Sharing Actually Moves Your Data

September 20, 2026

Most of the digital tools people use every day — email, cloud storage, social media — share the same basic shape, so much so that it's easy to stop noticing it's a choice at all. Peer-to-peer is the less common alternative, and it's worth understanding on its own terms rather than just as a buzzword.

Client-server: the shape most tools use

In a client-server setup, one place — a server — holds the data, and everyone else connects to that same central point to upload or download it. A photo posted to a social network, a document saved to cloud storage: one copy lives on a server, and any number of people can request it from there, whenever they want.

Peer-to-peer: no hub

A peer-to-peer connection removes that middle point entirely. Once two devices are connected, data flows directly between them — there's no third location holding a copy in between. It's less a broadcast from a central hub and more a direct line between two specific participants.

Where each shape genuinely wins

Client-server earns its place when many different people need access to the same file over time — a public dataset, a downloadable PDF linked from a website — because the server can just keep answering requests whenever they come in, asynchronously. Peer-to-peer earns its place in the opposite case: one sender, one specific recipient, right now.

The trade-off that actually matters

A stored copy on a server is convenient — it's why cloud links let someone download a file hours or days later. But a stored copy is also something that exists somewhere and has to be protected, for as long as it sits there. A direct peer-to-peer transfer leaves nothing behind once it ends, at the cost of both participants needing to be present and connected at the same time.

Why this shows up as a real design decision, not just an implementation detail

That stored-copy cost is exactly why so many client-server file-sharing services impose size limits and storage quotas — every byte held on a server is a byte someone has to pay to keep. A peer-to-peer transfer, with nothing left sitting on a server, doesn't carry that same cost structure, which is why it doesn't need the same kind of cap.