How browser P2P video calls work

Three parts of a browser call

First, your browser asks for camera and microphone permission. Second, Rulxo signaling exchanges connection information with your partner. Third, WebRTC looks for a usable network path and starts encrypted audio and video. Text chat and moderation reports use the server.

P2P with a TURN fallback

A direct connection can carry media browser to browser. Firewalls, network address translation or restrictive mobile networks can prevent that path. TURN provides a relay for encrypted media. Relay use is normal and may add latency; P2P does not mean the service has no servers.

What encryption protects

WebRTC encrypts media in transit. Your partner receives and can record that media. Connection metadata, text messages and reports are separate from the media path. A direct peer connection can reveal network addresses; do not equate P2P with total anonymity.

Fix a missing camera or microphone

Use a current browser on HTTPS. Check site permissions and your operating system’s camera and microphone permissions. Close other apps using the device, then retry Look Check. The call menu provides Camera & Mic Sources for changing inputs. If the camera is muted, use the camera toggle.

Fix a call that will not connect

Check that both participants still have connectivity. Try a different network if a firewall blocks WebRTC, and reconnect after changing networks. Video quality depends on bandwidth, device load and the camera. Effects and background blur use extra processing; turn them off on slower devices.

Questions before you start