Storage

What can be cloned

Storage cloning is optional. When selected, SupaClone can clone:

• Bucket configuration.
• Public/private bucket state.
• File size limits and allowed MIME types when available.
• Storage files for snapshot clones.
• Policies on storage.objects and storage.buckets.

Bucket behavior

If a bucket does not exist on the target, SupaClone creates it. If it already exists, SupaClone updates its configuration after confirming the target bucket is empty.

For public buckets, SupaClone creates the bucket conservatively and finalizes public access after files and policies have been copied.

File behavior

Storage files are copied in snapshot mode. Structure-only clones copy bucket and policy configuration without copying object contents.

SupaClone lists objects recursively, downloads from the source, uploads to the target, and verifies target objects using available metadata such as size and checksum values.

Policy behavior

SupaClone recreates policies on:

• storage.objects
• storage.buckets

The clone report also calls out risky policy patterns, such as public roles or write policies without WITH CHECK.

Limitations

Storage cloning is not a merge tool. The target bucket must be empty before files are copied.

Very large buckets may be limited by runtime, bandwidth, or Supabase API behavior. For large production buckets, run a smaller staging clone first and verify performance before copying everything.