How to Back Up a Mac Without Time Machine

Time Machine is the default answer to "how do I back up my Mac" for a reason. It ships with macOS, runs hourly, integrates with Migration Assistant, and handles APFS snapshots cleanly. For most people, it is the right answer.

But "most people" is not "everyone." If you are managing a fleet of mixed-OS machines, working under strict compliance rules, or have simply hit one too many sparsebundle errors, you may want a different setup. This guide covers every realistic alternative, what each one is genuinely good at, and what you give up by leaving Time Machine behind.

It also covers something most articles skip: the hybrid setups that quietly outperform any single tool, including Time Machine alone.

Why You Might Want to Back Up Without Time Machine

Before we look at tools, it is worth being honest about why you might be in this situation. The reason matters, because some alternatives solve only some of the problems.

Locked-down or managed environments (MDM)

In MDM-managed corporate or education fleets, Time Machine is often disabled, restricted to approved destinations, or simply unsupported by the IT policy. If your Mac is enrolled in Jamf, Kandji, Mosyle, or Intune, the choice may not be yours to make. In those environments, you typically need either a sanctioned cloud backup tool or an approved enterprise solution.

Multi-platform consistency (Mac, Linux, Windows fleets)

If you are responsible for backing up a mix of Macs, Linux servers, and Windows workstations, running three different backup systems is painful. A single cross-platform tool like Restic, Borg, or Arq lets you use the same restore workflow, the same monitoring, and the same destination across every machine. That operational simplicity often beats Time Machine's polish.

Specific compliance or chain-of-custody requirements

Time Machine backups are essentially opaque APFS structures. If you need versioned, hash-verified, immutable archives — say, for legal hold, HIPAA, or anything involving auditors — you want a tool with explicit content-addressable storage and append-only modes. Restic and Borg both support this; Time Machine does not.

APFS sparsebundle frustrations

Network Time Machine backups create a sparsebundle, a bundle of small "band" files that grows as the backup grows. Sparsebundles can become corrupt if a backup is interrupted at exactly the wrong moment, and there is no first-party repair tool. Most users never hit this, but those who do tend to never trust network Time Machine again. If that is you, an alternative tool that uses regular files is more comforting.

The Realistic Alternatives

There are a lot of "Mac backup" tools out there. Many of them are essentially front-ends for the same underlying primitives. The list below covers the tools that are genuinely distinct and actively maintained.

Carbon Copy Cloner (CCC)

CCC is the closest thing to a complete Time Machine replacement. It creates bootable clones, runs scheduled incremental copies, takes APFS snapshots, and keeps a configurable snapshot history on the destination. The UI is polished, the documentation is excellent, and the developer (Bombich) has been around since the early Mac OS X days.

