Free project storage quota exceeded — unable to delete Storage files (HTTP 402) #51513
Replies: 4 comments 5 replies
|
Short version: there's no self-serve way out of this one. Once a Free org is restricted for exceed_storage_size_quota, the Storage API itself returns 402, and that includes remove() calls and the dashboard's Storage browser. So you can't delete files through the supported path while the restriction is active. To your three questions: Deleting while restricted: not possible through the Storage API. You're right not to touch storage.objects in SQL. The troubleshooting guide is explicit that deleting rows there only removes metadata and leaves the physical files orphaned, still counting toward your quota: |
|
Here is how to resolve the HTTP 402 lock and safely clear storage files without upgrading: 1. Why direct SQL deletion on
|
|
I tried the S3 workaround on a project that was restricted for exceed_storage_size_quota and didn't help. I generated S3 credentials, used AWS CLI, and tested both endpoints mentioned here. Listing objects returns 402 Payment Required. Deleting a known orphaned object also returns 402. |
|
We are facing the same catch-22 on a production CRM project. The Storage Dashboard, Storage API, Edge Function, and S3 endpoint all return HTTP 402 / Support ticket: SU-547804. Supabase's AI support agent has forwarded it to a human teammate. We are requesting temporary Storage deletion access or an administrative cleanup window. A 10-day media retention job is already prepared to prevent recurrence once access is restored. |
Uh oh!
There was an error while loading. Please reload this page.
Hi Supabase community,
I'm using the Free plan for my WebOfWishes project,
web-of-wishes, and my organization has exceeded its storage quota.My storage usage is approximately 2.64 GB against the 1.1 GB quota. My project is now restricted with the error
exceed_storage_size_quota, and Storage API requests return HTTP 402.The Storage dashboard cannot fetch buckets, and clicking Edit bucket → Empty bucket does nothing. I've also tried Incognito mode, but the issue persists.
I deleted all 128 records from my
boyfriends_day_websitestable, but the actual uploaded files remain in Storage. Mysongsbucket contains 316 files, and I would like to remove them to reduce storage usage without upgrading to Pro.The SQL Editor is still accessible, but I understand that deleting rows from
storage.objectsdirectly is not the correct way to remove physical Storage files.I've already submitted a support request (ticket SU-502090).
My questions:
I want to resolve this without losing database data or accidentally affecting other website assets.
Thank you for your help!
All reactions