Supabase Storage now in Beta

Summary

Supabase released Storage Beta with several functional and architectural improvements three months after its alpha launch. The storage service now supports the Content-Range HTTP header for streaming audio and video, alongside entirely public buckets configured with dashboard safeguards and standard authorization policies. Directory uploads are enabled via the File and Directory entries API, while self-hosted instances can use a new local filesystem backend rather than requiring AWS S3 configuration. To support Node.js without adding polyfills or bundling complexity, the storage server was updated to accept binary data and streams directly. Additionally, the dashboard storage explorer simulates filesystem directories using hidden placeholder files and implements list virtualization.

Takeaways

1. 1

   Buckets in Supabase Storage must be public in their entirety to eliminate ambiguity over exposed objects, while still enforcing Auth Policies for uploads and deletions.

2. 2

   Modifying the storage server to accept binary data allowed the client library to support Node.js streams and binary formats without increasing its 15.8 kb bundle size.

3. 3

   Empty directories in the dashboard storage explorer are simulated by uploading a hidden placeholder file that is removed once an object is uploaded to that path.