Supabase Storage Costs: Quotas and How to Cut Egress
On this page
Supabase Storage costs explained: Free and Pro quotas, egress, image transformations and file limits, with the limits that apply in Lovable apps.
Supabase Storage costs come from four meters: the gigabytes you keep, cached egress, uncached egress and image transformations. The Pro plan includes 100 GB of storage, 250 GB of cached egress, 250 GB of uncached egress and 100 origin images, and every unit above those quotas bills at its own rate. This guide is for founders and engineers who store user uploads on Supabase, and for Lovable builders who want to know which limits apply to their app. It follows Supabase's pricing page and Storage documentation and Lovable's storage documentation, read on 19 November 2026.
Key takeaways
- Storage bills on the average size over the billing period, measured in gigabyte-hours, so a late clean-up lowers the bill by a small amount.
- On Pro, uncached egress costs $0.09 per GB and cached egress costs $0.03 per GB after 250 GB each. Public buckets raise the CDN hit rate, and a long
cacheControllets browsers reuse a file without a new request. - Image transformations bill per distinct original image, at $5 per 1,000 above the 100 included. Ten sizes of one photo count once.
- Delete files through the Storage API. A SQL delete leaves the object in the bucket as an orphan.
What does Supabase Storage charge for?
Supabase charges for what you store and what Storage sends out, and it bills image resizing on top. Each meter has an included quota on a paid plan, and you pay for usage above it. The numbers below come from the pricing page and the usage guides.
| Meter | Free plan | Pro plan quota | Above the Pro quota |
|---|---|---|---|
| File storage | 1 GB | 100 GB | $0.0213 per GB per month |
| Uncached egress | 5 GB | 250 GB | $0.09 per GB |
| Cached egress | 5 GB | 250 GB | $0.03 per GB |
| Image transformations | Pro and above | 100 origin images | $5 per 1,000 origin images |
| Largest single file | 50 MB | Up to 500 GB | You set the limit |
The egress quota is shared. Database responses, Auth, Edge Functions and Storage all draw from the same 250 GB, which the documentation calls the unified egress quota. Our Supabase pricing guide covers the whole bill, including compute and the Spend Cap.
How does Supabase calculate storage size?
Supabase measures the total size of every object in your buckets and bills the average over the billing period, in gigabyte-hours. One gigabyte-hour is 1 GB stored for 1 hour. The unit price of $0.00002919 per gigabyte-hour equals $0.0213 per gigabyte for a full month.
The averaging rule has two consequences. A project that stores 20 GB for half a month and nothing for the other half averages 10 GB, the example Supabase gives in its documentation. A bulk upload that you delete the next day costs one day of storage. Deleting a large folder in the last week of the cycle lowers the average, and the bill reflects the weeks the files sat there.
The documentation gives a Pro example with 288 GB stored. That is 188 GB over the quota, which adds about $4 to the invoice.
Why does egress cost more than the files themselves?
Serving a file costs more than keeping it. Keeping 1 GB for a month costs $0.0213 above the quota, while sending that gigabyte to a browser once costs $0.09 uncached or $0.03 from the CDN cache. A file that thousands of visitors open every month produces more egress than storage cost.
Supabase splits egress into two meters, each with its own 250 GB quota on Pro, as the egress usage guide explains. Cached egress is data the CDN serves on a cache hit, and Supabase's documentation ties it to Storage files served through the Smart CDN. Uncached egress covers the rest, including cache misses.
How do public and private buckets cache?
Supabase says files in a public bucket benefit from a high cache hit ratio, because the CDN serves them without an authorization check. Private bucket permissions are checked per user, so two users who request the same file from one region can both get a miss. A signed URL adds another effect: Smart CDN treats each token as its own cache key, so the first request for any signed URL is a miss. Supabase says that if you generate a new signed URL on every request, the cache never warms. Reuse one signed URL across requests where your security model allows it.
Profile photos and logos fit a public bucket. Invoices and per-account documents belong in a private bucket, and the extra cache misses are the price of access control. Our guide to securing Supabase Storage buckets explains how to choose, and how signed URLs interact with the cache.
A worked example on the Pro plan
Take a photo app that stores 300 GB on average and sends 700 GB a month. The table compares two ways of serving those 700 GB. The figures use the unit prices above.
| Item | Served from the CDN cache | Served without caching |
|---|---|---|
| Storage above 100 GB | 200 GB × $0.0213 = $4.26 | 200 GB × $0.0213 = $4.26 |
| Egress above 250 GB | 450 GB × $0.03 = $13.50 | 450 GB × $0.09 = $40.50 |
| Overage on top of the $25 plan fee | $17.76 | $44.76 |
Each column assumes all 700 GB falls into one egress meter. A real project splits its traffic between the two meters, and each meter has its own 250 GB quota, so a split bill can come out below either column. The ratio holds: egress costs three times as much when the CDN cannot serve the file from cache.
How do cache settings lower the bill?
Cache settings lower the bill by keeping repeat requests off the origin. Four settings matter on Pro and above.
- Public buckets for static files. Supabase says public bucket files benefit from a high cache hit ratio, and each hit counts as cached egress.
- Smart CDN. Supabase turns it on for Pro and above. It caches each asset on the CDN for as long as possible and syncs asset metadata to the edge, so the cache revalidates when a file changes or disappears. After an update or delete, the invalidation can take up to 60 seconds to reach every data center.
- The cacheControl upload option. It sets how long browsers keep the file, independent of the CDN. The default browser lifetime is about 1 hour, and you can set a longer value. A browser that holds a fresh copy sends no request, so that view adds no egress.
- New paths for new versions. Supabase recommends uploading a changed file to a different path instead of overwriting it with
upsert, because overwrites can leave stale content at the edge while the change propagates.
Give each version of an image a new path, such as a content hash in the filename, and set a long cacheControl on it. Browsers reuse the file for that lifetime, the CDN keeps it as long as it can, and an edit becomes a new URL. Supabase warns that a CDN can evict an object that nobody has requested from a given region for a while, so expect some misses even with a long lifetime.
What do image transformations cost?
Image transformations cost $5 per 1,000 origin images above the 100 that Pro includes. An origin image is a distinct source file that you transformed during the billing period. Supabase counts it once, for any number of sizes you request. The documentation's example has four transformations across two files, and it counts two origin images.
Billing uses packages. The usage guide says that if your usage falls between two packages, Supabase bills the next whole package. Its Pro example uses 850 origin images, which is 750 over the quota, and adds $5 to the invoice. A product that resizes the same few thousand catalog photos pays little. A product that transforms every user upload pays for each new upload.
The transformation limits also shape the cost. Width and height must be whole numbers from 1 to 2,500. The source image cannot exceed 25 MB or 50 megapixels. The quality setting runs from 20 to 100 and defaults to 80. Request the size the screen shows and lower the quality for thumbnails. Switch the feature off in the dashboard if your app does not use it. Supabase's image transformations guide notes that disabling the feature stops any transformation request from processing, which prevents surprise usage.
Which file limits protect the bill?
File limits stop one bad upload from filling the quota. Set the global limit in Storage settings to the largest file your product accepts. The Free plan cannot go above 50 MB, and Pro and Team can go up to 500 GB. Then add a smaller limit to each bucket. A per-bucket limit must stay below the global one, and a bucket can restrict file types, so an avatar bucket accepts images and rejects video.
Upload method matters for large files. Supabase recommends standard uploads for files of 6 MB or less. Standard uploads can reach 5 GB, but the documentation recommends resumable (TUS) uploads above 6 MB for reliability. Our guide to secure file uploads for SaaS covers upload limits and storage costs on the application side.
How do you delete files without leaving orphans?
Delete files with the Storage API instead of a SQL query. Supabase's guide to deleting objects says a SQL delete does not remove the object from the bucket and leaves it orphaned. The row disappears from your view of storage.objects, and the bytes stay in storage.
const { error } = await supabase.storage
.from('uploads')
.remove(['avatars/old-1.png', 'avatars/old-2.png'])
The remove method accepts up to 1,000 objects per call. Emptying a bucket through the dashboard or the API fails above 200,000 objects. For those buckets, Supabase recommends syncing the bucket with an empty local directory through the AWS CLI and the project's S3 endpoint with the --delete flag. The command is slow on large buckets and leaves no orphans behind.
A scheduled clean-up job removes most waste. List the files in a bucket, compare the paths with the rows in your own tables, and remove files that no row references after a grace period. Abandoned uploads and deleted accounts leave files behind unless code removes them.
How do storage limits work in a Lovable app?
A Lovable app uses one of two setups, and each sets limits in a different place. Lovable's built-in backend (Cloud) includes storage, and you manage it from the Storage view. A project connected to your own Supabase project follows the Supabase quotas above.
| Lovable built-in storage | Your own Supabase project | |
|---|---|---|
| Upload size limit | 2 GB by default, adjustable up to 5 GB under More, then Storage | 50 MB on Free, up to 500 GB on Pro, set in Storage settings |
| What you pay | Stored files use Lovable run credits, including while the project is paused | The Supabase quotas and unit prices in the table above |
| Public buckets | Blocked by default on all plans, and a workspace owner or admin can lift the block | You decide per bucket |
| Per-bucket limit | Ask Lovable in the project chat to set it or read it back | Set in the bucket settings |
Lovable's documentation lists no price per gigabyte, so read the Usage view for what storage costs your project. Storage runs on the same backend as the database and user accounts, and the documentation says storage usage continues while a project is paused, because the files stay in place. Remove files you no longer need.
Moving between the two setups needs a manual file copy. Lovable's documentation says database exports contain schema and table data and leave out storage files, so download those files before you migrate or remove the built-in backend. Our Lovable Cloud to Supabase migration guide walks through the move.
How do you cut Supabase Storage costs?
Work through these steps in order.
- Open the usage page in your Supabase dashboard and note which meter is largest: storage, cached egress, uncached egress or image transformations.
- Set the global file size limit to your real maximum, then add a lower limit and a file type restriction to each bucket.
- Move static assets, such as logos and avatars, into public buckets, and keep private files in private buckets.
- Version file paths and set a long
cacheControlon files that stay the same for weeks. - Ask for the size the screen needs when you transform images, and switch image transformations off if you do not use them.
- Schedule a clean-up job that compares bucket contents with your tables and removes orphaned files through the Storage API.
Egress that Supabase has served cannot be reduced, so every change above lowers future usage.
Frequently asked questions
Is Supabase Storage free?
The Free plan includes 1 GB of file storage, 5 GB of egress, 5 GB of cached egress and a 50 MB limit per file. That covers a prototype. Supabase pauses Free projects after 1 week of inactivity, according to its pricing page, so a live product belongs on Pro, which includes 100 GB of storage.
Why did my egress jump while storage stayed flat?
Egress counts every byte that Supabase sends to a client, and all services share one quota. A single large file that many users download, or a page that loads full-size images, can use hundreds of gigabytes without adding a byte to storage. Check which meter grew on the usage page, then serve repeat requests from the CDN cache.
Does deleting a file lower this month's bill right away?
Deleting a file lowers the storage average a little more each day it stays gone, because Supabase bills the average size over the period. It does not reduce egress that Supabase already served. Delete through the Storage API so the object leaves the bucket.
Do image transformations bill for each resize?
No. Supabase bills each distinct origin image once per billing period, and the count resets at the start of the next cycle. Ten sizes of one photo count as one origin image.
Can I cap storage spending?
Supabase's cost control documentation lists egress, storage size and image transformations as items the Spend Cap covers. With the cap on, passing the storage quota sends a notification to your billing email and starts a grace period under Supabase's Fair Use Policy. On a paid plan without the cap, you pay the overage.
Summary
Supabase Storage costs follow four meters, and egress deserves the most attention. Set file limits that match your product, serve repeat files from the CDN cache, count image transformations by original, and delete through the API. If you want a second opinion on your buckets and cache settings before a launch, our backend and API development service covers PostgreSQL design, authentication, APIs and cloud infrastructure for startups.
Topic: AI-built apps & Supabase