When your Mac starts running slowly, the fans spin up like a jet engine, or an application becomes completely unresponsive, randomly clicking buttons will not solve the issue. Instead, you need to diagnose the root cause using macOS’s built-in diagnostic tool: Activity Monitor.
Activity Monitor is the macOS equivalent of the Windows Task Manager. It provides a real-time window into how applications and background processes are consuming your Mac’s CPU, Memory, Energy, Disk, and Network resources. In this guide, you will learn how to use Activity Monitor to identify and resolve performance bottlenecks.
Accessing Activity Monitor
There are a few ways to launch the application:
- Spotlight Search (Fastest): Press Cmd + Space, type “Activity Monitor”, and hit Enter.
- Launchpad: Open Launchpad and look inside the “Other” folder.
- Finder: Navigate to Applications > Utilities > Activity Monitor.
Understanding the CPU Tab
If your Mac feels sluggish or the fans are loud, the CPU (Central Processing Unit) tab is where you should look first. It shows how hard your processor is working.
- Click the CPU tab at the top of the window.
- Click the column header named % CPU to sort the list so that the processes using the most power are at the very top.
- Look for any application consistently using a massive percentage (e.g., 90% or higher).
Important Note: You will see many processes owned by “root” or “_windowserver”. These are essential macOS system processes. Do not attempt to force quit these. Focus only on applications you recognise, such as Google Chrome or Adobe Premiere.
How to Force Quit an Unresponsive App
If an app has crashed (often highlighted in red with the words “Not Responding” next to it), or a runaway process is consuming all your CPU:
- Click to select the problematic process.
- Click the Stop (X) button in the toolbar at the top of the Activity Monitor window.
- Choose Quit (a safe shutdown) or Force Quit (an immediate termination, which may result in unsaved data loss for that specific app).
Understanding the Memory Tab
If your Mac stutters when switching between apps, or you receive a “Your system has run out of application memory” warning, you need to check the Memory tab.
- Click the Memory tab.
- Sort by the Memory column to see which apps are hoarding RAM. Browsers like Chrome, especially with dozens of tabs open, are frequent offenders.
Look at the Memory Pressure graph at the bottom of the window:
- Green: Your Mac has plenty of RAM available. Performance should be fine, even if most of the RAM is “used” (macOS is designed to use RAM aggressively for caching).
- Yellow: Your Mac is starting to compress memory and use the hard drive (swap space) to compensate. You might notice slight slowdowns.
- Red: Your Mac is critically out of RAM and heavily relying on the much slower hard drive. You must close heavy applications immediately to restore performance.
Understanding the Energy Tab
If you are using a MacBook and wondering why your battery is draining rapidly, the Energy tab provides the answers.
- Click the Energy tab.
- Sort by Energy Impact. This represents the current power draw of the application.
- Sort by 12 hr Power to see which applications have been the biggest drain on your battery over the course of the day.
If an app shows “Yes” in the Preventing Sleep column, it means that app will stop your Mac from going to sleep when you close the lid (common with video players or heavy download managers).
Understanding the Disk and Network Tabs
- Disk: Shows which apps are reading and writing the most data to your storage drive. High disk usage can slow down older Macs with mechanical hard drives, though it is less noticeable on modern Macs with fast SSDs.
- Network: Shows which apps are sending and receiving data over the internet. If your internet feels slow, sort by Rcvd Bytes (Received Bytes) to see if a background process (like an iCloud sync or software update) is monopolising your bandwidth.
By learning to read Activity Monitor, you transition from guessing why your Mac is slow to diagnosing and fixing the exact software culprit.