P2P Chat — Private Peer-to-Peer Messaging
Message another person straight from browser to browser. Share an invite link, connect directly, and chat over an end-to-end encrypted channel — no account, no app, and no server storing your messages.
How peer-to-peer chat works
- Click “Create invite link” and send the link to the one person you want to chat with (via email, DM, or any app).
- They open the link — that’s it. Your two browsers negotiate a direct connection automatically.
- Chat away over an end-to-end encrypted channel. Messages travel straight from device to device and are never stored on any server.
Private by design
ByteKit P2P Chat is built on WebRTC data channels, the same browser-native technology used for video calls. Your two browsers form a direct connection and every message is encrypted with DTLS in transit. ByteKit runs no chat server: there is nothing to relay your messages, nothing to log them, and no account tying the conversation to your identity. The connection handshake travels inside the invite link's URL fragment, which browsers never transmit to a server.
Frequently asked questions
Is ByteKit P2P Chat really peer-to-peer?
Yes. It uses WebRTC data channels, so once the two browsers connect, your messages travel directly between the two devices. There is no chat server relaying or storing them.
Does a server ever see my messages?
No. Your messages are end-to-end encrypted and travel directly between the two browsers — ByteKit has no chat server that could read or store them. To introduce the two browsers, a one-time handshake (each side’s network details, roughly 1–2 KB, containing no message content) passes through a ByteKit signaling endpoint and is automatically deleted within a few minutes.
Do I need to sign up or install anything?
No account, no install, no extension. It runs in any modern browser. You just create an invite link and share it with one other person.
Why does connecting sometimes fail?
Establishing a direct connection relies on public STUN servers for NAT traversal. If both people are behind very strict or corporate firewalls (symmetric NAT), a direct link can not always be formed, since ByteKit uses no relay (TURN) server. Trying from a different network usually resolves it.
How many people can join a chat?
It is a private 1-to-1 conversation. Each invite connects exactly two people.
Are messages saved if I refresh the page?
No. The conversation lives only in your browser tab for the duration of the session. Refreshing or closing the tab clears it and ends the connection.