How to Monitor CPU Usage on Mac

macOS reports CPU usage as a percentage of total available processing power. A Mac with 100% CPU usage has every processor cycle allocated to active tasks, while 5% usage means the processor is mostly idle. The operating system categorizes this into three buckets: user processes (applications you launched), system processes (background services macOS runs automatically), and idle time.

User processes include browsers, code editors, media players, and any application you open directly. System processes include WindowServer, kernel_task, mds_stores (Spotlight indexing), and other macOS services. Idle percentage is the remaining capacity not currently allocated to any task.

Activity Monitor is the graphical tool Apple ships with every Mac. Open it from Applications > Utilities > Activity Monitor, then select the CPU tab. The window lists every running process with its %CPU column, and the bottom bar shows the system-wide breakdown of user, system, and idle percentages.

Terminal offers the top command for a text-based view. Run top -o cpu to sort processes by CPU consumption. Press q to exit. The top command updates every few seconds and shows load averages, memory pressure, and per-process statistics in a single view.

Both methods require opening a separate application and navigating to the correct view. Neither displays CPU usage persistently in the menu bar without additional software.

P-Cores are designed for maximum single-thread and multi-thread performance. An M1 chip has 4 P-Cores and 4 E-Cores; an M3 Pro has 6 P-Cores and 6 E-Cores. P-Cores consume more power but deliver significantly higher instructions-per-clock throughput.

E-Cores are optimized for energy efficiency. macOS schedules lightweight tasks — notifications, background sync, system maintenance — onto E-Cores to preserve battery life. When a task requires more power, the scheduler migrates it to a P-Core automatically.

Standard macOS tools like Activity Monitor do not distinguish between P-Core and E-Core utilization. Understanding which core type is under load helps diagnose whether a Mac is thermally constrained or simply handling background work.

Runaway processes are applications that enter an infinite loop or memory leak, consuming CPU cycles indefinitely. A single misbehaving browser tab running JavaScript can pin a core at 100% without any visible indication in the browser itself.

Spotlight indexing (mds_stores) and Photos face recognition (photoanalysisd) can consume significant CPU for hours after a macOS update, new photo import, or external drive connection. These processes eventually finish, but they can slow a Mac noticeably while running.

kernel_task is a macOS process that intentionally consumes CPU cycles to generate idle work, preventing other processes from overheating the chip. High kernel_task usage indicates thermal management is active, often due to blocked ventilation, heavy sustained load, or charging in a warm environment.

MoniThor shows a live CPU percentage in the menu bar that updates every second. Clicking the menu bar icon reveals per-core utilization bars, each labeled with its core type — P-Core or E-Core — so you can see exactly which cores are under load without opening Activity Monitor.

The expanded dashboard includes a 60-sample sparkline graph that visualizes CPU usage over the last minute. Load averages (1, 5, and 15 minutes) appear alongside thermal state, system uptime, and the top 3 CPU-consuming processes with their PID and percentage.

MoniThor splits CPU usage into user and system percentages, matching the same breakdown Activity Monitor shows but accessible without switching applications. Color-coded values shift from green to yellow to red as usage increases, providing instant visual feedback about system health.

Activity Monitor's CPU tab reveals which processes consume the most cycles. Sort by %CPU and look for anything above 80% that is not a task you intentionally started. Select the process and click the X button in the toolbar to force-quit it.

Browser tabs are a common source of hidden CPU usage. Each tab runs its own process, and tabs with animations, video, or complex JavaScript can consume a full core. Closing unused tabs or using a tab suspender extension reduces CPU load immediately.

Login items launch automatically when you sign in. Open System Settings > General > Login Items and remove applications you do not need at startup. Fewer login items mean fewer background processes competing for CPU time.

Rebooting clears memory leaks, resets runaway processes, and forces macOS to rebuild system caches cleanly. A restart often resolves unexplained high CPU usage that persists after closing all visible applications.