// free plan limits

Which free plan limit will your app hit first?

A paused database, a read-only table, a "Site not available" page: free plan limits break apps in ways that look like bugs. Answer four questions and see which limit comes first for your app, then what it looks like when it does.

Your answers stay in this page. Nothing is sent or stored.

About your app

Your app runs on
How many people use it on a typical day?
How much data does the database hold, or will soon?
Do people upload files?
How often does it go unused?

The limits your app meets first

A rough estimate from your answers, highest first. The assumptions are below.

Also true whatever your answers

  • Netlify Each production deploy uses 15 credits. Deploys spend the same credits as traffic, so a day of many deploys can pause the sites. Deploy previews, branch deploys and failed deploys use none.
  • Vercel Personal, non-commercial use only. Taking payments, showing ads or being paid to build the site needs the Pro plan.
  • Vercel 300 seconds per function call. A slower call, like a long AI request, stops with 504 FUNCTION_INVOCATION_TIMEOUT.
  • Firebase No Cloud Functions on Spark. Server code in Cloud Functions needs the Blaze plan.
  • Supabase 2 active projects. A third project cannot run until you pause one. Paused projects do not count.
How the estimate works
  • Each daily user makes 1 visit a day, and monthly users are 4 times the daily users.
  • A visit downloads 1 MB from the host on average and makes 20 requests, 5 of them to server functions.
  • A visit reads 200 KB from the database, or makes 30 Firestore reads and 3 writes.
  • Photos and documents means about 500 MB in all with files up to 8 MB; video or large files, about 5,000 MB with files up to 200 MB.
  • Each answer counts above the middle of its range, so the ranking warns early. Your own usage page is the real number.

The limits, service by service

Supabase Free plan

Pricing page

  • Paused after 7 days with no activity

    When you hit it: Every database and sign-in call fails because the whole project is paused. Restore it from the dashboard with one click; that stays possible for a year.

  • 500 MB database size

    When you hit it: The database turns read-only: reads work, but saves fail with "cannot execute INSERT in a read-only transaction".

  • 5 GB of data sent out a month

    When you hit it: You get a notice and a grace period. Past it, Supabase can restrict the project, and API calls can return status 402.

  • 1 GB of file storage

    When you hit it: Uploads past the quota get the same notice, grace period and restrictions.

  • 50 MB largest file upload

    When you hit it: A bigger file is refused at upload, however much space is left.

  • 50,000 signed-in users a month

    When you hit it: Past it, the same notice, grace period and restrictions as the other quotas apply.

  • 2 active projects

    When you hit it: A third project cannot run until you pause one. Paused projects do not count.

Check your usage In the Supabase dashboard, the organization usage page shows each quota for the billing cycle. A paused project shows a Restore button on its project page.

Vercel Hobby plan

Pricing page

  • 100 GB of data transfer a month

    When you hit it: Vercel reaches out first. Sustained use past a Hobby limit can pause the deployment: visitors get 503 DEPLOYMENT_PAUSED until you resume it.

  • 1,000,000 function calls a month

    When you hit it: Same as data transfer: sustained use past it can pause the deployment.

  • 4 hours of active CPU a month

    When you hit it: Same as data transfer: sustained use past it can pause the deployment.

  • 300 seconds per function call

    When you hit it: A slower call, like a long AI request, stops with 504 FUNCTION_INVOCATION_TIMEOUT.

  • 4.5 MB per request or response body

    When you hit it: An upload sent through a function that is bigger fails with 413 FUNCTION_PAYLOAD_TOO_LARGE. Upload straight to storage instead.

  • 100 deployments a day

    When you hit it: Further deploys are refused until the day has passed.

  • Runtime logs kept for 1 hour

    When you hit it: An error from this morning is gone from the logs by the time you look.

  • Personal, non-commercial use only

    When you hit it: Taking payments, showing ads or being paid to build the site needs the Pro plan.

Check your usage In the Vercel dashboard, the Usage tab shows each Hobby allotment used this month.

Netlify Free plan

Pricing page

  • 300 credits a month, hard limit

    When you hit it: When the credits run out, every site on the team is paused and visitors see "Site not available". The Free plan cannot buy more; credits reset each cycle.

  • Each production deploy uses 15 credits

    When you hit it: Deploys spend the same credits as traffic, so a day of many deploys can pause the sites. Deploy previews, branch deploys and failed deploys use none.

  • 20 credits per GB of bandwidth

    When you hit it: On a busy site, bandwidth is usually what uses the credits up.

  • 2 credits per 10,000 web requests

    When you hit it: Every request counts, including edge functions.

  • 10 credits per GB-hour of function compute

    When you hit it: Slow or memory-heavy functions use credits fastest.

Check your usage In the Netlify dashboard, the team usage page shows the credits used and left this cycle.

Firebase Spark plan

Pricing page

  • 1 GiB stored in Firestore

    When you hit it: Past a no-cost quota on Spark, the product is shut off for the project until the quota resets or you move to the Blaze plan.

  • 50,000 document reads a day

    When you hit it: Reads fail for the rest of the day. The quota resets around midnight Pacific time.

  • 20,000 document writes a day

    When you hit it: Saves fail for the rest of the day. The quota resets around midnight Pacific time.

  • 360 MB of hosting transfer a day

    When you hit it: After a short grace period the site is disabled until the start of next month.

  • 10 GB of hosting storage

    When you hit it: The site stays up, but new deploys fail until you delete old releases.

  • 50,000 signed-in users a month

    When you hit it: Past a no-cost quota on Spark, the product is shut off until the quota resets or you move to the Blaze plan.

  • No Cloud Storage on Spark

    When you hit it: File uploads need the Blaze plan. Since February 3, 2026, Spark projects get 402 or 403 errors from every Cloud Storage bucket.

  • No Cloud Functions on Spark

    When you hit it: Server code in Cloud Functions needs the Blaze plan.

Check your usage In the Firebase console, the Usage and billing page shows each product against its Spark quota.