How to Check CPU Usage on a Mac

Keeping an eye on your Mac's CPU usage is one of the most useful habits you can develop as a user — whether you're troubleshooting slowdowns, managing battery life, or just curious about what's happening under the hood. Fortunately, macOS gives you several built-in ways to monitor processor activity, and understanding what you're looking at makes the information far more actionable.

What Is CPU Usage and Why Does It Matter?

Your CPU (Central Processing Unit) is the main processor that handles instructions from apps and the operating system. CPU usage refers to the percentage of your processor's capacity being used at any given moment.

A Mac sitting idle might show 2–5% CPU usage. Running a video export, compiling code, or playing a game can push that to 80–100%. That's normal. What's not normal is sustained high CPU usage when you're not doing anything demanding — that usually signals a misbehaving app, a background process gone rogue, or a system under stress.

Understanding your CPU load helps you:

  • Identify which apps are slowing your Mac down
  • Diagnose overheating or fan noise issues
  • Make informed decisions about closing or force-quitting apps
  • Assess whether your Mac's hardware is being pushed beyond its comfortable range

Method 1: Activity Monitor (The Most Detailed View)

Activity Monitor is macOS's built-in task manager and the most comprehensive way to check CPU usage.

How to open it:

  • Press Command + Space to open Spotlight, type Activity Monitor, and hit Enter
  • Or navigate to Finder → Applications → Utilities → Activity Monitor

Once open, click the CPU tab at the top of the window. You'll see a live list of every running process, sorted by how much CPU each one is consuming.

Key columns to understand:

ColumnWhat It Shows
% CPUPercentage of CPU this process is using right now
CPU TimeTotal processor time used since the process started
ThreadsNumber of threads the process is running
PIDProcess ID — useful for advanced troubleshooting

At the bottom of the window, you'll see a CPU Usage graph showing real-time activity split between User (your apps) and System (macOS itself) load.

💡 You can sort by % CPU (click the column header) to instantly surface the most demanding processes.

Method 2: The Menu Bar — Always-On CPU Visibility

If you want a persistent CPU readout without keeping Activity Monitor open, you can add it to your menu bar.

Inside Activity Monitor, go to View → Dock Icon and select Show CPU Usage. This displays a small live graph in your Dock. For the menu bar specifically, third-party utilities handle this more elegantly — but macOS does include a native option through the CPU History window under the Window menu.

Method 3: Terminal — For Command-Line Users

If you're comfortable with the command line, macOS's Terminal offers several options for checking CPU usage:

  • top — Runs a live, updating display of processes sorted by CPU use. Press q to quit.
  • htop — A more readable version of top, available if you've installed it via Homebrew.
  • ps aux — Displays a snapshot of all running processes with their CPU percentages.

These tools are especially useful for remote access scenarios or when diagnosing issues without a GUI.

Method 4: Widgets and System Settings (macOS Sonoma and Later)

On macOS Sonoma and newer, you can add interactive widgets to your desktop or Notification Center. While Apple's native widget options focus more on battery and memory, several third-party apps listed in the Mac App Store offer CPU monitoring widgets that sit on your desktop or lock screen.

Understanding What the Numbers Actually Mean 🖥️

Raw percentages only tell part of the story. A few variables shape what "high CPU usage" actually means for your machine:

Chip architecture matters. Macs running Apple Silicon (M1, M2, M3, and their variants) handle CPU load very differently than older Intel-based Macs. Apple Silicon chips have dedicated efficiency cores and performance cores, so the same task may register differently in Activity Monitor depending on which cores are active.

Core count changes the math. Activity Monitor displays CPU usage as a percentage of total available processing power. On an M2 Pro with 12 cores, 100% means all 12 cores are maxed out. On a base M1 with 8 cores, 100% represents less total throughput. A process showing 400% CPU is actually using the equivalent of four full cores — not a bug in the display.

Thermal throttling is real. On sustained heavy loads, your Mac may reduce CPU speed to manage heat. If performance dips during intensive tasks, that's not always a software problem — it can be the system protecting itself.

Background processes aren't always villains. Processes like mds_stores (Spotlight indexing) or WindowServer (managing your display) may spike briefly and then settle. A persistent spike from a browser tab or a specific app is more worth investigating.

What Counts as "Too High"?

There's no single threshold that applies to every Mac and every use case. A creative professional running Final Cut Pro at 90% CPU is operating normally. The same 90% reading on a Mac doing nothing is a red flag.

Factors that shift the threshold include:

  • The age and model of your Mac
  • Whether it's plugged in or on battery
  • Ambient temperature and ventilation
  • How many apps are running simultaneously
  • Whether the Mac is performing background tasks like backups or indexing

Signals Worth Investigating

Watch for these patterns rather than reacting to any single high reading:

  • Sustained high CPU (above 80–90%) for extended periods with no obvious cause
  • A single process consistently near the top of Activity Monitor, especially one you don't recognize
  • Unusual fan activity or heat correlated with high CPU readings
  • Sluggish performance that Activity Monitor confirms is CPU-bound rather than memory or disk-related ⚡

The combination of which process is running hot, how long it's been elevated, and what you were doing at the time tells a more complete story than any single percentage reading.


What's "normal" and what warrants action depends on your specific Mac model, how you use it, and what baseline behavior you're comparing against — and that's something only your own monitoring history can establish.