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.

File Sharing for Remote Teams Without a Shared Cloud Account

October 4, 2026

The default assumption in a lot of remote work is that everything goes through the shared drive. That's true for ongoing collaboration — it isn't always true for a one-off handoff.

What shared cloud storage is actually for

A team drive earns its place for anything more than one person will need over time — ongoing documents, shared assets, anything that benefits from version history and everyone having consistent access.

Where it's overkill

A one-off handoff between two specific people — a contractor delivering a final file to the one person who requested it, a quick asset handoff between two teammates mid-call — doesn't need a shared drive's permissions setup or persistent storage just to happen once.

The friction a shared account adds to a one-off

Before a cloud handoff even starts, someone often has to check the recipient actually has access to the right folder, or share a link with the right permissions set correctly. For a single file to one person, that setup can genuinely take longer than the transfer itself.

Where a direct transfer fits into a remote workflow

For a same-call, right-now handoff between two people already talking — a screen-share call, a quick huddle — pairing directly and sending skips the account-and-permissions step entirely. The file just moves.

Not a replacement for the team drive

This is a complement, not a competitor: the shared drive is still where a team's ongoing, multi-person assets belong. A direct transfer is for the specific, common case of one person handing one thing to one other person, right now.