Why your Mac has two “Macintosh HD” volumes

Open Disk Utility and you'll see two volumes with nearly the same name: Macintosh HD and Macintosh HD - Data. It looks like a duplicate, or a glitch. It's neither. Since macOS Catalina, every Mac splits its startup disk this way on purpose, and the Macintosh HD - Data volume on your Mac is exactly where your files are meant to live. Nothing is broken. Here's what the two volumes are, why Apple designed it this way, and why you should leave both alone.

It's normal: your startup disk is an APFS volume group

macOS is installed on what Apple calls "a set of volumes known as a volume group." The group has two members that work as a matched pair:

• Macintosh HD: the read-only system volume. It holds macOS itself and nothing else. Apple keeps it "completely separate from all other data to help prevent the accidental overwriting of critical operating system files."
• Macintosh HD - Data: the writable data volume. Your account, the apps you install, your documents and photos, your settings, and every scratch file macOS makes all live here.

Finder fuses the two so you experience a single drive called "Macintosh HD"; you never have to think about the split day to day. Disk Utility shows both because it works one level down, at the volume level. If you upgraded from an older macOS instead of installing fresh, the read-only volume was created for you during that upgrade.

So two "Macintosh HD" entries is the correct, healthy state. A Mac with only one would be the unusual one.

Why the split exists: a sealed system and safer updates

Two reasons, both about trust.

Integrity. On modern macOS the system volume isn't merely read-only. It's the Signed System Volume (SSV), documented in Apple's Platform Security guide. Apple cryptographically hashes the entire system volume down to a single root hash it calls a "seal." A kernel mechanism then verifies system content as it runs and "rejects any data — code and noncode — without a valid cryptographic signature from Apple." In plain terms: the operating system can't be silently altered: not by malware, not by a misbehaving installer, not by you. Apple introduced the read-only system volume in macOS Catalina (10.15) and added the cryptographic sealing in macOS 11.

Reliable updates. Because the system is a known-good, sealed snapshot, macOS can apply and verify updates against that seal and boot into a fresh system cleanly. Your data volume rides alongside, untouched by the swap. (If you use FileVault, it encrypts the data volume separately with your own secret, a second, independent layer.)

The takeaway is that this design is doing quiet, useful work every time your Mac boots and every time it updates.

Don't try to delete or merge them

This comes up a lot, so plainly: no.

You can't merge the two back into one; the whole point is that they're separate, and the system volume is sealed against modification. And you must not erase Macintosh HD - Data to "reclaim" it: that volume is your Mac's contents. Wiping it erases your account, apps, and files. The two are a pair by design. Leave both exactly as they are; there's no maintenance to do here and nothing to fix.

What the Macintosh HD - Data volume holds (and what it means for storage)

Practically everything you care about sits on the data volume: your Users folder, installed apps, ~/Library, caches, and the catch-all System Data category. The system volume, by contrast, is fixed and comparatively small; you don't manage it, and it barely changes between updates.

Here's the part that trips people up when they're low on space. Both volumes live inside a single APFS container, and volumes in a container share the container's free space. Free space isn't a property of one volume or the other. It belongs to the container, and either volume can draw on it. That's why Finder shows you one capacity bar instead of two, and why the accurate place to read true free space is the APFS container in Disk Utility, not an individual volume.

It's also why the numbers can look strange. When macOS reports purgeable space or a startup disk that's suddenly almost full, that math is happening at the container level, across both volumes and the snapshots and caches shared between them, not on the tidy little system volume. The two-volume layout isn't what's eating your disk; it's just the structure the real usage is reported through.

Seeing where the space actually goes

The two-Macintosh-HD design is solid engineering, but it does hide the ball: one fused drive in Finder, one blended free-space number, and a sealed volume you can't inspect anyway. When you actually need space back, the question isn't "which Macintosh HD." It's what's piling up on the Data volume, inside the shared container. Plumby maps that container in plain terms (caches, snapshots, iOS backups, developer build-up), each with its exact path and real size, and clears only the safe, regenerable things. Freed space is measured as each item goes, nothing is estimated, and anything it clears can go to the Trash rather than be deleted, so you can put it back. It never touches your documents, photos, or projects.