Supabase Database Size Limit

Quick Answer

Free space: delete unused tables and rows, drop bloat with VACUUM FULL, remove large TOAST columns

The Limit

What is this limit?

The maximum amount of data your project database can store before the database is locked into read-only mode. The Free plan includes 500 MB; the Pro plan includes 8 GB.

Why this limit exists

Supabase runs one PostgreSQL instance per project and uses a size-based guardrail (read-only mode near the limit) so a single project cannot exhaust shared infrastructure, and so you have a clear signal to plan capacity upgrades.

What happens when this limit is exceeded

• The database switches to read-only mode - writes fail with 'cannot execute INSERT in a read-only transaction'
• You can still read data and run maintenance such as VACUUM
• Writes stay blocked until you free space or upgrade
• You receive email notifications as you approach the limit

How to check or raise this limit

1. Dashboard - Database shows database size usage vs the limit
2. Run SELECT pg_size_pretty(pg_database_size(current_database())) to measure precisely
3. Watch for the read-only warning banner in the dashboard
4. Raise the limit by upgrading plans in Dashboard - Billing

Code Examples

SELECT pg_size_pretty(pg_database_size(current_database())) AS db_size;

-- largest tables in the public schema
SELECT tablename, pg_size_pretty(pg_total_relation_size(quote_ident(tablename))) AS size
FROM pg_tables
WHERE schemaname = 'public'
ORDER BY pg_total_relation_size(quote_ident(tablename)) DESC
LIMIT 10;

You Might Also Like

Recommended Tools

Recommendations are editorial — DB Error Reference takes no payment or affiliate fees for tool listings.

Official Sources

This page is based on the official Supabase documentation linked below and adds practical guidance on top.

• Supabase Database size and read-only modeofficial
• Supabase Pricingofficial