Five Approaches to Downloading Supabase Storage Files as a ZIP Explained
Developers working with Supabase Storage face key architectural decisions when building a 'download all' feature, particularly around where the ZIP archive is constructed and whether it is stored for reuse. The five main approaches range from server-side background workers and Edge Functions to browser-based zipping and managed ZIP APIs, each with distinct trade-offs in resource limits, reliability, and infrastructure complexity. Edge Functions on Supabase operate under constraints including 256 MB memory, limited CPU time, and worker lifetimes of up to 400 seconds on paid plans, making them suitable only for bounded, well-tested exports. Browser-based ZIP generation avoids server infrastructure but depends on client resources, CORS configuration, and tab stability throughout the download. Choosing the right method depends on factors such as file count, archive size, connection reliability, and whether the finished archive needs to be reused for subsequent downloads.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in