Free plan limit?

[dmishkan]

So it says on my free plan that I have exceeded the limits (specifically, I have exceeded the storage limitations) for the current billing cycle and that I have a grace period until the end of the month. So I went ahead and deleted almost everything from my storage buckets, waited almost 24 hours, but it still shows that I have exceeded the limits and the storage used still shows the same exceeded number from before I made all of those deletions.

What is going on here? Does it just take more time to update? Or do I have to wait until the start of the next billing cycle in order to see that I'm not going over.

[GaryAustin1]

Did you delete with the Storage UI or Storage API commands?
If you deleted from storage.objects with SQL then you have orphaned the file data in s3.

I've not seen anything consistent on when it resets for a valid delete. Could be the next billing period.

[dmishkan]

I deleted with the Storage UI

[guomengtao]

Hi dmishkan,

Sorry to hear your storage usage still isn’t updating after deleting files—that must be really frustrating, especially when you’re trying to get back under the Free plan limit. Let’s break down why this might be happening (building on Gary’s note about orphaned data) and walk through actionable steps to fix it:

1. First: Check if you have "orphaned data" (the #1 cause of stuck usage)

As Gary mentioned, deleting files directly via SQL (e.g., DELETE FROM storage.objects) only removes entries from Supabase’s metadata table—not the actual file data stored in S3 (Supabase’s underlying storage layer). This means the "storage used" number stays high because the files are still sitting in S3, even if they don’t show up in your bucket anymore.

To confirm:

• Go to your Supabase Dashboard → Storage → Open your bucket.
  • If the files you deleted are still listed here: Your deletion didn’t work (or you used the wrong method).
  • If the files are gone but usage is still high: You likely have orphaned data from a SQL delete.

2. Fix: Delete files the "right way" (to clear S3 data)

To make sure S3 deletes the actual files (and your usage updates), use Supabase’s official tools instead of SQL:

Option A: Delete via the Storage UI (simple for small batches)

1. Go to Supabase Dashboard → Storage → Select your bucket.
2. Check the boxes next to the files/folders you want to remove.
3. Click the trash icon (top-right) → Confirm deletion.

Option B: Delete via the Storage API (better for large batches)

If you have lots of files, use the API to bulk-delete (avoids UI lag). Replace the placeholders with your project details:

curl -X POST 'https://<YOUR_PROJECT_ID>.supabase.co/storage/v1/bucket/<YOUR_BUCKET_NAME>/delete' \
  -H 'apikey: <YOUR_ANON_PUBLIC_KEY>' \
  -H 'Authorization: Bearer <YOUR_ANON_PUBLIC_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
    "prefixes": ["path/to/folder1", "path/to/file2.jpg"] // List files/folders to delete
  }'

Find your PROJECT_ID and ANON_PUBLIC_KEY in Supabase Dashboard → Settings → API.

3. When will the storage usage update?

After deleting via UI/API:

• Typically: Usage drops within 1–4 hours (Supabase syncs S3 data to the dashboard regularly).
• In rare cases: Up to 24 hours (due to S3 latency or dashboard caching).

If it’s been >24 hours:

• Clear your browser cache (the dashboard sometimes caches old usage data).
• Refresh the Storage page—look for the "Storage Used" number at the top (it should now reflect your deletions).

4. If it still doesn’t update: Check for hidden files + escalate to support

Sometimes hidden files (e.g., old backups, partial uploads) take up space without showing in the bucket. To check:

1. Go to Supabase Dashboard → Storage → Click the 3 dots next to your bucket → Select Inspect Bucket.
2. Compare "Total Size" to the sum of visible files—if "Total Size" is higher, hidden files are the issue.

If this happens (or usage still sticks):

• Open a Supabase Support ticket (Dashboard → Support → Open Ticket).
• Include:
  • Your Project ID (Settings → General).
  • A screenshot of the Storage page (showing "Storage Used" and your empty bucket).
  • A note that you deleted via UI/API (not SQL) and waited 24+ hours.

Supabase’s team can manually trigger an S3 sync to clear stuck data—this usually fixes the issue quickly.

5. Quick note on your grace period

The "grace period until end of month" means your storage won’t be disabled until then—you don’t need to wait for the next billing cycle. Once you get usage under the limit (via correct deletions), the "over limit" warning will disappear automatically.

Let me know if you hit snags with the UI/API delete, or if usage still doesn’t update after trying this!

Best regards,
Tom

[dhqnush]

Hi @guomengtao , unfortunately I didnt get to clearing my storage before the grace period ended , now im unable to access my storage buckets via ui and script as well , is there anyway to proceed without upgrading to pro plan . I will be migrating this project to a server that we already have later.

