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 File Transfer Gets Stuck at 99% (and How to Fix It)

September 13, 2026

It's one of the most universally frustrating moments in computing: a progress bar climbs cleanly to 99%, and then just sits there. Here's what's actually happening, and what genuinely helps.

It's rarely actually 99% done

A progress bar for a chunked transfer usually reflects how much data has been sent, not how much has been fully received and confirmed. The last stretch — the final acknowledgment, assembling the last pieces, cleanly closing out the connection — can take real, disproportionate time compared to the steady climb that got you to 99% in the first place.

A dropped connection the UI hasn't caught up to

The more common culprit is a connection that quietly dropped without the interface noticing yet — a Wi-Fi hiccup, a laptop going to sleep, a phone screen locking, or a browser throttling a tab that's been sitting in the background. The data channel has effectively gone quiet, but the progress bar hasn't been told that yet.

Practical fixes

Keep both devices' tabs in the foreground and screens awake for the duration of a large transfer — background throttling is a common, invisible cause of exactly this stall. If it does stick, retrying is usually faster than waiting it out. And check that both sides still show as connected before assuming the transfer itself is the problem — sometimes the pairing dropped first.

Why a folder can actually help here

Sending a large batch of files as an actual folder, rather than one giant archive, has a real practical advantage: each file gets its own progress and its own retry, so one stalled file doesn't take the rest of the batch down with it — you're not stuck re-sending everything from zero.

If it keeps happening

A stall that repeats on the same network points to that network, not the transfer tool — try switching from Wi-Fi to a mobile hotspot (or the reverse) to see if the pattern follows the connection.