Skip to content
Cloudflare Docs

Limits, timeouts and quotas

Understanding the limits and timeouts of Cloudflare Realtime is crucial for optimizing the performance and reliability of your applications. This section outlines the key constraints and behaviors you should be aware of when integrating Cloudflare Realtime into your app.

Free

  • Each account gets 1,000GB/month of data transfer from Cloudflare to your client for free.
  • Data transfer from your client to Cloudflare is always free of charge.

Limits

  • API Realtime per Session: You can make up to 50 API calls per second for each session. There is no ratelimit on a App basis, just sessions.

  • Tracks per API Call: Up to 64 tracks can be added with a single API call. If you need to add more tracks to a session, you should distribute them across multiple API calls.

  • Tracks per Session: There's no upper limit to the number of tracks a session can contain, the practical limit is governed by your connection's bandwidth to and from Cloudflare.

Inactivity Timeout

  • Track Timeout: Tracks will automatically timeout and be garbage collected after 30 seconds of inactivity, where inactivity is defined as no media packets being received by Cloudflare. This mechanism ensures efficient use of resources and session cleanliness across all Sessions that use a track.

PeerConnection Requirements