# Supabase Storage limit, free tier and pricing, explained

> How much file storage each Supabase plan includes, the max upload size per plan, the overage price, and what changes once you exceed the included amount.

Source: https://scribase.com/supabase-storage-limit

Supabase Storage is billed separately from database size. Free includes 1 GB and caps a single upload at 50 MB; Pro and Team jump to 100 GB included with a 500 GB per-file ceiling, and extra storage is metered, not a hard wall.

## Included storage and max upload size per plan

_From the Supabase pricing page (checked 2026-10-12)_

| Plan | Storage included | Max single upload | Overage |
| --- | --- | --- | --- |
| Free | 1 GB | 50 MB | Not billed; uploads fail once the project is over |
| Pro | 100 GB | 500 GB | $0.0213 per GB |
| Team | 100 GB | 500 GB | $0.0213 per GB |
| Enterprise | Custom | Custom | Custom |

## Sources

- [Supabase: Pricing](https://supabase.com/pricing)

## Why an upload fails before the file is even large

- The 50 MB per-file ceiling on Free is separate from the 1 GB total: a single 60 MB file is rejected even with plenty of the 1 GB left.
- Storage counts against the same organization-wide quota as every other project on the plan, so one busy project can use up storage meant to be shared.
- Resumable (TUS) uploads still obey the same per-file ceiling; chunking a 2 GB file on Free does not bypass the 50 MB limit.

## Sources

- [Supabase: Pricing](https://supabase.com/pricing)

## Getting more room

- Upgrade to Pro: the included 1 GB becomes 100 GB and the per-file ceiling becomes 500 GB in the same step.
- On a paid plan, storage past the included 100 GB is billed per GB rather than blocked, so a growth spike is a bill, not an outage, unless a spend cap is set.
- Compress or resize before upload for anything that does not need the original (images, video thumbnails) — it is the cheapest way to stay under a per-file ceiling and cuts egress on every later download too.

## Sources

- [Supabase: Pricing](https://supabase.com/pricing)

## Storage access is still an RLS decision, not just a quota one

Every upload and download is a row operation on storage.objects, so who can read or write a file is controlled the same way as any other table: an RLS policy. A missing policy blocks uploads outright, independent of the size limit.

## Sources

- [Supabase: Storage access control](https://supabase.com/docs/guides/storage/security/access-control)

## Storage on Scribase

Every Scribase project includes 100 GB of Storage at $25 a month with a 5 GB per-file ceiling, the same supabase-js Storage client, and RLS policies on storage.objects that move over unchanged with the importer.

## Sources

- [Scribase pricing](https://scribase.com/pricing)

## FAQ

**What is the Supabase Storage limit on the Free plan?**

1 GB of total storage with a 50 MB maximum size for any single uploaded file.

**Is Supabase Storage billed separately from database size?**

Yes. Database disk size, Storage, and egress are three separate quotas with their own included amounts and overage prices on paid plans.

**What happens if I go over the Supabase Storage limit?**

On Free, new uploads fail once the project is over its allowance. On Pro and Team, storage past the included 100 GB is metered at $0.0213 per GB rather than blocked.

**Can I raise the per-file upload limit without upgrading the plan?**

No. The per-file ceiling (50 MB Free, 500 GB Pro/Team) is set by the plan.

## Related

- [RLS policy examples](https://scribase.com/supabase-rls-policy-examples)
- [Supabase storage RLS 403](https://scribase.com/supabase-storage-rls-403)
- [Supabase egress limit exceeded](https://scribase.com/supabase-egress-limit-exceeded)
- [Supabase alternative](https://scribase.com/supabase-alternative)
- [Pricing](https://scribase.com/pricing)