Why Mac CPU Usage Can Go Over 100%

An app in Activity Monitor is using 200% CPU. Another reaches 350%. At the bottom of the same window, the overall CPU figures still add up to about 100%. It looks as though the numbers cannot all be right.

The short answer: the process list and the whole-system summary use different scales. A process's 100% is roughly one fully busy logical CPU's worth of time. A process using several cores can therefore exceed 100%. The summary at the bottom describes the Mac's overall CPU capacity. A large process percentage is not automatically a broken reading or a reason to force quit an app.

Watch overall load, then check the busiest processes

MacStats keeps your Mac's overall CPU load in the menu bar. Open the Detailed dashboard for Top CPU, where process percentages use the per-logical-CPU scale explained below. You can watch the whole Mac, then check which processes are busiest when something changes.

The monitoring is free for Apple silicon Macs running macOS 13 or later. MacStats Pro adds the Process Explainer when you want help understanding a process you are investigating. Use Activity Monitor's All Processes view for the full system list.

Download MacStats free

Our menu bar CPU guide explains the setup.

100% of what?

For an individual process, think of 100% as one logical CPU's worth of busy time during the measurement interval. The work does not have to stay on one physical core; the scheduler can move it around.

Here are illustrative readings, not measurements from a particular app:

A multithreaded app can distribute work across cores. That is why a video export, build or other parallel task can produce a reading above 100%. Mozilla's Activity Monitor documentation explicitly notes that the process CPU percentage can exceed 100% when several cores are in use.

On Intel Macs with Hyper-Threading, one physical core can expose two logical processors. On Apple silicon, performance and efficiency cores do not all have the same throughput. These percentages measure busy CPU time, not a promise that twice the percentage finishes a job in half the time.

Why the bottom of Activity Monitor stays near 100%

Apple's CPU activity guide describes the three figures at the bottom of the CPU view:

• System: capacity used by macOS processes.
• User: capacity used by your apps and the processes they start.
• Idle: capacity not being used.

Those figures share a whole-system scale. Their total is approximately 100%, allowing for rounding. The individual process rows are not on that same scale.

As a simplified example, consider a machine exposing ten logical CPUs. A process using two logical CPUs' worth of busy time could show around 200% in its row and account for roughly 20% of the machine's total available CPU time. That is an explanation of the scales, not a benchmark of ten-core Macs or a prediction of an app's speed.

This is also why two monitoring tools can show different percentages without either being wrong: check whether each reports a core-based process value or a value normalized across the machine.

Is a high number a problem?

Ask what the app is supposed to be doing.

If you started an export and it is progressing, a busy process may be using the cores you bought to finish that work. If the same app remains busy after the task ends, or it is unresponsive and the Mac is struggling, you have a more useful reason to investigate.

A percentage alone does not tell you whether work is useful, whether the app is stuck, or whether the Mac is running out of memory. Check the duration, the task's progress and how the computer responds.

For the practical steps to open the CPU view and sort its process list, use our guide to checking CPU usage. If memory is the concern instead, memory pressure is a separate reading.

What to do about a process that stays busy

Start with the app you recognize. Save your work and stop the task through the app's own controls if you no longer need it. If it is not responding, macOS provides a process-quit procedure in Activity Monitor. Force Quit can lose unsaved work, so it should not be the first response to an unfamiliar number.

For a background process, identify it before acting. Our background-process guide explains the difference between your apps, user agents and system-owned services. A system process is not interchangeable with a document app you can simply close.

If the Mac feels unusually hot, investigate that as well. CPU activity and macOS thermal state are related observations, not two names for the same measurement.

Frequently asked questions

Why is an app using 200% CPU on my Mac?

Activity Monitor can count an individual process across several CPU cores. Around 200% represents roughly two logical CPUs' worth of busy time, rather than 200% of the Mac's total capacity.

Can a Mac process use more than 100% CPU normally?

Yes. A task that uses multiple cores can exceed 100%. Judge whether that work is expected and making progress, rather than diagnosing a problem from the percentage alone.

Why do System, User and Idle add up to 100%?

They describe the whole Mac's available CPU capacity. Individual process percentages use a different scale, so a process can exceed 100% while the summary still totals about 100%.

Should I force quit anything using more than 100%?

No. Identify the process and check what it is doing first. Save work before quitting an app, and do not treat an unfamiliar system service like an ordinary app window.