Why is the Unity Editor using so much CPU on my Mac?
Last reviewed: 19 November 2026.
The Unity Editor keeps updating its windows in a loop, and how long it idles between frames is set by Interaction Mode in Unity > Settings > General. No Throttling makes the Editor update as fast as possible, which Unity says uses a lot of CPU and drains laptop batteries quickly. In Play mode Unity ignores throttling entirely unless you turn on VSync in the Game view or set a target frame rate.
What does Interaction Mode do?
Unity's documentation describes Interaction Mode as how long the Editor can idle before it updates; it exists to throttle Editor performance and reduce CPU and power use. Throttled modes stop idling as soon as you interact, for example by panning in the Scene view.
| Interaction Mode | Behavior |
|---|---|
| Default | Idles up to 4 ms each tick. If a frame takes 5 ms or more, the next frame starts without idling. |
| No Throttling | The next frame starts immediately. Unity notes this consumes a lot of CPU and can drain a laptop battery quickly. |
| Monitor Refresh Rate | Idles up to the display's refresh interval, typically 16 ms. |
| Custom | Set Frame Throttling between 0 and 33 ms. |
How do you reduce the Unity Editor's CPU use?
- Throttle the Editor. Choose Unity > Settings > General and set Interaction Mode to Monitor Refresh Rate, or Custom with a higher Frame Throttling value.
- Cap the frame rate in Play mode. Turn on VSync in the Game view, or set
Application.targetFrameRateto a value other than -1, so Play mode does not run unthrottled. - Exit Play mode when you are not testing. Play mode runs your game loop continuously and ignores Interaction Mode.
- Close Scene and Game views you do not need. Each visible view is redrawn on every Editor update.
What else makes Unity busy?
Importing assets and compiling scripts after you change files use several cores until they finish. Code Optimization On Startup sets whether the Editor starts in Debug or Release mode; Unity notes Release gives faster C# performance in Play mode but does not allow attaching external debuggers. Unity Hub, which manages installs and projects, runs separately from the Editor and should be idle when you are not using it.
When is Unity's CPU use a problem?
Full CPU during imports, script compilation, light baking or Play mode is expected. High CPU while the Editor sits idle in Edit mode usually means Interaction Mode is set to No Throttling, or an Editor script or package is repainting a window continuously.
How can Thrum help with Unity?
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 Unity 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 Unity 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
Why does Unity heat up my MacBook when idle?
With Interaction Mode set to No Throttling, the Editor updates as fast as possible even when you are not interacting with it. Choose Default, Monitor Refresh Rate or Custom instead.
Does Interaction Mode affect Play mode?
No. Unity ignores this throttling in Play mode; use VSync in the Game view or a target frame rate.