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.

Why QR Codes Became the Default Way to Pair Devices

October 18, 2026

QR codes have quietly become the default pairing method for a huge range of tools — not just file transfer, but payments, event check-ins, Wi-Fi sharing, two-factor login. It's worth asking why this particular format, specifically, is the one that won out over the alternatives.

The actual problem a QR code solves

Pairing two devices needs one of them to communicate a piece of information — a token, an address, a shared secret — to the other, quickly, without either person typing anything manually. A QR code is a way of encoding a meaningful amount of data into a pattern a camera can read correctly in a fraction of a second, from across a table.

A brief detour: what a QR code actually encodes

Underneath the pattern of squares, a QR code is just a compact, error-corrected way of storing text or a short string of data — in this case, typically a token or session identifier, not anything sensitive on its own. The error correction built into the format is also why a QR code can still scan correctly even partially obscured or slightly damaged; a meaningful chunk of the pattern can be missing and the data still reads correctly.

Why not just show the raw code as text

A pairing token is normally a long, effectively random string, specifically designed to be hard to guess. Asking someone to correctly type twenty-plus random characters, quickly, without a single typo, is a distinctly worse experience than pointing a camera at a grid for a moment — and far more error-prone besides.

Why not a shorter, human-typeable code instead

A code short enough to comfortably type out is also short enough to occasionally be guessed or brute-forced, especially given a wider window of time to attempt it in. That trade-off is exactly why a PIN-based pairing method usually pairs a short code with a short expiry window, rather than trying to solve the whole security problem with length and randomness alone.

The security property people rarely think about

A QR code shown on a screen is also inherently local — someone has to be physically close enough, or looking at the same screen, to scan it. That's a real, if easy to overlook, security property: it naturally limits who's even in a position to attempt pairing, in a way a code sent over a network wouldn't.

Cameras being universal is what actually made this work

QR codes have existed as a technology since the 1990s, originally built for tracking parts on a factory floor. What changed, comparatively recently, is that essentially every device with a screen now also carries a camera and a browser that can access it directly — the browser-capability shift this blog has covered elsewhere. The format didn't change; what a browser could do with it did.

Why Nearsend offers three ways anyway

A QR code assumes a working camera, reasonable lighting, and a second device free to do the scanning — none of which is guaranteed. That's exactly why a PIN and a spoken voice phrase exist as fallbacks alongside it: three different ways of solving the same underlying problem, so one bad camera angle, a glare-covered screen, or a noisy room doesn't block pairing outright.