API & NetworkingNo data storage or transmission to servers

Browser Video Call

Make a direct one-to-one P2P video call with screen sharing and private browser-to-browser chat.

Camera and microphone stay in your browser.

Microphone level: 0%

Enter a display name to continue.

Direct browser-to-browser call

Audio, video, screen content, and chat travel through WebRTC between the two browsers. codingtool.dev does not store them. Room codes only relay a short-lived connection handshake, never call content, and without a TURN relay some restricted networks may not connect.

A modern browser over HTTPS is required.

1-to-1 • No account • No server storage

Related Tools

Browser P2P File TransferSend files directly between two browsers using WebRTC. No upload, no account, no server storage.Internet Speed TestCheck download speed, latency, jitter, and upload availability from your browserQR Code GeneratorGenerate QR codes instantly from URLs, text, or JSON — no backend needed
What is P2P Browser Video Call?

A private one-to-one WebRTC call with video, audio, screen sharing, and chat sent directly between two browsers. No account, chat database, or media upload is used.

How room codes work
  1. 1.The caller enters a name and creates a room.
  2. 2.The receiver enters the 5-letter room code (or scans the QR code) and joins.
  3. 3.The call connects automatically once both sides are in the room — no manual copy-paste needed.
  4. 4.Video, audio, screen sharing, and chat then use the direct peer connection.
Manual pairing fallback

If a room cannot be created or joined, an advanced manual pairing option appears: the caller copies an invitation code to the receiver, the receiver copies back an answer code, and the caller applies it to connect.

Privacy and connection limits

codingtool.dev never receives or stores call content, chat messages, or media. Room codes use short-lived server-side signaling metadata (the WebRTC connection handshake only) to help two browsers find each other; that metadata expires automatically and is never used to relay audio, video, or chat. A public STUN service helps browsers discover a direct route but does not relay media either. Because no TURN relay is configured, restrictive NAT, corporate firewalls, VPNs, or some mobile networks can still prevent a connection.