Supabase Egress & Storage Cost Calculator (2026)

Supabase Egress Architecture: Storage CDN Offloading & $0.09/GB Bill Shock Prevention

Supabase includes generous monthly bandwidth quotas (5 GB free on the Free Tier, 250 GB included on the $25/mo Pro Tier), but excess bandwidth egress is billed at $0.09 per GB. For media-rich web applications, AI generative image storage backends, and public file download portals, raw database and storage egress fees can rapidly eclipse database compute expenses unless fronted with an external edge cache like Cloudflare.

Production Pipeline: Cloudflare Worker Reverse Proxy for Supabase Storage

Deploying a Cloudflare Worker in front of the Supabase Storage endpoint caches public assets globally with zero egress fees hitting your Supabase account:

// Cloudflare Worker: Supabase Storage CDN Cache Proxy
export default {
  async fetch(request: Request): Promise<Response> {
    const url = new URL(request.url);
    const SUPABASE_ORIGIN = 'https://xyzcompany.supabase.co';
    
    // Construct target URL to Supabase Storage public bucket
    const targetUrl = `${SUPABASE_ORIGIN}${url.pathname}${url.search}`;
    
    // Check Cloudflare Edge Cache first
    const cache = caches.default;
    let response = await cache.match(request);
    
    if (!response) {
      response = await fetch(targetUrl, {
        headers: request.headers,
      });
      
      // Cache successful image and static asset responses for 30 days
      if (response.status === 200) {
        const newHeaders = new Headers(response.headers);
        newHeaders.set('Cache-Control', 'public, max-age=2592000, immutable');
        response = new Response(response.body, { ...response, headers: newHeaders });
        await cache.put(request, response.clone());
      }
    }
    
    return response;
  }
};

Production Governance & Egress Guardrail Checklist

• Enable Spend Caps on Pro Plan: By default, Pro plans allow overages. Enable the Spend Cap in the Supabase billing settings to prevent unauthorized egress runaway if an image goes viral.
• Avoid SELECT * on Large Bytea Columns: Storing base64 images or PDF binary blobs directly inside PostgreSQL tables burns database egress on routine queries. Always store media in object storage.
• Image Resizing Transformations: Utilize Supabase's built-in image transformation engine (`/render/image/public/bucket/pic.jpg?width=400`) to send thumbnail bytes instead of original 10MB camera uploads.