Supabase free tier limits: what the Free plan includes
Supabase’s Free plan costs nothing and includes two active projects, a 500 MB database per project, 5 GB of egress, 50,000 monthly active users, 1 GB of file storage, 500,000 Edge Function invocations and 2 million Realtime messages a month. API requests are unlimited. Free projects pause after a week of low activity, have no automatic backups, and are never billed: go over a quota and Supabase restricts the project instead of charging you.
New to Supabase? Start with what Supabase is. The numbers below come from Supabase’s pricing page and platform docs. Plans change, so check those pages before you rely on a limit.
Supabase Free plan limits at a glance
| Limit | Free plan | What happens at the limit |
|---|---|---|
| Active projects | 2, counted across every organization where you’re an Owner or Admin | Pause or delete one to start another. Paused projects don’t count |
| API requests | Unlimited | Not counted or billed, but responses use egress |
| Database size | 500 MB per project, on a fixed 2 GB disk | Fair Use restriction; read-only mode at 95% of the disk |
| Compute | Nano: shared CPU, up to 0.5 GB of memory, 60 direct connections, 200 pooled clients | Micro and larger sizes are paid-plan only |
| Egress (data sent out) | 5 GB, plus 5 GB served from the CDN cache | Grace period, then Fair Use restriction |
| Monthly active users | 50,000 | Grace period, then Fair Use restriction |
| File storage | 1 GB in total, 50 MB maximum per file | Larger uploads are rejected |
| Edge Functions | 500,000 invocations a month, 100 functions per project, 150 seconds wall clock per worker | Grace period, then restriction; no 101st function |
| Realtime | 2 million messages a month, 200 concurrent connections, 100 messages per second, 256 KB per Broadcast message | New connections refused; clients disconnected above the message rate |
| Logs | 1 day for API and database logs, 1 hour for auth audit logs | Older logs are gone |
| Backups | None | Export your own with supabase db dump |
| Inactivity | Paused after 7 days of low activity | Restore from the dashboard within a year |
| Support | Community only | No email support |
Branching, point-in-time recovery, custom domains, image transformations and leaked password protection all need a paid plan. Team members are unlimited on every plan.
Does the Supabase Free plan have unlimited API calls?
Yes. Supabase doesn’t count or bill requests to its database API on any plan, Free included.
What those requests use is limited. Every response counts toward the 5 GB egress quota: at 50 KB per response, that’s roughly 100,000 responses a month. Every query runs on the Nano compute instance, a shared CPU with half a gigabyte of memory. Sign-in endpoints have their own rate limits. Edge Function calls count as invocations, and live updates count as Realtime messages. So “unlimited API requests” means no request meter, not unlimited traffic.
What happens when you go over a Free plan limit
Usage quotas: a warning, a grace period, then restrictions
For egress, monthly active users, storage, function invocations and Realtime messages, Supabase emails your billing address and starts a grace period. If usage stays over, its Fair Use Policy applies, and restrictions can mean:
- pausing projects
- switching databases to read-only
- blocking new project launches and transfers
- answering every API request with HTTP status
402
Restrictions usually cover every project in the organization. They lift when the quota resets at the start of the next billing cycle, or straight away if you upgrade to Pro. Once you’ve used a grace period, going over again restricts the project straight away, until you’ve stayed under the limits for several cycles.
Pausing or deleting a project stops new usage but doesn’t erase usage already counted this cycle.
Database size: two different limits
The 500 MB figure is a billing quota. Supabase’s database size docs say it’s checked across the organization using the average daily size over the billing period, not today’s size. Deleting data doesn’t lift a restriction right away, because the average takes time to come down.
The physical limit is the disk. A Free project has a fixed 2 GB disk that never grows. At 95% full, the database switches to read-only, and writes fail with cannot execute INSERT in a read-only transaction. If the disk fills completely, Postgres shuts down and stays down until you upgrade. The write-ahead log (Postgres’s record of recent changes) shares that disk, so a bulk import or a large update can fill it even when your data is small. Split big writes into batches.
Inactivity: the project pauses
Supabase pauses a Free project when it gets too few database requests over 7 days. You get a warning email first, and visiting the project in the dashboard or sending it real traffic prevents the pause. A paused project keeps its data and can be restored from the dashboard for up to a year. Paid projects never pause (project pausing docs).
Hard caps: refused on the spot
Some limits don’t wait for a grace period. Files over 50 MB are rejected, which rules out most phone videos. The 201st Realtime connection is refused with too_many_connections, and a project sending more than 100 messages a second has clients disconnected until the rate drops (Realtime limits). A project can’t hold a 101st Edge Function.
Is the Supabase Free plan OK for production?
It’s fine for prototypes, demos, internal tools and early tests with a handful of users. It isn’t built for an app people pay for:
- No automatic backups. If a bad migration or a bug deletes data, you can restore only from exports you made yourself, which Supabase recommends doing regularly.
- Pausing. A B2B tool used once a week, or a launch that goes quiet, can pause.
- One day of logs. When a customer reports a bug from two days ago, the logs are gone.
- Small headroom. A 50 MB upload cap, a 2 GB disk and 200 Realtime connections run out quickly with real users.
- Community support only.
Whatever the plan, Supabase’s built-in email server sends 2 auth emails an hour and only to members of your project’s team (SMTP docs). Sign-up confirmations and password resets to real users need your own email provider.
Production apps outgrow these numbers quickly. A media delivery app we work on has more than 200 Edge Functions against the Free plan’s 100, and its creators upload single videos of 4 GB or more, so those go to separate object storage. A real-time trading platform we run sent over 2.5 billion Realtime messages in one billing cycle, against a Free allowance of 2 million. Realtime pricing explains why messages multiply so fast.
How to tell you’re close to a limit
- Open the organization’s usage page. It shows how each project is tracking against your plan’s quotas this billing cycle.
- Check database size on the project’s Database Reports page, or run
select pg_size_pretty(sum(pg_database_size(datname))) from pg_database;in the SQL editor. A new project already uses about 40 to 60 MB. - Check disk size on the Database Settings page. That’s the 2 GB figure that triggers read-only mode.
- Read Realtime logs for
too_many_connectionsand other refused joins. - Watch for
402responses and errors with SQLSTATE25006. The first means the organization is restricted, the second means the database is read-only. - Don’t ignore Supabase’s quota emails. The grace period starts with the first one.
What upgrading to Pro changes
Pro starts at $25 a month per organization and includes $10 of compute credits, enough for one project on the Micro size. Usage quotas are shared across the organization’s projects; disk is per project:
| Free | Pro | |
|---|---|---|
| Pausing | After 7 days of low activity | Never |
| Daily backups | None | 7 days |
| Database disk | 500 MB quota, fixed 2 GB disk | 8 GB included per project; grows past 8 GB automatically once the spend cap is off |
| Egress | 5 GB + 5 GB cached | 250 GB + 250 GB cached |
| Monthly active users | 50,000 | 100,000 |
| File storage | 1 GB, 50 MB per file | 100 GB, up to 500 GB per file |
| Edge Functions | 500,000 invocations, 100 functions | 2 million invocations, 1,000 functions |
| Realtime | 2 million messages, 200 connections | 5 million messages, 500 connections |
| Logs | 1 day | 7 days |
| Support | Community |
Above those quotas, Pro bills per unit. A spend cap is on by default, which blocks overage on most usage items rather than billing it. It doesn’t cap compute. Each extra project adds its own compute, from about $10 a month for Micro. Our guide to Supabase pricing walks through the full bill.
A Free project runs on Nano compute. After you upgrade, it stays on Nano but is billed at the Micro price, so move it to Micro, as Supabase recommends. The resize restarts the database, so do it at a quiet time.
Lovable Cloud apps follow different rules
Lovable Cloud is built on Supabase’s open-source foundation, but you don’t get a Supabase account or its Free plan. Lovable bills Cloud usage in its own credits: Free, Pro and Business workspaces get 20 Cloud credits a month, then usage draws on your general credit balance. When a workspace runs out of credits, Lovable’s plans and credits docs say apps on Cloud pause. The Supabase quotas above apply only if you connect your own Supabase project.
FAQ
How many free projects can I have on Supabase?
Two active projects, counted across every organization where you’re an Owner or Admin. If another Owner or Admin in an organization has used their two, nobody can start a free project there. Paused projects don’t count, so you can keep as many paused as you like.
Does Supabase charge you for going over the free tier?
No. The Free plan is never billed. Going over a quota leads to restrictions, from read-only mode to paused projects, until the quota resets or you upgrade.
How do I stop a free Supabase project from pausing?
Regular database activity prevents it: Supabase says a few real requests a day is usually enough. For anything users depend on, Pro is the reliable fix, because paid projects never pause.
If your app is already hitting Free plan limits in front of real users, our vibe coding rescue starts by finding which limit is breaking it and what it will cost to fix.
