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.

Sending Raw Photos and Video Without Compression: A Photographer's Guide

October 11, 2026

You shot it carefully — RAW stills, high-bitrate video — and then the tool you used to hand it off quietly threw quality away in the process. It's a common, often invisible problem, and it's worth understanding exactly where it happens.

Where compression sneaks in

Most messaging apps re-encode images and video by default to save bandwidth and storage — a sensible trade-off for a casual photo, a real problem for anything you need to look exactly right. Some free cloud-storage tiers do something similar: downsampling previews or transcoding video for faster streaming, sometimes without making that clear upfront.

Why RAW and high-bitrate footage is especially vulnerable

A RAW file or a high-bitrate video clip is exactly the kind of large file that trips assumptions built around a typical 3MB JPEG. Tools sized for ordinary photos don't handle a 45MB RAW file, or a multi-gigabyte video clip, gracefully — they cap, compress, or choke on exactly the files a working photographer or videographer actually needs to send.

What a direct transfer actually preserves

Since there's no upload-to-a-server-then-serve-it-back step, and no size cap forcing a format decision, the exact bytes you selected are what arrives on the other end — no recompression, no automatic format conversion, no stripped color profile.

A practical workflow for a shoot handoff

Send a batch as an actual folder rather than zipping it into one archive first — each file gets its own progress and its own retry, so one hiccup doesn't take the whole batch down. Doing the handoff in person, right after the shoot, also skips the wait a client would otherwise have for an upload to finish before they can even start reviewing.

What this doesn't solve

Worth being honest about the limits: a direct transfer can't make a weak Wi-Fi connection faster, and the recipient still needs software that can actually open a RAW or high-bitrate file. The transfer method guarantees the bytes arrive intact — not that every device on the other end can render them.