[Bruh-Codes]

Hi @guomengtao I have optimized and cached my db queries and even fetching only needed data. Just to confirm I want to stay on free now since my app just went live. Will the egression reset once the grace period ends?

[guomengtao]

Hi @Bruh-Codes,
Regarding egress reset for the Supabase Free Plan, the official rule is: Egress limits automatically reset at the start of each billing cycle, not when the grace period ends.
First, confirm your billing cycle: Log into the Supabase Dashboard → Navigate to the "Billing" page. Here, you’ll see the start and end dates of your "Current Billing Cycle" (typically defaulting to "1st day of the month to last day of the month", though some accounts may align with the registration date).
The grace period only prevents immediate storage service disruption after exceeding limits—it doesn’t impact egress reset logic. For example, if your grace period ends in late May and your billing cycle runs May 1–May 31, your egress will automatically revert to the Free Plan’s limit (2GB/month, per Supabase’s rules as of May 2024) on June 1 (the next cycle’s start).
If you’re concerned about egress overages, monitor your current cycle’s usage in real time via "Billing → Usage". This helps avoid unexpected overages from sudden traffic near the cycle’s end.
If egress doesn’t reset after the cycle switches, submit a support ticket via the Dashboard’s "Support" tab. Include your Project ID and a screenshot of the "Usage" page—Supabase’s team will assist with verification.

[Bruh-Codes]

Thank you for the help. My reset is on the 9th of Sep. And grace period ends on 1st of Oct. I will reach out to support if anything goes bad.

[dmishkan]

Hey @guomengtao So what ended up happening to me is that I ended up getting restricted when the month ended (even though I cleared all of my storage) but I read that this is because Supabase doesn't fully clear everything until the next billing cycle. So I waited until the next billing cycle (today) and I'm STILL restricted. And this time, it even shows that I'm within all of the limits. What's going on? Is this account just permanently restricted now? Can you help?

[Bruh-Codes]

did your database billing cycle reset before this happending?

[guomengtao]

Hi @dmishkan,

I'm sorry to hear you're still facing restrictions even after the billing cycle reset—this must be really frustrating! Let's troubleshoot this step by step:

1. Check for lingering restrictions
   The first thing to verify is whether the restriction is purely visual or actually affecting functionality. Try performing a basic action in your project (like uploading a small file to storage or querying your database) to see if it's working as expected. Sometimes the UI can show outdated restriction messages even after limits are normalized.

2. Clear dashboard cache
   The restriction message might be stuck in cache:

   • Clear your browser cache completely
   • Open the Supabase dashboard in an incognito/private window
   • Check if the restriction warning still appears

3. Verify storage metrics
   Double-check that all storage metrics are indeed within limits:

   • Go to Storage → Overview
   • Confirm "Total Storage Used" is under the free plan limit (500MB)
   • Check for any unexpected buckets or files that might have been recreated

4. Contact support directly
   Since the billing cycle has reset and your metrics show you're within limits but restrictions persist, this requires Supabase's team to investigate.

   When contacting support (via Dashboard → Support → Open Ticket), include:

   • Your Project ID (from Settings → General)
   • Screenshots showing your current usage metrics (proving you're within limits)
   • Screenshots of the restriction message
   • A brief timeline of events (when you deleted files, when billing cycle reset, etc.)

Supabase support can manually check the status of your account restrictions and should be able to resolve this quickly. This isn't a permanent restriction—just a system synchronization issue that needs manual intervention.

Let me know if you need help with any of these steps!

[Bruh-Codes]

@guomengtao my database just reset today which is fine but I am still getting this grace period warning. Does it mean no matter what I have to upgrade?

[guomengtao]

Hey there! First, no need to jump to upgrading right away—let’s break down why that grace period warning is still popping up even after your database reset.

Mostly, the warning ties to your account’s plan status (like a free trial or expired subscription) rather than the database’s data itself. Resetting the database only clears its content, not the countdown for your plan’s grace period. Here’s what you can do step by step:

1. Check the warning details first—does it say something like “trial ending in X days” or “storage limit exceeded”? That’ll tell you the real cause.
2. Head to your database provider’s dashboard (e.g., the admin panel) to confirm your current plan: Is it still active? Has it expired?
3. If the plan is valid and the warning is vague, it might just be a system delay—wait 1-2 hours, refresh the page, or restart the service.

If none of this works, reach out to the support team with your account ID, database name, and a screenshot of the warning. They can fix it directly or confirm if upgrading is actually needed. You’ve got this!