When Apple introduced APFS (Apple File System) to replace the aging HFS+ file system, it fundamentally revolutionized how storage allocation works on macOS. One of its most powerful capabilities is instant Copy-on-Write (CoW) cloning.
However, most legacy disk cleaners and "duplicate file finders" built for the old HFS+ era still calculate disk space using naive file-size addition. As a result, they falsely scare users into believing they are wasting 50–100 GB on "duplicate files" that actually consume zero extra physical space.
1. How APFS Copy-on-Write (CoW) Cloning Works
On legacy file systems, duplicating a file required copying every single raw data block on disk from one physical sector to another. If you had a 20 GB file, duplicating it consumed 20 GB of new space and took several seconds to write.
Under APFS, when you duplicate a file or folder on the same volume (⌘D in Finder):
- macOS creates a new file metadata record (inode).
- Both inodes point to the exact same shared physical storage extents (NAND flash blocks).
- No duplicate data is written to disk. The operation completes in 0 milliseconds and consumes 0 bytes of extra disk space.
2. Why Traditional Mac Cleaners Give False Alarms
Traditional disk space analyzers compute folder sizes by summing the logical byte count of every file returned by the standard POSIX stat() API.
If you have a 50 GB project and create two clones for experimentation:
- Naive Cleaner Calculation: 50 GB + 50 GB + 50 GB = 150 GB reported
- Physical SSD Reality: Exactly 50 GB physically allocated
When a naive cleaner instructs you to "Delete 100 GB of duplicate files!", deleting those clones frees 0 bytes of space while destroying your backup versions and active project branches.
APFS-Aware Storage Mapping with DiskAtlas
DiskAtlas queries APFS shared extents directly via kernel APIs, accurately displaying Logical vs. Physical disk footprint so you only clean what actually frees up space.
Try DiskAtlas Free3. How to Check APFS Clones in Terminal
You can verify if two files on your Mac share the same physical extents using the macOS stat command or ls -lO:
stat -f "Inode: %i | Blocks: %b | Size: %z bytes | File: %N" file1.mov file1_copy.mov
To inspect the low-level APFS container extent reference counts and volume structure:
diskutil apfs list
4. Logical Size vs Physical Footprint Compared
| Scenario | Logical Size (Finder) | Physical Space on SSD | DiskAtlas Detection |
|---|---|---|---|
| Original 4K Video | 42.0 GB | 42.0 GB | Unique Blocks |
| Finder Duplicate (⌘D) | 42.0 GB | 0.0 GB (Shared Extent) | APFS CoW Clone Identified |
| Xcode Workspace Clone | 28.5 GB | 0.0 GB (Shared) | APFS CoW Clone Identified |
| Modified Video (500 MB edit) | 42.0 GB | 0.5 GB (Delta Only) | Delta Extents Tracked |
Key Takeaways for Mac Users
- Feel free to duplicate: Duplicate large projects, datasets, and videos on your primary APFS drive without fear of consuming double storage.
- Beware generic cleaners: Do not trust legacy cleaners that do not understand APFS shared extents.
- Use DiskAtlas: DiskAtlas gives you true physical accuracy, protecting your shared clones while isolating real bloat.