Where CCC genuinely shines is the bootable clone. If your Mac dies, you can boot the clone on another Mac (within Apple's signing rules) and keep working. Time Machine cannot do that.

Trade-off: $40 one-time, no native cloud destination — you point it at a local disk or a mounted network share. There is no Finder timeline UI for browsing old versions; you use CCC's own snapshot navigator.

SuperDuper!

SuperDuper! is the original bootable-clone tool for the Mac and is still actively maintained. It is simpler than CCC, with fewer scheduling and snapshot features, but the simplicity is the point. Many long-time Mac users prefer it precisely because it does one thing extremely well.

Trade-off: The free version only does full clones; scheduling and incremental "Smart Update" copies require the $28 license. No cloud destinations, no APFS snapshot management beyond what macOS does natively.

Arq Backup

Arq has been the cross-cloud Mac backup tool for over a decade. It backs up to S3, Backblaze B2, Wasabi, Google Cloud Storage, Azure, your own SFTP server, or a local drive. Backups are encrypted client-side with your own key, deduplicated, and versioned indefinitely.

If you want "Time Machine, but to any cloud you choose, with end-to-end encryption you control" — Arq is the answer. See our deeper comparison on the Arq alternative page.

Trade-off: $50/year for one Mac, plus whatever the cloud destination charges. Restores require running the Arq app — no Migration Assistant integration. The UI is functional but not particularly elegant.

Backblaze Personal Backup

Backblaze is the simplest "set it and forget it" cloud backup for the Mac. $99/year per computer, unlimited storage, runs in the background, no thinking required. It is excellent at what it does.

What it is not is a complete system backup. Backblaze excludes the macOS system, Applications, most of /Library, and various cache directories. You are backing up your data, not your Mac. Version history is 30 days by default, extendable for an extra fee.

Compare in detail on our Backblaze alternative page.

Trade-off: Per-device pricing gets expensive for households with multiple Macs. Initial backups can take weeks on slower upload connections. Restores are by web download or paid drive shipment.

rsync — the Unix workhorse

If you are a developer and you just want a one-liner that copies your home folder to a NAS or external drive, rsync is hard to beat. Free, scriptable, and battle-tested.

The catch on macOS: you need the right flags to preserve extended attributes, ACLs, and resource forks. The bundled BSD rsync is too old for some of this; most users install rsync via Homebrew and use flags like -aHAX --xattrs. Even then, rsync is a copy tool, not a backup tool — there is no built-in versioning, no deduplication, no encryption, no restore browser.

Trade-off: You are now your own backup system. That is fine until the day you need to restore something from three weeks ago and discover you only kept the latest copy.

Borg / BorgBackup

Borg is a deduplicated, encrypted, compressed snapshot backup tool, originally from the Linux world but fully usable on macOS via Homebrew. Each backup is a "snapshot" in a "repository," and Borg deduplicates aggressively across snapshots — so 30 daily snapshots of a 500 GB Mac take far less than 15 TB.

Borg is push-based to a remote SSH destination (typically a Borg-aware server like rsync.net or your own VPS). It is the favourite of sysadmins who want a single backup tool across Linux servers and Macs.

Trade-off: Command-line only on macOS. No GUI restore browser. You need to maintain the destination yourself or pay for a Borg-compatible host.

Restic

Restic is the modern, Go-based equivalent of Borg, with first-class support for cloud destinations (S3, B2, Azure, GCS, Swift, plus REST and SFTP). Same model: deduplicated, encrypted, versioned snapshots in a content-addressable repository.

Restic is what a lot of people reach for in 2026 if they want a single tool that runs on every OS and backs up to every cloud. It is also what underpins several commercial backup products.

Trade-off: CLI-only. Restores can be slow if you have millions of small files because the index has to be loaded. Like Borg, the workflow assumes you are comfortable with a terminal.

Manual cloud sync (iCloud Drive, Dropbox, Google Drive, OneDrive)

Cloud sync is not backup. We have to keep saying this because people keep treating it as backup, and then they discover that "sync" means "if you delete it locally, it deletes in the cloud" and "if ransomware encrypts your files, the encrypted versions sync up."

That said, iCloud Drive, Dropbox, and Google Drive all have version history and undelete features that look like backup for individual files. Dropbox keeps 30 days (180 with Plus), Google Drive keeps 30 days, iCloud Drive keeps 30 days for most file types. Compared on our iCloud comparison page and iCloud alternative page.

Trade-off: No system files, no apps, no settings, no Photos library (unless you use iCloud Photos), no version history beyond ~30 days, and the sync semantics are dangerous if you do not understand them.

Comparing the Alternatives at a Glance

Here is how the main options stack up on the dimensions that actually matter:

Tool	System backup	Versioning	Encryption	Cloud destinations	Restore via Migration Assistant	Cost
Time Machine	Yes	Hourly / daily / weekly	Optional (AES-XTS)	Via SMB share (e.g. Capsule Backup)	Yes (native)	Free + storage
Carbon Copy Cloner	Yes (bootable)	APFS snapshots	Via APFS / FileVault	No (local / SMB only)	Indirect (boot the clone)	$40 one-time
SuperDuper!	Yes (bootable)	Limited	Via APFS / FileVault	No	Indirect (boot the clone)	$28 one-time
Arq	Files only	Indefinite	Yes, client-side	S3, B2, Wasabi, GCS, Azure, SFTP	No	$50/year + storage
Backblaze Personal	Files only	30 days (extendable)	Yes (optional private key)	Backblaze only	No	$99/year/Mac
rsync	Possible, fragile	None	None (use SSH)	Anywhere with SSH	No	Free
Borg	Files only	Indefinite, dedup	Yes	SSH targets	No	Free + host
Restic	Files only	Indefinite, dedup	Yes	S3, B2, Azure, GCS, REST, SFTP	No	Free + storage

What You Give Up When You Skip Time Machine

It is easy to focus on what alternatives offer that Time Machine does not. The harder question is what you quietly lose.

No Migration Assistant integration

When you set up a new Mac, Migration Assistant offers to pull from a Time Machine backup. It restores everything: apps, settings, keychain entries, system preferences, network locations, mail accounts, in roughly the right order. No third-party tool plugs into this flow. With Arq, Restic, or Borg you restore to a folder and then manually copy files into your new Mac. It works, but it is hours of extra work.

No native APFS local snapshots tie-in

When Time Machine cannot reach its destination — you are away from your home network, your laptop has not seen the cloud share — it still takes hourly APFS snapshots locally and keeps them for 24 hours. So even when you are "off backup," you can still roll back. Most third-party tools do not integrate with this. CCC is the exception.

No Finder timeline browsing

The Time Machine timeline UI, where you fly back through stacked Finder windows to find an older version of a file, is genuinely useful. Most third-party tools have a list view at best. CCC has a passable snapshot browser; the rest expect you to know what you are looking for.

No automatic hourly cadence (depends on tool)

Time Machine just runs every hour. Most third-party tools require you to configure scheduling — and "every hour, on AC power, only when on a trusted network" is not always trivial to express. Arq and CCC handle this well. rsync and Restic require you to write a launchd plist or rely on a cron job.

Settings and Library nuances

macOS scatters important state in non-obvious places: ~/Library/Application Support, ~/Library/Containers, ~/Library/Group Containers, the keychain in ~/Library/Keychains, mail in ~/Library/Mail. Time Machine knows to back all of this up. A naive rsync of ~ with default exclusions can miss critical files. Always test your restore.

Decision Tree: Which Tool When

If you are still not sure which way to go, work through these questions in order:

• Do you need a complete Mac that boots if your current one dies? Use Carbon Copy Cloner or SuperDuper! to a local SSD.
• Do you want zero-thought offsite backup of your data files? Use Backblaze Personal Backup, or pair Time Machine with a cloud SMB destination like Capsule Backup.
• Do you manage multiple OSes and want one tool? Use Restic (or Borg if you prefer the older, more proven codebase).
• Do you need versioned, encrypted backups to a specific cloud you already use? Use Arq.
• Are you in a locked-down corporate environment? Use whatever IT has approved, and supplement it with your own offsite for personal files if policy allows.
• Are you a developer who just wants their ~/code on a NAS? rsync via launchd is fine — but back up the rest of your Mac with something else.

Why Time Machine Plus a Cloud Destination Is Still the Default Recommendation

Here is the honest answer most "alternatives" articles do not give you: for the average Mac user, Time Machine writing to a cloud SMB destination is still the best balance of simplicity, reliability, and restore experience.

You get the native Migration Assistant integration. You get the hourly cadence, the Finder timeline, the encryption-at-rest, and the APFS snapshot tie-in. You get the offsite copy. You do not have to learn a new tool, write launchd plists, or manage a repository. The setup is one Finder shortcut and one System Settings checkbox — see our walkthrough on setting up Time Machine.

The reason people end up looking for alternatives is almost always one of three things:

• They tried network Time Machine to a cheap NAS, hit sparsebundle errors, and lost trust in the whole approach.
• They never had a reliable destination at all and wanted "real" cloud backup.
• They have specific constraints (multi-OS, MDM, compliance) that Time Machine genuinely cannot solve.

For the first two, the fix is not abandoning Time Machine — it is giving it a destination that actually works. For the third, the alternatives above are all valid.

Combining Approaches: The Setup Most Pros Use

The strongest backup setup is not "pick the best tool." It is layering, because any single tool eventually fails, and the cost of backups is low compared to the cost of data loss.

A common pro setup looks like this:

• Time Machine to cloud SMB — your hourly, automatic, offsite, restorable-via-Migration-Assistant baseline.
• Carbon Copy Cloner weekly to a local SSD — your bootable, take-it-and-run insurance against the cloud being unreachable.
• iCloud Drive or Dropbox for active project folders — fast cross-device sync, not backup, but useful as a third copy of work-in-progress.
• Optionally, Arq or Restic to a second cloud region — only if you have compliance reasons or genuinely large data and want a third independent copy.

This follows the well-known "3-2-1" rule: three copies of your data, on two different media, with at least one offsite. With the setup above, you have four copies on three media with two offsite. That is the level of redundancy that lets you sleep through a flood, a theft, or a ransomware event.

For more on the security side of this — encryption at rest, in transit, and key handling — see our security overview.

The Bottom Line

You can absolutely back up a Mac without Time Machine. CCC, Arq, Restic, Borg, and Backblaze are all credible tools used by serious people every day. But "without Time Machine" is rarely the question worth asking. The question is "what backup setup would actually save me on the worst day of my year?" and the answer is almost always "more than one copy, in more than one place, with at least one of them offsite and automatic."

If you are skipping Time Machine because of a destination problem, fix the destination. If you are skipping it because of a real constraint, pick the alternative that matches your constraint and pair it with at least one other copy. And whichever path you choose, do the one thing most people skip: test a restore. A backup you have never restored from is a hope, not a backup.