Carbon Copy Cloner — Mac download

Where Time Machine keeps versioned snapshots, Carbon Copy Cloner builds a direct, bootable duplicate of your entire disk. The workflow is deliberately simple.

1. Select a source volume — your startup disk, an external project drive, or a specific folder.
2. Choose a destination disk for the clone.
3. Set a schedule. Hourly, daily, weekly — the backup runs automatically in the background.
4. CCC 7 copies everything, creating an exact, bootable clone ready when your main drive isn’t.

Version 7 is a native build for both Intel and Apple Silicon Macs, fully qualified on macOS Golden Gate. The interface stays flat and functional. No wizards, no hidden panels — just a clear map of source, destination, and task status. It remains a straightforward utility for teams who need a disk clone that boots without drama.

Yes, a CCC Clone Really Boots

One question surfaces more than any other: does a clone really boot? Yes. A CCC 7 clone made from an APFS startup volume with the default settings produces a fully bootable external drive. Plug it into any compatible Mac, hold Option at startup, select the clone — the machine starts exactly as the original did, right down to the last preference pane tweak.

People also ask whether CCC replaces Time Machine. It doesn't. The two complement each other. Time Machine gives you hourly snapshots to browse back through. CCC gives you a complete, standalone copy you can work from immediately. Many small teams run both: CCC for a nightly bootable safety net, Time Machine for catching the file you accidentally overwrote at 2 p.m.

Another recurring concern: what happens to files I delete from the source? CCC's default safety net preserves them on the destination until space runs low. You can tighten this behaviour — switch to a strict mirror that removes anything not on the source — but the safe default keeps the deleted stuff around. For most people, that is the right call for the first month.

Launches in Under Two Seconds

CCC 7.1.6 loads quickly. On an Apple Silicon Mac, the window appears in under two seconds; on an older Intel machine, perhaps three. Memory use sits around 120 MB during a backup. The background scheduler, CCC Dashboard, idles near zero CPU when no task runs. During a full clone to a spinning external drive, CPU usage hovers between 4 and 8 percent on an M-series chip — low enough that most people forget it is running.

Stability has been uneventful across months of scheduled nightly tasks. Tasks fire on time. The only interruptions tend to be external: a destination disk that wasn't plugged in, a NAS share that dropped offline. CCC logs these clearly, with a red task badge in the sidebar that you can inspect with a click. The log entries are plain English, not syslog gibberish.

Snapshots on APFS volumes add another layer of quiet protection. CCC can retain multiple dated snapshots on the destination, so you can browse yesterday's version of a folder even after today's clone overwrote it. Browsing snapshots feels fast — mounting one takes a second or two, and the Finder treats it like any other volume.

Boot from Your Clone Before Automating

Start with one manual clone. Don't schedule anything yet. Pick your startup disk as the source, an external SSD as the destination, and let the task run through. Watch the activity log scroll. Once it finishes, reboot from the clone to confirm it boots. That single test eliminates a dozen future unknowns.

After the boot test, set up a simple schedule. A daily task at the end of the workday works well for most solo users. Small teams often prefer a late-evening window — 10 p.m. or 11 p.m. — so backups don't compete with active work. CCC's schedule editor lets you chain multiple time slots; you can set a weekday schedule and a separate, later weekend slot in the same task.

Enable snapshots on the destination early. The checkbox sits in the task's destination options. Set snapshot retention to something manageable — "retain last seven daily snapshots" is a sensible starting point. This gives you a week of fallback points without consuming excessive space.

If you migrate data from an old Mac, consider running a one-off folder-level task instead of a full disk clone. Pick your user folder as the source, an external drive as the destination, and exclude caches and Library/Containers to speed the transfer. CCC handles partial copies with the same engine it uses for full clones.

When Scheduled Tasks Never Start

Scheduling won't stick. The task appears to save, but the next run time never arrives. This usually traces back to a permissions prompt CCC showed and you dismissed. Open System Settings, navigate to Notifications, find CCC Dashboard, and confirm it has permission to alert. While you are there, check that the com.bombich.ccc background item is enabled under Login Items. A restart of the Mac after toggling these settles most scheduling gremlins.

External drive reports "not eligible" as a destination. CCC 7 requires APFS for bootable clones on modern macOS. If your external disk is still formatted as Mac OS Extended, the destination selector will flag it. The fix: back up any data on that drive, open Disk Utility, erase it as APFS (GUID partition scheme), then return to CCC. The eligibility warning disappears.

Disk errors mid-clone. A task that runs fine for weeks suddenly fails with I/O errors. Before you blame the backup software, run First Aid on the destination disk through Disk Utility. Nine times out of ten, the drive itself has a directory corruption issue or a failing block. If First Aid passes, try a different cable and port — USB-C hubs occasionally introduce transfer faults that a direct connection resolves.

Clone takes far longer than expected. A first full clone of a 500 GB drive can take a couple of hours over USB 3. Subsequent clones, using CCC's block-level copy, should finish in minutes. If every run takes hours, check that "Find and replace corrupted files" is switched off in the task's advanced settings — this option re-reads every file on every pass and is meant for troubleshooting, not daily use.

• macOS 10.15 Catalina or newer
• Runs on Intel and Apple Silicon Macs