WebRTC Text Chat (P2P) - Online No‑Server Messenger

This tool uses WebRTC (Web Real-Time Communication) — a browser-native technology that enables direct peer-to-peer connections. The initial "handshake" (exchanging SDP offer/answer codes) is done manually by copying and pasting between users. Once connected, all messages travel directly between the two browsers without passing through any server. No registration, no cloud storage, no intermediaries.

Yes. WebRTC mandates DTLS-SRTP encryption for all data channels. This means every message is end-to-end encrypted between the two peers. Even if someone intercepts the network traffic, they cannot decrypt the content. Additionally, since there's no server, no third party can access or log your conversations. The SDP codes exchanged for setup only contain network routing information (IP addresses and ICE candidates), not message content.

WebRTC requires a "signaling" step to establish the connection. Normally, this is done through a server. Since this tool is 100% serverless, the signaling data (SDP offer/answer) must be exchanged manually. Think of it like exchanging phone numbers before calling — once both parties have each other's information, the direct call can begin. You can share the codes via any channel: messaging apps, email, QR codes, or even verbally.

Connection failures usually happen due to symmetric NAT or strict firewalls that block P2P connections. This tool uses Google's public STUN servers to help peers discover their public IP addresses. If both peers are behind restrictive networks, a TURN relay server would be needed — but that requires a third-party server, which is not included in this serverless tool. Tips: try switching networks (e.g., from corporate VPN to mobile hotspot), disable VPN temporarily, or ensure both parties are on less restrictive networks.

No. Messages exist only in the browser memory during the active session. Once you close the tab, refresh the page, or disconnect, all messages are permanently lost. There is no server-side storage, no database, and no logging. The chat history is ephemeral by design. If you need to keep a record, copy important messages before ending the session.

Absolutely. This tool is fully responsive and works on all modern browsers including Chrome, Firefox, Safari, and Edge on both desktop and mobile. WebRTC is supported on iOS Safari (from iOS 11+) and Android Chrome. The copy/paste workflow works seamlessly on mobile, and you can also use the "Share Link" feature to send the invite URL via any messaging app.

Key differences: No server — messages never leave the direct browser-to-browser path. No account — no phone number, email, or registration needed. No logs — nothing is stored, not even metadata. No tracking — no analytics, no cookies, no surveillance. Regular messaging apps (even encrypted ones like Signal or WhatsApp) still route through servers and may retain metadata. This tool is truly ephemeral and private.

STUN (Session Traversal Utilities for NAT) helps a device discover its public IP address and the type of NAT it's behind. This tool uses free public STUN servers (Google's). TURN (Traversal Using Relays around NAT) acts as a relay when direct P2P connection is impossible. This serverless tool does not include a TURN server, which keeps it fully independent but may limit connectivity in very restrictive networks. Most home and mobile networks work fine with STUN alone.

No, this is strictly a one-to-one (1:1) P2P chat. WebRTC supports multi-party connections (via mesh or SFU architectures), but a serverless implementation for group chat would require each participant to connect to every other participant individually, making the setup exponentially more complex. For now, this tool focuses on simple, private 1:1 conversations.

The SDP codes contain network information (IP addresses, port numbers, and supported codecs). While the message content is encrypted separately, sharing these codes publicly could expose your IP address and potentially allow someone else to attempt a connection. It's best to share codes only with your intended chat partner through a private channel. The codes expire once used or when you close the page.