Supabase Storage

Supabase Storage manages file buckets and their access layer inside a Supabase project. It is distinct from the broader Supabase platform and does not replace an application-specific upload experience or media pipeline.⁶⁷

For: Supabase applications that want file access rules to share project identity and Postgres policy context

• The application already uses Supabase Auth and its file rules map cleanly to RLS.
• Storage must remain portable from the rest of the application backend.
• The workload needs storage controls or regions outside the current Supabase offering.

• Integrated access controlStorage metadata can be governed with Postgres row-level security and Supabase Auth context.⁶⁷
• Project-level cohesionFiles, policies, database records, and application identity can share one managed project boundary.⁶⁷
• Application-facing APIsSupabase documents SDK and API workflows for buckets, objects, and signed access.⁶⁷

Storage cost is part of Supabase's plan and product usage model, with stored volume, egress, transformations, and plan quotas requiring a current project-level estimate.⁸

Primary meters

Storage, egress, and optional image transformation usage⁸

Architecture boundary

Storage policy and billing are attached to the broader Supabase project⁸