Quotas and limits

Understanding the quotas and limits for LiveKit Cloud plans.

Free quotas

Every LiveKit project gets the following for free:

Connection limits

LiveKit projects have limitations on the number of concurrent connections of various types in order to ensure the stability of the network and to prevent abuse. This is similar to rate limiting for an HTTP service, but for a continuous service with long-lived connections. Like rate limiting, the primary purpose of these connection limits is to prevent abuse.

You can view the current connection limits on your project at any time in the LiveKit Cloud dashboard by navigating to Settings and selecting the Project tab.

For pricing information for any of the following plans, see the pricing guide.

Build plan

Projects on the Build (free) plan have the following limits:

When these limits are reached, new connections of the same type fail.

Ship plan

Projects on the Ship plan have the following limits:

  • 1,000 concurrent participants.
  • 100 concurrent egress requests.
  • 100 concurrent ingress requests.

When these limits are reached, new connections of the same type fail.

Scale plan

Projects on the Scale plan have the following limits:

  • Unlimited concurrent participants.
  • 100 concurrent egress requests.
  • 100 concurrent ingress requests.

When these limits are reached, new connections of the same type fail.

An admin for your project can request an increase for a particular limit in your project settings.

Custom plan

LiveKit can work with you to ensure your project has the capacity it needs. Contact the sales team with your project details.

Egress time limits

Egress has time limits, depending on the output type:

Egress outputTime limit
File output (MP4, OGG, WebM)3 hours
HLS segments12 hours
HLS/RTMP streaming12 hours

When these time limits are reached, any in-progress egress automatically ends with the status LIMIT_REACHED.

You can listen for this status change using the egress_ended webhook.

Media subscription limits

Each participant may subscribe to a limited number of media tracks. Currently, the limits are as follows:

  • Up to 100 video tracks.
  • Up to 100 audio tracks.

For high volume video use cases, consider using pagination and selective subscriptions to keep the number of subscriptions within these limits.

API request rate limits

All projects have a 1000 requests per minute rate limit on API requests. The limit only applies to Server API requests (for example, RoomService or EgressService API requests) and doesn't apply to SDK methods like joining a room or sending a data message.

LiveKit doesn't anticipate any project exceeding this rate limit. However, you can reach out to support to request an increase. Include the Project URL in your email. You can find your project URL in the LiveKit Cloud dashboard in your Project Settings page.