
You've got two buckets connected. Maybe one is your main storage and the other is a copy at a different provider. Keeping them matched by hand gets old fast.
Sync does that part for you. A sync job mirrors files between two buckets you've already connected, in the direction you choose, on a schedule or whenever you click a button.
It lives under Settings, then Sync. Here's how to set one up.
The Bucket replication section on the Sync page reads Mirror files between two S3-compatible buckets with push, pull, or two-way sync. You pick a source, a destination, and which way changes should flow.
Sync copies files. It reads a file from one bucket and writes it to the other, and the original stays where it was. Files are matched by path, so photos/2026/beach.jpg on one side lines up with photos/2026/beach.jpg on the other.
This is a different job from backup. Backup keeps a second copy in a vault file.rocks hosts for you. Sync works between two buckets you connected yourself.
You need at least two connected buckets. If you only have one, connect another first. There are guides for Amazon S3, Cloudflare R2, Backblaze B2, and Wasabi.
Until you have two, Replicate between buckets stays greyed out. There's no message saying why, so check your bucket count first.
Sign in at file.rocks. Open Settings, then Sync (/settings/sync).
The easy path is Replicate between buckets in the Bucket replication section. It opens Create Sync Job with your first two buckets filled in as source and destination, plus a name built from both.
You can also click New Sync Job under Sync Jobs. If you go that way, pick your Source and Destination from the dropdowns on purpose, even if the right bucket already looks selected.
Give the job a Job name you'll recognize later. Check Source and Destination, then set the direction, schedule, and conflict rule covered below.
Click Create. You'll see Sync job created, and the job shows up under Sync Jobs.
Source folder prefix (optional) and Destination folder prefix (optional) limit a job to one folder, like folder/subfolder. Leave them blank to sync the whole bucket.
The two prefixes don't have to match. You could sync clients/ in one bucket into archive/clients/ in the other.
Need a folder to point at first? That's how to create a folder in your own bucket.
Sync direction has three options. Two-way is the default.
Push mirrors your source to your destination, so changes on the source show up on the destination. Use it when one bucket is the main copy and the other should follow it.
Pull goes the other way. It mirrors your destination back to your source, which is handy for bringing files from the other bucket into yours.
Two-way keeps both sides matched. In the app's words, Changes on either side propagate. New files on either bucket get copied across.
Under the options, a short line spells out which way changes will flow for the buckets you picked. Give it a quick read before you click Create.
Schedule starts on Manual only, which means the job runs when you tell it to. The other choices are Every 15 minutes, Every 30 minutes, Every hour, Every 6 hours, and Daily at midnight.
Choose carefully here. Once a job exists, you can't change its direction or schedule.
If you want something different later, create a new job. The trash icon on the old job's card removes it right away. It removes the job, not your files.
A conflict is when the same file is on both sides but the two copies don't match. Conflict resolution decides what happens then.
Newest wins is the default, so the copy changed most recently is kept. Source wins always keeps the source copy. Destination wins always keeps the destination copy. Skip conflicts leaves both files alone and counts them as skipped.
This setting matters for one-way jobs too. A Push job with Destination wins won't overwrite files already on the destination, so only new files get copied.
It's also the one setting you can change after the job exists. There's a Conflict resolution dropdown right on the job card.
Click Run now on the job card to start a pass. When it's done, you'll get a quick summary of what changed.
The card shows the job's status and when it last ran. Click History to see recent runs, with file counts and size for each one.
If a run comes back Partial or Failed, the card shows the last error in red. That's the first place to look.
Does Sync replace Backup? No. Sync mirrors between two buckets you connect. Backup keeps a copy in a hosted vault.
Can I sync just one folder? Yes. Set a source folder prefix, a destination folder prefix, or both.
How often does it run? As often as your schedule says. Leave it on Manual only and it runs only when you click Run now.
Can I edit a job after creating it? Only the conflict rule. For a different direction or schedule, create a new job.
Pick two buckets, pick a direction, and let Sync keep them matched.
Want a hosted second copy instead? That's how to enable backup for your own bucket.