No Login Data Private Local Save

Local Peer‑to‑Peer Chat - Online No‑Server Messenger

Communication Network chat local P2P WebRTC
50
0
0
0
P2P Setup
Peer Not connected
No messages yet

Establish a P2P connection to start chatting. Your conversation is fully encrypted and private.

End-to-end encrypted · P2P direct connection

Frequently Asked Questions

Local Peer-to-Peer Chat is a direct communication method where messages travel directly between two browsers without passing through any central server. It uses WebRTC (Web Real-Time Communication) technology to establish a secure, encrypted data channel between peers. This means no third party—not even the website hosting this tool—can see your messages. Everything stays on your devices.

The tool uses a manual signaling approach. Instead of a server relaying connection information, you copy and paste an encoded "invitation" (containing SDP and ICE candidates) through any external channel—email, instant messaging, SMS, or even verbally. Once both peers exchange these codes, WebRTC establishes a direct encrypted connection. STUN servers (free public ones from Google) are used only for NAT traversal to help peers discover their public IP addresses; they never see your message content.

Yes. WebRTC encrypts all data channels using DTLS-SRTP (Datagram Transport Layer Security), the same encryption protocol used in VPNs and secure VoIP calls. The encryption is end-to-end: only the two browsers in the conversation can decrypt the messages. Even if someone intercepts the network traffic, they cannot read the content. Additionally, since no server stores your messages, there is zero risk of server-side data breaches. Your chat history is stored only in your browser's localStorage.

The copy-paste process replaces what a signaling server would normally do. In traditional WebRTC apps (like Zoom or Google Meet), a server coordinates the initial handshake between peers. Since this tool operates without any server, you act as the "courier" for the connection metadata. The codes contain your browser's network information (SDP session descriptions and ICE candidates) needed to establish the direct link. This 2-step exchange takes less than 30 seconds.

ICE (Interactive Connectivity Establishment) candidates are potential network addresses that your browser discovers for the P2P connection. They include: host candidates (your local IP on the LAN), srflx candidates (your public IP discovered via STUN, reflecting off a NAT), and relay candidates (TURN servers, not used in this no-server setup). The tool collects multiple candidates over ~3 seconds to maximize the chance of a successful direct connection, even when both peers are behind different NATs.

Connection failures can occur in symmetrical NAT environments (common in corporate networks or certain ISPs) where STUN alone cannot traverse the NAT. In such cases, a TURN relay server would normally be needed—but this tool intentionally avoids server dependencies. Other reasons include: firewalls blocking WebRTC ports, VPN interference, outdated browsers, or one peer losing internet access. If connection fails, try switching networks (e.g., mobile hotspot) or using a different browser.

The current version focuses on text messaging. However, WebRTC data channels natively support binary data transfer, making file sharing technically feasible. Future versions may include drag-and-drop file sharing with progress indicators. For now, you can share links or text-based content. Since the channel is direct P2P, file transfers would also be encrypted and server-free.

Chat messages are automatically saved to your browser's localStorage. When you close and reopen the page, your chat history is restored. However, the P2P connection itself is ephemeral—you'll need to re-establish it (re-exchange codes) to continue chatting. To permanently delete your chat history, click the trash icon in the chat header or clear your browser's site data.

All modern browsers with WebRTC support work: Google Chrome 28+, Mozilla Firefox 22+, Microsoft Edge 79+, Safari 11+ (including iOS Safari), Opera 18+, and Samsung Internet 4+. Mobile browsers on both Android and iOS are fully supported. The tool requires JavaScript enabled and recommends allowing notifications for a better experience. If you're on an outdated browser, please update to the latest version.

Key differences: (1) No account required—no phone number, email, or registration. (2) No server—messages never pass through or are stored on any intermediary server. Even Signal uses servers for message routing and storage. (3) Pure browser-based—no app installation needed. (4) Manual signaling—you control the connection metadata exchange. The trade-off is convenience: you need to copy-paste codes instead of just tapping a contact. For maximum privacy and zero infrastructure, this tool excels; for daily convenience, traditional messengers may be preferable.
🔧 Related Tools