GPU Cache
Metal Shader Cache
Compiled Metal shader artifacts are stored under com.apple.metal so macOS and the GPU driver can reuse pipeline state data instead of recompiling shader code every time an app launches. This cache can accumulate stale driver-specific shader binaries, pipeline compilation results, and related GPU cache files after macOS updates, graphics driver changes, or app updates. Kudu removes those disposable Metal shader cache files so the system can rebuild fresh compiled shaders without affecting documents, accounts, settings, or saved app data.
Why clean Metal Shader Cache?
- Driver update invalidation leaves old compiled Metal shader blobs mismatched with the current GPU stack, causing stutter, hitching, or a long first launch while shaders are rebuilt
- Corrupted pipeline cache entries can trigger black textures, missing interface effects, or flickering scenes in apps that rely on Metal rendering
- Apps with heavy real-time graphics can repeatedly recompile shaders when cache records are inconsistent, showing up as frame drops and delayed scene transitions
- Old per-app Metal cache data can consume hundreds of megabytes of disk space even after the original apps or game versions have changed
- After a macOS upgrade, stale compiled shader artifacts may no longer match updated system frameworks, leading to rendering glitches or unexpected GPU-related crashes on startup
- Clearing the cache forces a clean rebuild of pipeline compilation results, which often resolves visual corruption without touching user files, preferences, logins, or project data
What gets cleaned
Cache paths Kudu targets
macOS
~/Library/Caches/com.apple.metal |
Frequently asked
Common questions about Metal Shader Cache
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.