How to check CPU and memory usage on Mac

Decide what you are trying to explain

Start with a specific symptom: a long export, a pause when switching windows, or a slowdown after opening several projects. Note what was running and when it happened. That context gives the CPU and memory figures something useful to explain.

CPU and memory readings describe resource use; neither alone identifies every cause of a delay. A busy processor may be doing exactly the work you requested. Look at the timing of the reading and the workload rather than treating one large number as a diagnosis.

Inspect the CPU view in Activity Monitor

Open Activity Monitor and click CPU. Apple’s guide distinguishes System activity from User activity and Idle capacity at the bottom of the window. Those categories help you see whether the processor is busy overall while the process list provides more detail about what is running.

For a view over time, Apple documents Window > CPU Usage for current activity and Window > CPU History for recent activity. Compare the period when the task is working with a quieter period. Do not infer a fault from a brief peak during an intensive operation.

1. Open Activity Monitor on the Mac you are investigating.
2. Click CPU and observe the overall activity during the task.
3. Use the CPU Usage or CPU History window if a time view helps.
4. Note whether activity falls after the task finishes.

Read memory use with memory pressure

Click Memory to see installed memory, memory used, memory pressure and related figures. Apple explains that memory pressure reflects how efficiently memory is serving the current workload, using factors including free memory, swap rate, wired memory and file cache.

Occupied RAM is not the same as wasted RAM. macOS can use otherwise unused memory for cached files, and compressed memory is another part of how it manages active workloads. Read those figures together before deciding that a high used-memory amount explains a slowdown.

Compare before, during and after one task

Try this observation exercise with a task you already perform, such as exporting a video or opening a large project. Before starting, note the CPU activity and memory pressure. Observe them during the work, then again after it completes. Record the task and approximate time as well as the readings.

This is a suggested way to collect context, not a benchmark or a report of a test we ran. A peak that ends with the task tells a different story from activity that continues while the Mac is otherwise idle. If a problem recurs, that short record gives you a clearer starting point for investigating the relevant app.

Use Wisp for a glanceable system view

Wisp monitors system CPU, memory, network activity and storage capacity. You can choose CPU and memory readings for its menu bar and open the dashboard for more context. Its memory card presents usage alongside a pressure badge, so the amount in use does not have to stand alone.

The reviewed Wisp release is 1.0.3 and requires macOS 26 or later. Hardware and macOS access affect measurement availability; missing readings stay unavailable. The release notes state that macOS 26 and Intel hardware testing remain outstanding. A supported package requirement is not evidence of testing on every Mac.

Use the reading to guide the next check

If activity coincides with an app doing expected work, let the task finish and observe again. If a particular workload repeatedly coincides with poor responsiveness, inspect its process information and review the app’s own guidance. Save work before closing anything you need.

A monitor supplies observations. Wisp’s readings do not promise that adding memory, clearing a cache or terminating a process will fix a problem. Identify the workload, record the context and investigate repeated behavior instead of trying to make every usage figure small.

Questions