Skip to content

Supabase Storage: Public Bucket

Glossary

A public bucket in Supabase Storage serves every file by its address, without sign-in and without checking who is asking. For product images or logos that is intended. For invoices, IDs or user uploads it is a data leak: whoever knows or guesses the address has the file. Private buckets, by contrast, only serve files through access rules or signed, time-limited links.

Supabase Storage keeps files in buckets. If a bucket is public, its files are reachable at a fixed address (/storage/v1/object/public/<bucket>/…). That is convenient, which is exactly why generators and tutorials like to make buckets public, even when users later upload documents there. In the app both look the same: the image or PDF is displayed.

Keep two questions apart. First: is the bucket public, so every file can be fetched by anyone with its address? Second, for private buckets: are the access rules (policies) on storage.objects bound to the owner, typically via one folder per user ((storage.foldername(name))[1] = auth.uid()::text)? A rule that only checks whether someone is signed in lets every account reach everyone else's files.

Done right means: make buckets private unless there is a reason for public access, serve files through signed URLs and store files under <user-id>/…. The free decivo Scan checks from the outside which buckets of your project are configured as public and whether the buckets your app names itself are served publicly. Only metadata and status are read, never a file. The deep scan checks the access rules themselves inside the repository.

Frequently asked questions

What is a public bucket in Supabase Storage?
When may a Supabase bucket be public?
How do I secure a Supabase Storage bucket?
How do I check whether my buckets are open?

Ready for production-ready software?

Bring your project to a first call — we'll assess it honestly and recommend the right next step.

Book a call

30 minutes, free. You talk to us directly.