This page contains information about legacy WebRTC Go ("Go") and Peer-to-Peer ("P2P") Video Rooms. Twilio customers who used Go or P2P Rooms prior to October 21, 2024, may continue to use those types and Twilio will continue to support them. However, customers who weren't using these Room types prior to October 21, 2024 won't have access to them and will only have access to Group Rooms.
Go and P2P Rooms both use peer-to-peer media exchange; Participants share audio and video data directly between one another without relaying that media through Twilio's cloud. Twilio infrastructure acts as the signaling server and helps each Participant create a direct connection to every other Participant in the Room for sending audio and video data.
Both Go and P2P Rooms have the following characteristics:
The following picture illustrates the architecture of a P2P Room with three Participants.
As seen above, in a P2P Room, a Participant needs to send their audio and video streams once for each other Participant in the Room. As a result, upstream bandwidth (and typically battery consumption) scales as n-1
, where n
is the number of Participants. Because of this, P2P Rooms do not scale well with more Participants.
Go Rooms are for one-on-one video calls. Participant minutes and TURN server usage is free. Go Rooms use a peer-to-peer topology, but the maximum number of Participants in a Go Room is two. There can be a maximum of 500 concurrent Participants at a time per Account. For example, one Account could host a total of 250 Rooms with two Participants each.
P2P Rooms can have up to 10 Participants. However, for best video quality, we recommend that P2P rooms have no more than three participants in a video call (or four participants with low-quality video). For audio-only calls, P2P rooms can have up to 10 participants.