Supabase Limits

Supabase Limits: Complete reference of Supabase plan limits: database size (500 MB free /… Searchable index with fixes, code examples, and official sources.

Supabase enforces hard limits per plan: database size, per-object storage size, connection counts, and realtime concurrency. The important detail is what happens when you cross each one — some limits block writes (database size switches the instance read-only), others reject individual requests (uploads over 50 MB fail with EntityTooLarge). Each page below documents the threshold, the exact failure mode, and how to check current usage before your users hit it.

5 limits Supabase Last verified 2026-08-19

All 5 limits

database-size-limit Database Size Limit The maximum amount of data your project database can store before the database is locked into read-only... database-connections-limit Database Connections Limit The maximum number of simultaneous direct database connections. Free projects allow 60; Pro projects allow... storage-object-size-limit Storage Object Size Limit Each individual file uploaded to Supabase Storage can be at most 50 MB (52,428,800 bytes). The per-object... realtime-concurrent-connections Realtime Concurrent Connections Limit The maximum number of simultaneous WebSocket connections to Supabase Realtime. Free projects allow 200... free-project-inactivity-pause Free Project Pause Free plan projects are paused automatically after 1 week (7 days) of inactivity - no API requests,...

Official Sources