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.

Livekit Rate Limits is the machine-readable rate-limit profile for LiveKit on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring concurrent_participants, concurrent_jobs, and concurrent_sessions.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Realtime, WebRTC, and Rate Limiting.

3 Limits Throttle: 429
RealtimeWebRTCRate Limiting

Limits

Participants per room (typical default) room
concurrent_participants
1000
Simultaneous Egress jobs (typical) project
concurrent_jobs
25
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