Restricted free project (exceed_storage_size_quota) — no way to export Storage objects to migrate to self-hosted Supabase

[kumarvishwas2737-cpu]

I want to move off the hosted Free plan onto self-hosted Supabase. The database side was straightforward: Postgres stayed reachable through the pooler, so pg_dump gave me a complete, verified dump.

Storage is where I am stuck. My project is restricted with exceed_storage_size_quota and every path I can find to read my own objects returns HTTP 402:

GET /storage/v1/bucket                  -> 402
GET /storage/v1/object/public/<bucket>/ -> 402
GET /storage/v1/object/list/<bucket>    -> 402
GET /storage/v1/s3                      -> 402   (S3-compatible protocol)

So the restriction blocks reads, not just writes, including the S3-compatible endpoint. That leaves me unable to perform the migration that would take me off hosted Storage permanently and put my usage at zero.

Project ref: eceephkqwyinbvdrzkhg (ap-south-1)

Current Storage usage is roughly 195 MB against the 1 GB Free plan limit, so I am already under quota. I did not delete anything via SQL — every deletion in my codebase uses the Storage API .remove(), so I should not have orphaned objects inflating the number. I already migrated my largest bucket to my own S3 bucket on 6 September and it is empty on Supabase now. The remaining objects are small images and PDFs I am required to retain as records, so deleting them instead of exporting them is not an option.

What I am asking for

1. A read-only window on Storage (a day is plenty) so I can copy my objects out. I am not asking for writes, or for the restriction to be lifted generally.
2. Failing that, is there any supported export route for Storage objects on a restricted project? A signed bulk export, or a backup file I can download?
3. A clarification I could not settle from the docs: Storage size is billed in GB-Hours, so is a restriction expected to persist until the billing cycle ends even once current usage is back under quota? If that is the intended behaviour I will plan around the date. I would just like to know it is expected rather than a stuck flag — because the same restriction also appeared on a brand-new project in the same organization that has never had a single file uploaded to it, which is what makes me think it is org-scoped and latched rather than recomputed.

Happy to be told this is working as designed. Mainly I would like a supported way to get my own files out so I can self-host and stop leaning on the free tier.

Thanks.

[GaryAustin1]

The only options if you did not reduce your storage during the Grace Period so that the daily average is dropping, is to go Pro for a month or ask support for relief. There is no user way to get to storage after the Grace Period ran out.