The original headline is: "Supabase Backups Don't Include Your Storage Files. Here's What Does."

Short summary

Supabase database backups (daily, PITR, or pg_dump) exclude Storage files, which live in a separate S3 backend. Restoring the database restores metadata pointers but not the actual file bytes, causing silent 404s. The author demonstrates using Supabase's S3-compatible endpoint with rclone or AWS CLI to sync storage buckets to external providers, and introduces an open-source CLI tool that bundles both database and file backups together.

• •Supabase backups restore storage.objects metadata but not actual file bytes — files live in separate S3 backend
• •Use Supabase S3-compatible endpoint with rclone or AWS CLI to sync storage to R2/B2/own S3
• •Schedule db dump and file sync together so snapshots describe the same moment; watch egress costs

Generated with AI, which can make mistakes.