LiveKit · Rate Limits

Livekit Rate Limits

LiveKit Cloud caps are tier-dependent and usage-driven. Common caps include max concurrent participants per room, max simultaneous rooms, max egress jobs in flight, and Agents session concurrency. Self-hosted LiveKit limits are operator-controlled by VM and SFU sizing.

3 Limits Throttle: 429

RealtimeWebRTCRate Limiting

Limits

Participants per room (typical default) room

concurrent_participants

1000

Simultaneous Egress jobs (typical) project

concurrent_jobs

Agents concurrent sessions (typical) project

concurrent_sessions

100

Tier-dependent; raised under Scale plan.

Policies

Room sharding

For very large rooms, shard participants across multiple LiveKit rooms with media-server fanout.

Backoff Strategy

Honor 429 Retry-After and apply exponential backoff with jitter on Twirp calls.

Sources

https://docs.livekit.io/home/cloud/quotas/