Carbon Copy Cloner for macOS

CCC 7 arrived as a Universal build, so it runs natively on both Intel and Apple Silicon without a Rosetta translation layer passing data back and forth. That architectural shift came alongside a hard line in the OS sand: version 7 dropped compatibility for Catalina, Big Sur, and Monterey entirely. If your Mac is still on one of those, the installer won't get past the gate.

Does it run natively on Apple Silicon without a crack?

The Universal binary means there's no architectural hack required—the code that ships from Bombich runs directly on M-series chips. The software is licensed, not sold, and the installer is a standard .dmg that handles the activation flow after you open it. If you're working with cracks or patched binaries, make sure SIP is configured to allow the execution flow you need so the app runs without code-signing complaints.

Can you actually clone a bootable drive with the Mac version, or do torrents promise features that aren't there?

Disk cloning is the core feature. CCC creates byte-level clones of entire disks, and the scheduling engine can automate incremental backups on whatever timetable makes sense for the data. A torrent labelled Carbon Copy Cloner 7 torrent often bundles an older version that predates the OS cutoff—meaning it may ship with Catalina-compatible code that CCC 7 itself stripped out, and those builds can still bless an APFS volume group as bootable on modern hardware if you verify the bootability flags after cloning.

A full-system clone and restore walkthrough

Let's say you're swapping the internal SSD in a Mac Studio for a larger one. You have the new drive in an external Thunderbolt enclosure, and you want the replacement to boot exactly like the original—every preference file, every Mail envelope index, every half-finished Xcode project.

1. Open CCC and click New Task. Set the Source to your internal drive's volume group—CCC lists it as a single item with a small icon badge indicating it's an APFS volume group.
2. Set the Destination to the external drive. If the destination is unformatted, CCC prompts you to erase it as APFS. Let it; the dialog even offers to match the source's volume layout.
3. Check the SafetyNet setting. For a straight clone, turn it off—otherwise CCC keeps deleted files in a _CCC SafetyNet folder on the destination, which eats space and isn't what you want for a bootable clone.
4. Click Clone. CCC copies every APFS volume in the group—System, Data, Preboot, Recovery, VM—and blesses the destination so firmware can find the bootloader.
5. Once it finishes, open System Settings > General > Startup Disk, select the external clone, and reboot. Test that everything works: open a few apps, check that iCloud Drive is syncing, verify that Touch ID still functions on the external boot.
6. Shut down, physically swap the drives, and boot. The Mac won't know the difference. No reinstallation, no Migration Assistant, no re-entering licence keys for plugins that fingerprint the boot volume.

If the clone refuses to appear in Startup Disk, boot into Recovery with the external drive attached, open Disk Utility, and check that the clone's Preboot volume exists and is populated. Occasionally a clone interrupted mid-transfer leaves that volume empty, and holding Option at boot shows no entry. Re-run the clone and let it complete without sleeping the Mac.

Why a photographer reaches for a bootable clone after her Samsung T7 fails

Lena runs a small product photography studio from a MacBook Pro. Her working Lightroom catalog lives on a 4 TB Samsung T7. One Tuesday morning, the T7 mounts but beachballs on any read attempt. Disk Utility's First Aid reports unfixable APFS metadata damage.

She opens CCC. The external backup target—a slower 8 TB desktop drive she updates nightly—is already connected. The backup task is named Working SSD Nightly, with SafetyNet enabled and a schedule set to 2:00 a.m. every day. The last successful run shows 3:14 a.m. that same morning, with 12 GB of changes synced from her afternoon Lightroom edits.

She plugs a spare 4 TB Samsung T7 into a different port, opens the CCC task, changes the destination to the fresh drive, and clicks Clone. SafetyNet being on during the recovery run doesn't matter because the destination is empty. Ninety minutes later, she opens Lightroom, points it at the catalog on the new drive, and every edit, flag, and collection is present. The only things lost are a few Finder tags she added after 2:00 a.m. She is back working before the courier arrives with the replacement drive.

