Can I delete dyld (the dyld shared cache) on a Mac?
- No. The dyld shared cache is where macOS keeps all of its system libraries, the code every app on your Mac runs on. Since macOS 11 those libraries no longer exist as separate files, so this cache is the only copy.
- What deleting it would cost: apps, and macOS itself, couldn’t start. That’s why it lives in parts of the system that are sealed and checked, where you can’t change it.
- Does it come back? It’s replaced with each macOS update and never needs cleaning by hand. There’s nothing to win here.
- SiftMac’s verdict: Leave it
1. What it is
dyld is macOS’s dynamic linker: when an app starts, it connects the app to the system libraries it uses. To make that quick, macOS combines all of its libraries into one prebuilt cache per kind of processor, such as dyld_shared_cache_arm64e on Apple silicon.
Apple’s release notes for macOS Big Sur 11.0.1 say the system ships with a built-in cache of all system-provided libraries, and that copies of those libraries are no longer present on the file system. Deleting the cache wouldn’t clear out duplicates: it would remove the libraries themselves.
2. Where it is
Its location has moved as macOS changed:
| macOS | Where the shared cache is |
|---|---|
| 10.15 Catalina and earlier | /private/var/db/dyld |
| 11 Big Sur and 12 Monterey | /System/Library/dyld, on the sealed system volume |
| 13 Ventura and later | the OS cryptex: /System/Volumes/Preboot/Cryptexes/OS/System/Library/dyld, also reached through /System/Cryptexes/OS |
Howard Oakley notes that the move into a cryptex came with macOS Ventura, possibly in late releases of Monterey. A cryptex is a sealed disk image that macOS checks against its seal before mounting it at startup. Beside the cache you may also see aot_shared_cache, .map and .atlas files; they belong to the same set.
3. How big it gets
On recent macOS the folder can be measured without a password:
du -sh /System/Volumes/Preboot/Cryptexes/OS/System/Library/dyld
It sits on the Preboot volume, not on the data volume with your files, so it doesn’t show up when you measure your home folder.
4. Why it can’t go, and what to do instead
There’s no safe way to remove it, and on current macOS no way at all with the Mac running: the system volume is sealed, and the cryptex is verified before it’s mounted. Don’t look for workarounds such as turning off System Integrity Protection.
If a disk map showed it to you as something large:
- Count it as part of macOS, like the rest of the system. Its size is set by Apple and changes with updates.
- Get space back from what’s yours instead: System Data, app caches and old macOS installers.
5. What happens afterwards
- Left alone, it’s replaced as part of each macOS update, with nothing for you to manage.
- If it were ever damaged, apps would fail to open, and the fix would be reinstalling macOS from Recovery, which keeps your files.
Questions
Can I delete dyld on a Mac?
No. The dyld shared cache holds every system library; without it nothing launches. On current macOS it’s sealed and verified, so it can’t be deleted anyway.
Why is the dyld shared cache so large?
It holds all of macOS’s libraries in one prebuilt file per processor type, so apps start quickly. It replaced the separate library files that older versions of macOS kept.
What is /System/Cryptexes/OS?
A link to the OS cryptex on the Preboot volume, where macOS 13 and later keep the dyld shared cache and other parts of the system. macOS checks it before mounting it; leave it alone.
Is /private/var/db safe to clean?
No. It’s where macOS keeps its own databases, from the unified log to system settings. Leave everything under it to macOS.
How SiftMac handles it. SiftMac doesn’t list or touch the dyld shared cache: it’s part of macOS itself, which the app never touches.
Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works