P2P stands for Peer-to-Peer.
In WebRTC, P2P refers to the direct communication between two endpoints without media passing through an intermediary server. This is the simplest WebRTC architecture and is the default for one-to-one calls.
How P2P works in WebRTC
After ICE connectivity is established:
- Media (SRTP) flows directly between the two browsers
- No media server is involved (though signaling and STUN/TURN servers are still needed for setup)
- Data Channels also flow directly between peers
Advantages of P2P
- Lowest latency: No server hop in the media path
- Lowest cost: No media server infrastructure to maintain
- Privacy: Media never passes through a third-party server
- E2EE by design: Only the two endpoints can decrypt the media
Limitations of P2P
- Scaling: P2P only works for 1-to-1 calls. For group calls, you need a mesh (up to 4-6 participants) or an SFU/MCU
- NAT issues: Some NAT configurations prevent direct connectivity, requiring a TURN relay (which technically breaks pure P2P but data is still encrypted end-to-end)
- No server-side features: Recording, transcription, and moderation require a server in the media path
