Skip to main content
NinjaNext
MVP and product

Lovable Storage Quota Full? What Is Actually Using It

Your Lovable app's file storage is Supabase underneath, and the usual advice does not reach you. Why deleting files often changes nothing, and what to do instead.

By NinjaNext TechnologiesPublished 5 min read

Key takeaways

  • Lovable's built-in backend runs on Supabase, so Supabase's storage quota is the one you are hitting.
  • Deleting files from a database table leaves the files themselves behind. Usage stays exactly where it was.
  • The quota is measured as an average across the whole billing period, so clearing space late in the month may not lift the restriction until the next one starts.
  • Database, logins and files are one backend. Removing the database to reclaim space takes your uploaded files with it.

You uploaded a few hundred images, the app started refusing new ones, and somewhere a message mentioned a storage quota. You deleted the old files. Nothing changed. This is one of the more confusing walls to hit in an AI-built app, because the tool you built in and the service that is actually complaining are two different products, and almost everything written about the problem is addressed to people using the second one directly.

Lovable's own documentation says the built-in backend "utilizes Supabase's open-source foundation". So the database behind your app, the logins and the file storage are Supabase, and the storage limits you are running into are Supabase's limits. What you do not get is the Supabase dashboard, which is where most published advice tells you to go. That gap is the whole reason this is hard.

What your app is actually storing

Supabase includes 1 GB of storage on its Free plan and 100 GB on Pro, and charges Pro usage beyond that at $0.0213 per GB per month. One gigabyte sounds generous until you look at what a prototype tends to put in it. Photos straight off a phone are three to eight megabytes each. A profile-picture feature that keeps the original upload as well as a resized copy stores both. Anything that generates images, exports PDFs or accepts document uploads fills a gigabyte in a few hundred records.

Storage is also separate from your database size. A table of ten thousand rows is small. Ten thousand uploaded receipts attached to those rows is not. When an app that worked for weeks suddenly stops accepting uploads, it is almost always the files rather than the data.

Lovable's docs do not publish a file-size cap or a storage quota of their own, and backend usage is drawn from the same credit balance as building the app. So a storage problem can first show up as credits going down faster than you expected, rather than as anything that names storage.

Why usage stays high after you delete

Here is the part that wastes people days. Supabase keeps a record of every stored file as a row in a table called storage.objects, and keeps the file itself somewhere else. Deleting the row does not delete the file. Supabase's own troubleshooting page is blunt about it: removing objects by running SQL against the storage tables means "deleting database rows in this manner does not remove the corresponding physical files". The result is an orphaned object, invisible in your app, still counted in your quota.

This is a much likelier mistake in an AI-built app than in a hand-written one, and not because the tool is careless. If you ask an assistant to clear out old uploads, the shortest correct-looking answer is a delete from storage.objects statement. It runs, the rows disappear, the app stops showing the files, and every visible signal says it worked. Only the number that matters does not move.

Files have to be removed through the storage interface rather than the table, which in code is a call shaped like storage.from('bucket').remove([...]). The fix for files already orphaned is the same call against the paths that are left, which means you first need a list of what is genuinely there. That is the point where not having the dashboard starts to hurt, and where it is worth getting someone to look at the project rather than prompting at it.

Why the restriction does not lift the moment you clear space

Even when you delete correctly, the wall can stay up, and this one is not a bug. Supabase measures the quota as an average over the billing period rather than as a reading taken right now. Its documentation states that reducing storage late in the cycle "may not immediately clear a restriction until the next billing cycle begins".

So three weeks of sitting over the limit still counts for those three weeks. If you are on the Free plan, or on a paid plan with the spend cap on, Supabase sends a notice to the billing address and puts the project into a grace period instead of charging for the overage. Working out what that means for your project is a billing question, not an engineering one, and the honest answer is sometimes to pay for a month rather than spend a week optimising.

What to do, in order

  1. Find out whether it is files or data. If uploads fail but the rest of the app is fine, it is storage.
  2. Stop storing what you do not need. Resize images before upload instead of after, and keep one copy rather than the original and a thumbnail.
  3. Delete through the storage interface, never with SQL against storage.objects. Anything already deleted that way is still occupying space.
  4. Check the billing period before concluding the deletion failed. The average may not catch up until next cycle.
  5. Decide whether a paid month is cheaper than the engineering time. Often it is.

If you are hitting this wall, you are usually close to a second one. A prototype that accepts uploads from strangers also needs rules about who can read those files, which is the same problem as row-level security on your tables, and it needs its keys kept off the browser, which is where service role keys go wrong. The upload feature is often the first place all three meet.

This is also the question that makes people ask whether to move onto their own Supabase project, where the dashboard and the usage breakdown are yours. It is a reasonable move, and a bigger one than it looks: Lovable's docs note that moving the Postgres database alone "does not move authentication, storage, realtime, or Edge Functions", and that database contents and uploaded files have to be exported separately from the code. We have written up what moving off Lovable Cloud to your own Supabase actually involves, and the seven things we check before an AI-built app meets real users covers the rest of the list.

Quotas and prices change. The figures here were taken from Supabase's and Lovable's own documentation in November 2026, and both are worth re-reading before you make a decision based on them. If you would rather hand the whole thing over, our Lovable work starts with reading the project before changing anything.

Let's build it

Want help putting this into practice?

Tell us what you are building and where you are stuck. We will reply with questions, a suggested approach and next steps.