What is the maximum file size limit on Share2Me?

There are absolutely no file size limits on Share2Me. Because the transfer is established directly peer-to-peer (P2P) between the sender and receiver browsers via WebRTC, the data does not pass through or store on any intermediate cloud server.

Is my data secure when transferring files and text?

Yes, completely secure. All transfers are end-to-end encrypted using military-grade AES-GCM-256 encryption. The encryption key is derived locally on your device via ephemeral ECDH (P-256) key exchange, meaning the raw key never leaves your browser and cannot be read by anyone, including the signaling server.

Do both devices need to be online at the same time?

Yes. Because Share2Me uses direct WebRTC peer-to-peer tunnels to transfer data, both the sending device and the receiving device must have the page open and be online concurrently to perform the transfer.

Can I transfer files between different operating systems?

Absolutely. Share2Me is entirely browser-native and cross-platform. It works seamlessly between iOS, Android, macOS, Windows, Linux, and any other operating system running a modern web browser, without needing any software installations.

Can I send clipboard text and messages securely?

Yes. Share2Me offers a dedicated Text Transfer mode. Copy-paste any text, passwords, or code snippets, and it will be encrypted and streamed securely through the same WebRTC pipeline, complete with a convenient 'Copy All' button for the receiver.

WebRTC

How to Transfer Files Peer-to-Peer in the Browser

June 28, 2026

File transfers traditionally require intermediate servers. You upload the file, the server saves it, and the receiver downloads it. Peer-to-peer (P2P) transfers bypass this server altogether. Using WebRTC, your browser connects directly to the receiver's browser, creating a direct data pipeline. In this guide, we explore how WebRTC coordinates peer-to-peer transfer, how direct connections bypass corporate firewalls, and why zero-storage architectures represent the future of web privacy.

1. The Mechanics of WebRTC DataChannels

WebRTC (Web Real-Time Communication) is an open-source standard enabling real-time browser communication. While commonly associated with video and audio calls, it contains a powerful component called RTCDataChannel. This channel allows the transport of arbitrary data directly between browsers. Unlike media feeds, DataChannels support TCP-like reliability (retransmissions) or UDP-like speed, configured to match network conditions.

Direct Connection: Data flows directly between peers, reducing latency and utilizing local network speeds.
Low CPU Overhead: Browsers stream binary data using native low-level socket connections.
Zero Server Storage: Servers are completely bypassed during data transfer, removing hosting security risks.

2. The Role of Signaling, STUN, and TURN Servers

If WebRTC is peer-to-peer, how do browsers locate each other? They use a process called signaling. Before a direct link is established, browsers must exchange connection offers, answers, and network configurations (ICE Candidates). A signaling server acts as a temporary mailbox for this handshake. Furthermore, because most devices reside behind NATs and firewalls, helper utilities are required to navigate direct traffic routing:

Signaling Server: A WebSocket server (e.g. Socket.io) used only to establish the initial connection.
STUN Servers: Simple public servers that tell your browser its external IP address and port configuration.
TURN Servers: Relay servers used as a backup. If symmetric firewalls prevent a direct peer-to-peer connection, traffic is securely routed through the TURN server. The data remains end-to-end encrypted and unreadable by the relay.

3. Bypassing Size Limitations and Throttling

Traditional cloud storage platforms restrict file sizes to control hosting bandwidth costs. Because WebRTC establishes a direct line, there are no artificial limits. The file is split into small binary chunks (e.g. 64KB - 256KB) and streamed sequentially. The browser reads files using the File System Access API or FileReader, keeping memory overhead minimal even when transferring massive multi-gigabyte archives.

Conclusion

By removing server dependencies, WebRTC DataChannels redefine internet file sharing. The transfer is only limited by physical network speeds. Share2Me harnesses this technology, providing secure, unlimited, and lightning-fast transfers directly inside your web browser.