File transfer, synchronization and backup: choose by task
Sending a file to a phone, matching two folders, and recovering last week’s deleted work are three different goals. Decide whether you need a current copy or recoverable history.
Match the tool to your task
| Task | Tool | Limit | Check first |
|---|---|---|---|
| One-time local-network file and text transfers | LocalSend ↗ | Not an automatic synchronization or version-history backup tool. | Check network permissions and Wi-Fi client isolation. |
| Compare folders and preview synchronization actions | FreeFileSync ↗ | Mirror synchronization may delete extra destination files. | Confirm direction and configure versioning or separate backups. |
| Scheduled encrypted backups and versioned restores | Duplicati ↗ | Restores need a usable backup set, configuration and encryption passphrase. | Restore into a new folder and verify content before expanding the job. |
Before you process real files
- Define the goal: send a copy, synchronize, or restore history.
- Test new, modified and deleted files in a sample folder.
- Preview synchronization and test backup restores into a separate folder.
- Store passphrases, configuration and restore instructions separately from the source device.
Common questions
Does synchronization to another disk count as a backup?
It depends on deletion propagation and version retention. A mirror can copy accidental deletions. Test recovery scenarios rather than assuming a second location retains history.
What should I check after a transfer?
Verify the receiving device, file count, size and actual contents. Compare checksums for important files; a completed transfer does not establish a backup plan.
Sources and scope
This comparison is based on product documentation and our catalog. It is not a benchmark or a claim that every archived package was tested. Check the resource page for the listed version; newer documentation can differ.