Both major operating systems include free backup software. Both are good enough for most people, and both have specific limitations worth knowing before you rely on them.
They're also not equivalent tools, despite being presented as the same thing, so comparing them directly is slightly misleading. Here's what each one actually is.
Time Machine, on macOS
Time Machine takes snapshots of your whole system on a schedule — historically hourly for the past day, daily for the past month, and weekly beyond that, thinning older backups as the drive fills.
What it does well:
Full system restore. You can restore an entire Mac, including the operating system, applications, settings, and files, to a new or wiped machine. Migration Assistant reads Time Machine backups directly, which makes moving to a new Mac genuinely painless.
Browsing back in time. The interface lets you step backward through versions of a folder and pull out the state from a specific date. This is the feature people actually use, and it's excellent for recovering a file you overwrote or a folder you reorganized badly.
It runs itself. Once configured, it requires no attention.
Local snapshots. When the backup drive isn't connected, the system keeps snapshots on the internal drive, so limited recovery is possible even away from the backup disk. These aren't a substitute for real backups — they're on the same drive — but they've saved a lot of people from a bad afternoon.
Where it falls short:
One backup destination at a time is the common setup, though multiple destinations can be configured and used in rotation.
No cloud destination. Time Machine backs up to a local drive or a network location. Off-site requires either physically moving the drive or adding a separate cloud backup service.
Drive formatting matters. The backup drive needs to be formatted for macOS. A drive shared with a Windows machine generally won't work as a Time Machine destination.
Restores of a full system take hours. Fine, but plan for it.
It can be quietly slow to notice problems. If the drive develops errors, you may get a message asking to start a new backup, which discards your history. Read that message rather than clicking through it.
File History, on Windows
File History is a different kind of tool. It backs up files — versions of documents in specified folders — rather than your whole system.
What it does well:
Version history for documents. Restore previous versions of a file from a right-click, or browse back through folder states. Genuinely useful and the core function.
Selective and lightweight. It backs up user folders rather than the entire drive, so it's faster and needs less space.
Simple restore. Finding and restoring a previous version is straightforward.
Where it falls short:
It's not a system backup. File History alone will not restore a broken Windows installation, your applications, or your settings. This is the single most important thing to understand about it. For a full system image, Windows has a separate legacy imaging tool, or you use third-party software.
Default folder coverage is limited. It covers the standard user folders. Anything stored elsewhere — a second drive, a custom location, a game or application storing data outside the user profile — is not included unless you add it. Check the included folder list rather than assuming.
Microsoft's backup strategy has shifted over time, with more emphasis on syncing user folders to cloud storage rather than local file history. Which features are prominent varies by Windows version, and it's worth confirming what's available on your specific build.
Cloud folder sync is not the same as backup. If your setup is syncing your Documents folder to cloud storage and you're treating that as your backup, revisit that — sync propagates deletion.
The honest comparison
| Time Machine | File History | |
|---|---|---|
| Full system restore | Yes | No — needs a separate image tool |
| File version history | Yes | Yes |
| Migrating to a new machine | Excellent | Limited |
| Covers non-standard locations | Broadly, by default | Only what you add |
| Cloud destination | No | No |
| Setup difficulty | Very low | Low |
| Runs unattended | Yes | Yes |
Time Machine is the more complete tool. File History is a good versioning tool that people mistake for a complete backup, which is the main risk with it.
What both share, and what it means
Neither is off-site. Both write to a drive that's probably sitting next to the computer. Fire, flood, or theft takes both. You need a second copy elsewhere regardless of which you use.
Neither is ransomware-proof if the drive stays connected. A permanently attached backup drive is reachable. Unplug it between runs, or add a copy that isn't attached.
Both fail silently. Neither will call you when it stops working. The monthly status check is not optional.
Both back up local files only. Cloud-only documents, email on a provider's server, phone data, and website files are outside their scope entirely.
When to use third-party backup software instead
The built-in tools are enough for a lot of people. Consider third-party software when:
You want a bootable clone. Some tools create an exact copy of your drive that you can boot from directly. If your machine dies mid-project, you plug in the clone and keep working within minutes rather than restoring for hours. Genuinely valuable for anyone whose work has deadlines.
You want cloud and local in one tool. Several backup products handle both destinations from one interface, with one schedule and one restore workflow.
You need multiple destinations or complex rules. Different folders to different places, different retention for different data, backing up to a network drive and a cloud service simultaneously.
You're on Windows and want real system imaging with modern support and reliable restores.
You're backing up a business and need centralized management, reporting, or retention policies.
You want stronger ransomware protection — immutable backups, air-gapped copies, or versioning that can't be overwritten by an attacker.
The general principle: start with the built-in tool because it's free and running today. Add third-party software when you hit a specific limitation, not preemptively.
The setup I'd suggest for each platform
Mac:
- Time Machine to a local external drive, unplugged between weekly runs
- A cloud backup service running continuously for off-site
- Optionally, a bootable clone if downtime is expensive for you
- Annual restore test
Windows:
- File History to a local external drive, with all your file locations explicitly added
- A separate full system image, either the built-in tool or third-party, taken periodically
- A cloud backup service for off-site
- Annual restore test
In both cases the third-party or cloud element is what turns a local versioning tool into a real backup system. The built-in tool handles the everyday case — "I overwrote this document" — extremely well, and that's the case that comes up most often.
The three checks worth doing today
Is it actually on? Open the settings and look at the last successful backup date.
Does it include everything? Compare the included folders against where your files actually live. This is where most people find a gap.
Can you restore? Pull one file back and open it.
Ten minutes, and it's the difference between having backup software installed and having a backup.
Backup features and their names change between operating system versions. Check your system's current documentation for specifics.
Next in this series: How to Choose an External Hard Drive for Backups