Why did my transfer say Completed but nothing changed at the destination?

Q: Why did my transfer say Completed but nothing changed at the destination?

Two common reasons: - Dry run was on. A dry run goes through everything and completes without changing any file. Check the transfer's log — it lists what would have happened. Set it up again with Dry run (preview only) off. - Everything already matched. Copy and the syncs skip files that are already identical, so a transfer between two places that are already in step finishes quickly with little or nothing to send. Also make sure you're looking at the destination folder you actually chose — the full path is in the transfer's status card. Related: What is a dry run? · Why is a repeat run faster?

Short answer: Usually Dry run was on (it completes without changing anything) or everything already matched, so nothing needed sending. Check the log and the full destination path in the transfer's status card.

Two common reasons:

Dry run was on. A dry run goes through everything and completes without changing any file. Check the transfer's log — it lists what would have happened. Set it up again with Dry run (preview only) off.
Everything already matched. Copy and the syncs skip files that are already identical, so a transfer between two places that are already in step finishes quickly with little or nothing to send.

Also make sure you're looking at the destination folder you actually chose — the full path is in the transfer's status card.

Last reviewed October 1, 2026

Also available as Markdown and JSON.

Why did my transfer say Completed but nothing changed at the destination?

Related questions