Storage
The Storage component copies the buckets and files from your source Supabase project to the target project.
What Is Supabase Storage?
Supabase Storage is a file storage service (images, documents, videos, etc.) integrated into your project. Files are organized into buckets (root folders).
What Is Copied
- Buckets — created with the same settings (public/private, max size, allowed MIME types)
- Files — all files from each bucket
- Folder structure — the directory tree is preserved
- Metadata — MIME type, size
How It Works
- Twins lists all buckets from the source
- For each bucket, creates the bucket on the target (if it does not exist)
- Lists all files in the source bucket
- Downloads each file and re-uploads it to the target
Key Considerations
| Situation | Behavior |
|---|---|
| Existing bucket on the target | Files are added (existing files are not deleted) |
| File with the same name | Overwritten with the source version |
| Public bucket | Recreated as public on the target |
| Private bucket | Recreated as private on the target |
| RLS policies on buckets | Copied via the RLS component (these are policies on the storage.objects table) |
Storage Limits by Plan
Storage cloning is subject to plan limits based on the total size of files in your source project:
| Plan | Storage Limit |
|---|---|
| Free | 200 MB |
| Pro | 3 GB |
| Enterprise | Unlimited |
If the total storage exceeds your plan limit, the Storage toggle is automatically disabled in the clone preview. You can still clone all other components.
The preview shows the total storage size next to the section label (e.g., "Storage (142 MB)").
Volume and Time
Storage cloning can take a long time if you have many files or large files. The preview indicates the number of files per bucket.
Tip: If you do not need files in staging, disable the Storage component to speed up the clone.
Next Steps
- Auth Users — Clone user accounts
- Clone options — Disable storage if needed