Frequently Asked Questions

Everything worth knowing about how Nearsend's peer-to-peer sharing actually works, in plain terms, from what happens to your files in transit, to how pairing works, to how Nearsend compares with the sharing tools already built into most devices today.

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

They are never stored. Nearsend is a peer-to-peer (P2P) platform: the signaling server only exchanges temporary session tokens and WebRTC handshake coordinates. Once connected, your files, text, and clipboard stream directly between your devices via WebRTC DataChannels in 64KB DTLS-encrypted chunks. If a direct path is blocked (some corporate or mobile networks), an encrypted TURN relay forwards the data without being able to read it, and Nearsend tells you when that is happening.

How does the Voice Pairing work securely?

When you generate a voice pairing phrase (e.g. "Blue Falcon 728"), 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 it work across different operating systems?

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

Does it work on HarmonyOS phones, tablets and laptops?

Nearsend runs in the browser, so it works on a HarmonyOS phone, tablet or laptop whose browser supports WebRTC, which is what the direct connection uses. It needs no app and no Google services, and you can send to and from Windows, macOS, iPhone, and Android. HarmonyOS versions and browsers differ, so if pairing fails, try another browser on the device.

What is Local-Only Mode?

Local-Only Mode restricts WebRTC negotiation exclusively to local network IP candidates (mDNS and local LAN). It prevents connecting through external public STUN/TURN relays, guaranteeing transfers remain on your local Wi-Fi router.

Can I transfer entire folders?

Yes! You can drop an entire folder into the drop zone or click "Select Folder". Nearsend recursively traverses the directory tree using modern browser FileSystem entry APIs and preserves relative file paths.

Is there a file size limit?

Nearsend imposes no file size cap, and nothing is uploaded to a server. The practical limit is the receiving device: the browser holds a file in memory until it is saved, so multi-gigabyte files are best received on a desktop computer with plenty of free RAM, and Nearsend warns you before accepting a very large transfer. Backpressure flow control keeps the sender from overrunning the connection.

How does Nearsend compare to Apple AirDrop, Snapdrop, or LocalSend?

Unlike AirDrop, Nearsend works on every operating system without requiring Apple hardware or iCloud accounts. Unlike traditional file upload services, no files are stored in the cloud. Unlike native apps, Nearsend runs in any browser with zero installation.

Pairing works but files will not send in Brave. What should I do?

Brave’s Shields can block the network information a direct WebRTC connection needs, so two devices pair but the connection never opens. Tap the lion icon, turn Shields off for nearsend.app, reload both devices and pair again. If it still fails, use Safari or Chrome, and turn off any VPN or private relay.

Do both devices need to be on the same Wi-Fi network?

By default, Nearsend prioritizes local LAN/Wi-Fi connection candidates for maximum gigabit transfer speeds. If devices are on different networks, standard WebRTC STUN/TURN traversal coordinates the peer-to-peer connection.

Still have a question?

These eight questions cover the most common things people ask before or during their first transfer. For anything more specific, a particular error message, an unusual network setup, or a device combination not covered here, the Contact page is the direct way to reach the team, and this site's blog covers several of these topics in more depth than a short FAQ answer can, including dedicated posts on troubleshooting a stalled transfer, understanding what actually happens on a restrictive network, and how the underlying WebRTC technology works step by step.

Before asking, it's worth checking

A surprising number of pairing issues come down to one of three things: a camera permission that was never granted, a background tab that got throttled mid-transfer, or a corporate or guest network that isolates devices from each other. Ruling those out first often resolves the issue faster than waiting on a reply, and each one is covered in genuinely more depth elsewhere on this site.

Guides

Phone to PC Send Folders Large Files Without an App LocalSend Alternative P2P Transfer Without Shared Wi-Fi Private Sharing