Why is my Mac CPU usage high?

Find the current CPU user in Activity Monitor

Activity Monitor is the authoritative built-in view for the complete current process list. Observe the process for more than one refresh so a brief launch spike is not mistaken for sustained use.

1. Open Activity Monitor and select CPU.
2. Sort the process list by the CPU column.
3. Check the User, System, and Idle figures at the bottom of the window.
4. Choose Window → CPU History if you need to see activity across the processor over time.
5. Search for the process name or open its information panel before taking action.

Decide whether the workload is expected

A repeatable pattern is stronger evidence than a single number. If the same app returns to high CPU while idle after every restart, update it and reproduce the behavior before contacting its developer.

• Match the process name to an export, build, game, call, sync, backup, update, or indexing task.
• Wait for the foreground task to finish and see whether CPU use falls.
• If a helper process is busy, identify the parent app before closing it.
• If the process is unfamiliar or belongs to macOS, do not end it only because it ranks first.

Test a reversible next step

Force quitting can lose unsaved work or affect related processes. A lower CPU reading after force quit shows that the process was active; it does not by itself explain why.

1. Save work in the suspected app.
2. Quit the app normally with Command-Q.
3. Confirm in Activity Monitor that the process has exited and overall CPU use has fallen.
4. Reopen the app and repeat the same workload.
5. Use force quit only if the app does not respond to a normal quit.

Track the pattern with KernPulse

KernPulse can show total CPU in the menu bar, total and per-core activity in its panel, a live process ranking, and up to 24 hours of overall CPU history. Search helps find a named process, and up to three process names can be pinned for a separate one-hour CPU trend.

Optional CPU threshold notifications are delayed until the threshold remains high for several samples, reducing alerts from isolated peaks. An alert still indicates load, not a confirmed fault.

Keep process actions in context

KernPulse can pause an eligible user app as a whole process group or ask a selected process to terminate, but it does not act automatically by default. Pausing preserves memory and stops CPU work; it does not repair the app, save documents, or complete background operations.

Protected system processes are excluded. Use Activity Monitor when you need every process, hierarchical relationships, samples, spindumps, or system diagnostics.