This documentation is for reference only. We are no longer onboarding new customers to Programmable Video. Existing customers can continue to use the product until December 5, 2026.
We recommend migrating your application to the API provided by our preferred video partner, Zoom. We've prepared this migration guide to assist you in minimizing any service disruption.
The Programmable Video service operates within certain quotas and limits that ensure a reliable and consistent operation. Quotas are account based and can be increased on request, whereas limits are system wide and independent of the account.
The following table describes the default values for Group Rooms and P2P Rooms:
| Default Quota [1] | Notes | |
|---|---|---|
| Max Concurrent Rooms | 10,000 [2] | Maximum Rooms that can be in-flight at the same time |
| Max Concurrent Participants | 10,000 [2] | Maximum Participants that can be connected to your Rooms at the same time |
| Max REST API Read Requests per second | 80 | Maximum Read requests, e.g get Room, get list of Participants, etc. |
| Max REST API Write Requests per second | 20 | Maximum Write requests, e.g create Room, update Participant, etc. |
[1]: More information on these quotas and how to design your application with these in mind can be found on the Guide to Scaling Applications page. Should you need an increase then contact sales.
[2]: Note that WebRTC Go Rooms are limited to 500 concurrent rooms or participants per customer (per parent account).
The following table illustrates the standard limits of the different Twilio Rooms:
| Go Room | P2P Room | Small Group Room | (Regular) Group Room | |
|---|---|---|---|---|
| Max Participants | 2 | 3 [1] | 4 | 50 [2] |
| Max Participant Duration | 24 hours | 24 hours | 24 hours | 24 hours |
| Max Room Duration | 24 hours | 24 hours | 24 hours | 24 hours |
| TURN Server Usage | Unlimited | Unlimited | Unlimited | Unlimited |
[1]: Can support up to 10 audio-only participants, but max 3 participants recommended when video is published
[2]: Group Rooms can support up to 35 PSTN participants. Learn more about adding Programmable Voice participants to Video Rooms.
The following limits are independent of the Room type:
| Value | |
|---|---|
| Max Room Name | 128 characters |
| Max Participant Identity | 128 characters |
| Max Track Name | 128 characters |
The following describes bandwidth limits for each Participant in a Room:
| Go Room | P2P Room | Small Group Room | (Regular) Group Room | |
|---|---|---|---|---|
| Publisher Bandwidth per Participant | ∞ | ∞ | 20,000 Kbps | 20,000 Kbps |
| Subscription Bandwidth per Participant | ∞ | ∞ | 4,000 Kbps | 4,000 Kbps |
The following describes the recommended limit of total tracks by media type per Room:
| Go Room | P2P Room | Small Group Room | (Regular) Group Room | |
|---|---|---|---|---|
| Max Audio Track Publications per Room | 4 | 6 | 6 | 60 |
| Max Video Track Publications per Room | 4 | 6 | 8 | 60 |
| Max Data Track Publications per Room | 2 | 3 | 4 | 50 |
The following describes the recommended limit of subscribed tracks per Participant:
| Go Room | P2P Room | Small Group Room | (Regular) Group Room | |
|---|---|---|---|---|
| Max Audio Track Subscriptions per Participant | 2 | 4 | 6 | 60 |
| Max Video Track Subscriptions per Participant | 4 | 8 | 8 [1] | 60 [1] |
| Max Data Track Subscriptions per Participant | 1 | 2 | 3 | 49 |
[1]: While it is possible to subscribe to many video tracks it is recommended that you limit the number of subscribed video tracks that receive media by using clientTrackSwitchOffControl when connecting to a Room using the network bandwidth profile.
The following describes the recommended limit of published tracks per Participant:
| Go Room | P2P Room | Small Group Room | (Regular) Group Room | |
|---|---|---|---|---|
| Max Audio Track Publications per Participant | 2 | 2 | 2 | 2 |
| Max Video Track Publications per Participant | 4 | 4 | 6 | 6 |
| Max Data Track Publications per Participant | 1 | 1 | 1 | 1 |