What is MTLCompilerService, and why is it using so much CPU?
Last reviewed: 19 November 2026. Path, account and running instances checked on macOS 26.3.1.
MTLCompilerService is the Metal framework's helper that compiles shaders, the small programs apps and games run on the GPU, into code for your Mac's graphics hardware. It uses a lot of CPU the first time an app or game builds its shaders, and after an app or macOS update, then drops back as compiled results are cached. It is safe and normally needs no action.
MTLCompilerService at a glance
| MTLCompilerService | |
|---|---|
| Made by | Apple (part of macOS, Metal) |
| Type | XPC service |
| Location | /System/Library/Frameworks/Metal.framework/Versions/A/XPCServices/MTLCompilerService.xpc/Contents/MacOS/MTLCompilerService |
| Runs as | your user |
| Can you quit it? | Yes, but the app that needed it will ask for it again, and any shader compile in progress starts over. |
What is MTLCompilerService?
Metal is Apple's interface to the GPU. Apps write their GPU code as shaders, and before a shader can run it has to be compiled for the specific GPU in your Mac. Metal does that compilation in MTLCompilerService, an XPC service (a helper process that a framework starts on demand) inside Metal.framework, rather than inside the app itself.
There can be several MTLCompilerService processes at once, typically one for each app that is compiling shaders, and each runs as your user. Games, video editors, 3D apps, browsers and macOS itself all use Metal. Compiled shaders are kept in a cache in your user's cache folder (com.apple.metal inside the folder that getconf DARWIN_USER_CACHE_DIR prints), so the same work is not repeated every launch.
Is MTLCompilerService safe?
Yes. MTLCompilerService is part of macOS, is signed by Apple, and lives inside /System/Library/Frameworks/Metal.framework on the read-only system volume. It runs only when an app asks Metal to compile shaders.
Why does MTLCompilerService use so much CPU and memory?
- First launch of a game or 3D app. Games and 3D apps often build hundreds or thousands of shader variants when they first start or load a new level. That can keep MTLCompilerService busy on several cores for minutes.
- After a macOS or app update. An update can change the compiler or the app's shaders, so cached results no longer match and shaders are compiled again.
- Changing graphics settings. Changing quality settings in a game can switch to shaders that have not been compiled yet.
- Large shader libraries. Compiling large or complex shaders takes memory while it runs; it is released when compilation ends.
How much CPU is normal for MTLCompilerService?
Idle or absent most of the time. High CPU for seconds to several minutes when a game or graphics app starts for the first time, or after an update, is expected; later launches are typically much quicker because results are cached.
Several instances at once are normal when several apps compile shaders at the same time.
How do you stop MTLCompilerService from using so much CPU?
- Let the first compile finish. Keep the game or app open on its loading or menu screen until MTLCompilerService drops back toward 0% in Activity Monitor. Quitting part-way means the work is repeated next time.
- Find which app started it. In Activity Monitor, choose View > All Processes, Hierarchically. Each MTLCompilerService appears near the app that launched it; quitting that app ends its compiler too.
- Update the app. If one app triggers long compiles on every launch, check for an update from its developer: shader caching is up to the app.
- Keep the cache. Avoid cleaning tools that empty the user cache folder. Deleting the Metal cache makes every app compile its shaders again.
When should you worry about MTLCompilerService?
Look closer if MTLCompilerService stays high every time you open the same app, long after its first launch. That suggests the app is not reusing compiled shaders, which is a matter for the app's developer.
It should only run from inside Metal.framework. A copy elsewhere would not be Apple's.
How do you check MTLCompilerService in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type MTLCompilerService in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every MTLCompilerService process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'MTLCompilerService' | grep -v grep
How can Thrum help with MTLCompilerService?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when MTLCompilerService is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click MTLCompilerService in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about MTLCompilerService
Why are there several MTLCompilerService processes?
Metal starts a compiler service for apps that need shaders compiled, so several apps compiling at once means several processes.
Does MTLCompilerService use the GPU?
No. Compiling happens on the CPU. The compiled shaders then run on the GPU inside the app that asked for them.
Can I stop it from running?
Not without stopping the app that needs it. Letting it finish once is the fastest way to make it go quiet.