Supabase Realtime Concurrent Connections Limit

What the Supabase realtime concurrent connections limit is, what happens when you exceed it, and how to check or raise it — verified 2026-08-19.

200 connections Supabase Free plan Last verified 2026-08-19

Quick Answer

Share one supabase client instance app-wide

The Limit

200 connections Free plan

Plan	Limit
Free	200 concurrent connections

What is this limit?

The maximum number of simultaneous WebSocket connections to Supabase Realtime. Free projects allow 200 concurrent connections.

Why this limit exists

Each Realtime client holds an open WebSocket; caps prevent a single project from saturating the shared realtime gateway.

What happens when this limit is exceeded

New channels fail to connect
Clients report connection or authorization errors on channel join
Channels silently disconnect under load

How to check or raise this limit

Check Dashboard - Realtime usage metrics for connection counts
Reduce concurrent clients at the app level
Upgrade to a paid plan for a higher concurrent-connection cap

Code Examples

Clean up Realtime subscriptions javascript

const channel = supabase
  .channel('room-1')
  .on('postgres_changes', { event: 'INSERT', schema: 'public', table: 'messages' }, cb)
  .subscribe()

// on unmount / sign-out:
supabase.removeChannel(channel)

Removing channels prevents connection leaks that push you toward the concurrent cap.

Framework-Specific Notes

react

Always clean up Realtime subscriptions in useEffect to avoid leaking channels.

useEffect(() => {
  const channel = supabase.channel('todos')
    .on('postgres_changes', { event: '*', schema: 'public', table: 'todos' }, cb)
    .subscribe()
  return () => { supabase.removeChannel(channel) }
}, [])