How to Find Apps Using CPU on Mac
To find which apps are using CPU on Mac, open Activity Monitor, click CPU, and sort processes by the CPU column. Observe the list for several minutes before quitting anything. Activity Monitor provides the detailed process view; HealthZero is a local dashboard for CPU, memory, storage, battery status, startup apps, and plain-language recommendations.
Short answer
Activity Monitor is the built-in way to identify a CPU-heavy app or background process. Its CPU view separates System, User, and Idle percentages, and you can sort the process list by a column heading. Apple also provides CPU Usage and CPU History windows plus a Dock graph for a quick glance.
The most important habit is to observe patterns rather than react to one high number. Video export, software builds, photo analysis, indexing, and browser work can all create short CPU bursts. A process that remains high while the Mac is idle deserves a closer look, but a high reading alone does not prove that the process is broken.
What you need
- A Mac with Activity Monitor, included with macOS.
- Five to ten minutes to reproduce the slowdown, fan noise, or battery drain.
- The name of the task you were performing when the problem appeared.
- Optional: HealthZero, which the current ZeroApps catalog describes as a local Mac health dashboard covering CPU, memory, storage, battery status, large files, startup apps, and recommendations. Check its product page for the current compatibility details; the ZeroApps FAQ currently lists macOS Ventura 13.0 or later for its apps.
Step-by-step: identify a CPU-heavy process
-
Open Activity Monitor. Press Command-Space, search for
Activity Monitor, and open it from Applications > Utilities if you prefer Finder. Keep the window open while you reproduce the symptom. -
Click CPU. The CPU tab lists running processes and shows an overall graph and percentages at the bottom. Apple defines System as processor capacity used by macOS processes, User as capacity used by apps you opened or their processes, and Idle as unused capacity.
-
Sort the process list. Click the CPU column heading to sort by current CPU use. Click it again to reverse the order. If the columns you need are hidden, choose View > Columns and enable the relevant fields. The exact process name may differ from the app name you recognise, so read the row carefully.
-
Capture a baseline. With the suspected app closed, watch the list for about a minute. Note the top few processes and whether the System, User, or Idle percentage changes. This gives you a comparison point instead of a single screenshot.
-
Reproduce the task. Open the app or start the operation that causes trouble. Watch which process rises and whether it stays high. Use the same file, project, or call when possible so your comparison is meaningful.
-
Check current and recent views. For a focused reading, choose Window > CPU Usage. For a trend, choose Window > CPU History. The Dock can also show a CPU graph through View > Dock Icon > the available Show CPU option. These views help you distinguish a brief spike from a sustained load.
-
Inspect before acting. Select a process and double-click it, or click the Info button, to view more information. If the name is unfamiliar, search for it in Apple Support or the software vendor’s documentation. Do not force-quit a system process simply because it appears near the top.
-
Test one change. Save your work, pause one background task, or quit the app you recognise. Wait, then compare the CPU graph and the symptom. If nothing changes, restore the task and test the next likely cause.
How to interpret CPU readings
CPU percentage is a measure of processor activity, not a quality score. A process can use substantial CPU briefly and still be working normally. Look for duration, repetition, and context: does the same process remain high when no task is running, or does it drop when the export, sync, or call finishes?
System and User usage tell you where the work is attributed, but they do not identify whether the work is desirable. A macOS service may be indexing or applying an update. An app you opened may be rendering, compiling, or syncing. Record the process name and the task rather than labelling it “bad” from the percentage alone.
CPU is also only one part of a performance diagnosis. A Mac can feel slow because of memory pressure, storage constraints, a thermal condition, a network wait, or an app that is not responding. Check the Memory, Energy, and Disk views when the symptom does not match the CPU reading. Apple’s Activity Monitor guide documents those separate views.
What to do when one app stays high
Use a conservative escalation path:
- Save the project and close unused documents.
- Check the app for an in-progress export, sync, scan, or update.
- Wait for a legitimate long-running task to complete if the progress indicator is moving.
- If the app is unresponsive, use its normal Quit command first. Force Quit is a last resort because unsaved work may be lost.
- Reopen the app and test the smallest reproducible task.
- Install updates from the developer or the distribution channel you used. For App Store apps, Apple’s Updates view can show available updates; apps obtained elsewhere are updated by their developer.
- Contact the vendor with the process name, macOS version, app version, and steps that reproduce the issue. Do not include private documents in a diagnostic screenshot.
A local dashboard for a broader health check
Activity Monitor is excellent for answering “which process is busy now?” It is less convenient when you want one readable overview of several health signals. HealthZero’s current catalog description covers CPU, memory, storage, battery status, large files, startup apps, and plain-language recommendations, processed locally on the Mac.
If you want that broader snapshot, review HealthZero. Use Activity Monitor to verify a specific process and HealthZero to keep the surrounding context in one place. The product page and checkout remain the authority for the current feature list, price, macOS requirement, and license coverage.
Important limitations
- A high CPU value does not identify malware or prove that an app should be removed.
- Activity Monitor reports processes, not always the friendly app label you expect. Confirm the process before taking action.
- Force-quitting can discard unsaved work and interrupt a legitimate operation.
- CPU readings change continuously and can differ between Apple Silicon and Intel Macs; compare the same task on the same machine rather than using another person’s percentage as a benchmark.
- HealthZero is a dashboard, not a replacement for Activity Monitor’s detailed process inspection or a vendor’s technical support.
Frequently asked questions
How do I sort apps by CPU usage on a Mac?
Open Activity Monitor, click CPU, and click the CPU column heading. Click the heading again to reverse the order. Apple also lets you show additional columns through View > Columns.
What is a normal CPU percentage?
There is no single “normal” number for every Mac or task. A short spike during an export can be expected; sustained high use while the Mac is idle is more informative. Compare the reading with the work you were doing and with a quiet baseline.
Should I quit a process called kernel_task?
Do not force-quit an unfamiliar system process based only on its name or CPU value. Check Apple’s documentation, save your work, and investigate temperature, peripherals, updates, or the app that triggered the activity first.
Why does Activity Monitor show high CPU when no app window is open?
Background services can index files, sync data, install updates, or perform maintenance without a visible window. Sort the process list, observe for several minutes, and search the process name before changing settings or deleting software.
Can HealthZero tell me exactly which process is using CPU?
The current ZeroApps catalog presents HealthZero as a broader health dashboard for CPU, memory, storage, battery, large files, startup apps, and recommendations. Use Activity Monitor for detailed per-process inspection, and check the HealthZero product page for the current feature list.