What snags do people hit with Carbon Copy Cloner?

"The destination doesn't have enough space" during an incremental backup

APFS snapshots on the destination can quietly consume gigabytes. Open Disk Utility, select the backup volume, and check Show APFS Snapshots from the View menu. If CCC's snapshot retention is generous, you may have weeks of old snapshots stacked up. Delete the oldest half-dozen and the next backup run completes without complaint.

Mail accounts demand re-authentication after a clone restore

This happens because Mail.app ties account tokens to a hardware identifier that changes when booting from a different physical drive. The fix isn't in CCC—it's in Apple's account framework. After the restore, open System Settings > Internet Accounts, delete each mail account, and re-add it. Your mail data is local; the re-auth just refreshes the token.

Scheduled task sits idle at "Evaluating source" for twenty minutes

CCC is walking the filesystem to calculate what changed. On mechanical drives with millions of small files—think node_modules folders or Logic Pro sample libraries—this takes a while. Two things help: exclude directories full of tiny cache files from the task, or switch the destination to an SSD so the subsequent delta copy doesn't compound the wait with slow writes.

Clone boots to a prohibitory symbol

The Mac's firmware can't find a blessed bootloader. Boot into Recovery, open Terminal from the Utilities menu, and run bless --folder /Volumes/YourCloneName/System/Library/CoreServices. If that returns an error about a missing boot.efi, the clone didn't capture the Preboot volume. Re-clone with the destination formatted fresh as APFS and the full volume group selected as source.

Why you should create at least two separate tasks on day one

• Create at least two tasks, not one. One for frequent incremental backups of your home folder (hourly or daily, with SafetyNet on), and one for a weekly full-system clone. The home-folder task catches the document you accidentally trashed at 11 a.m.; the weekly clone gives you a bootable fallback that's never more than seven days stale.
• Name your destination volumes deliberately. CCC uses volume names in notifications and logs. Calling a drive "Backup" tells you nothing when you have three of them. Use names like MacStudio-4TB-Clone or Photos-Nightly so the macOS menu bar and CCC's task list tell you exactly which drive is connected.
• Let CCC do a "dry run" backup before you trust it. Use the Preview button in the Clone pane to see exactly which files will be copied, which will be deleted from the destination, and which are excluded. If something looks off—like a massive .sparsebundle you didn't expect—adjust the task's filter rules before the first real run.
• Check Notification Center after the first scheduled backup fires. CCC sends detailed completion reports there, including transfer speed, file count, and any errors. If the task ran while the destination was unmounted, the notification tells you it was skipped, and the schedule picks up at the next interval.

What settings should you change straight away?

Snapshot retention policy

Open CCC's Preferences, go to Snapshots, and set a retention policy that matches your storage reality. The default keeps every snapshot forever, which on a 1 TB APFS volume can consume the destination within a month of daily backups. A policy like "keep daily snapshots for the last 7 days, weekly for 4 weeks" gives you point-in-time recovery without silently filling the disk. CCC prunes snapshots that fall outside the window automatically.

Power management for laptops

In the Performance & Power preference panel, two checkboxes matter on a MacBook. "Allow scheduled tasks to wake the system" lets an overnight backup run even with the lid closed and power nap active. "Prevent system sleep during backup" keeps a long initial clone from stalling when the display dims. If you work on battery often, leave the first one off and run backups manually when plugged in—a waking Mac in a bag can get toasty.

Exclude Apple's cloud-sync caches

Back in the main window, edit any task that backs up your home folder. Under Task Filter, add a custom exclusion rule for ~/Library/CloudStorage. CCC is file-level, not block-level, so it will happily copy placeholder files that iCloud Drive, Dropbox, or OneDrive have evicted to the cloud. That wastes destination space on stubs that can't be used without re-downloading. Exclude the cloud cache folders and let those services re-sync on the restored volume instead.

• macOS 10.15 Catalina or newer
• Apple Silicon or Intel Mac
• Interface: English