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 Your Browser Can Now Do What Used to Need an App

September 27, 2026

Not long ago, doing almost anything beyond reading a page meant there was an app for that — a separate download, a separate icon, a separate update cycle. Browsers have quietly closed a lot of that gap, and it's worth understanding what actually changed.

The old browser could barely touch your hardware

Early browsers were essentially document viewers. No camera access, no ability to open a live connection to another device, no meaningful way to work with local files beyond a basic upload button. Anything beyond that needed a native app with real operating-system permissions.

What actually changed

Over roughly the past decade, browsers gained a set of standardized capabilities, shipped consistently across Chrome, Firefox, Safari, and Edge: camera and microphone access, WebRTC for opening a real-time connection to another device, and APIs for working directly with local files. None of it is exotic technology — it's mostly become unremarkable, standard equipment.

Why this matters for something like file transfer

Nearsend is a direct example of the shift: scanning a QR code with a camera, opening a live peer connection, streaming a file straight to disk — every one of those was exclusively native-app territory a few years ago. Now it runs in a browser tab, no install step in between.

The trade-off that's still real

It's worth being honest that a browser tab still can't do everything a native app can — there's no persistent background execution once the tab is closed, and browsers still don't get the same low-level local-network discovery native apps do. This isn't "browsers replaced apps entirely" — it's that the gap narrowed a lot, specifically for real-time, one-off tasks.

Why that's good news for something you use occasionally

For a tool you reach for now and then rather than every day, not needing to install, keep updated, and eventually clean up an app is a genuine improvement — the capability is just there when you open a link, instead of a day-one download you'll forget to remove later.