When your Mac runs slowly, open Activity Monitor while the slowdown is happening. Look for a sustained pattern in CPU use, memory pressure and the apps you are using. One large number does not identify a fault on its own, and quitting unfamiliar processes at random can create a second problem.
This guide uses the built-in macOS utility. Names and layout can vary by macOS version. Save your work before closing applications or restarting, and keep a backup before making wider system changes.
Describe the symptom before changing settings
Does every app respond slowly, or is one website taking time to load? Does the delay begin after opening a particular project, connecting a drive or starting a video export? Note what changed and whether the Mac recovers after the task finishes.
Try the same simple action twice: once during the slowdown and once after closing an application you recognise. This controlled comparison is more useful than installing a “cleaner” and changing several things at once.
Open Activity Monitor and sort the relevant column
Find Activity Monitor through Spotlight or the Utilities folder. Apple’s process-viewing instructions explain sorting columns and changing the View filter. Use All Processes when you need a broader picture, and double-click a process for more information.
Give the display time to show a pattern. A process briefly reaching the top of the list while an app opens is different from the same app staying there throughout an unexplained slowdown. Record the app and task rather than treating every background process as unnecessary.
Check CPU activity while repeating the slow task
In the CPU view, sort by CPU use and watch which processes remain busy. Compare that with the overall activity at the bottom. Apple describes the System, User and Idle readings in its CPU activity guide.
A video export, game or large calculation has a reason to be busy. Let a known task finish and check whether normal responsiveness returns. If the same app remains unusually active when its work should be finished, save your documents, quit that app normally and reopen it. Then check for an update from its developer.
Read memory pressure rather than chasing empty RAM
In the Memory view, look at Memory Pressure alongside your actual symptoms. Apple’s memory usage explanation covers compressed memory, cached files and swap. Cached memory is not automatically wasted memory, and swap being present alone does not prove a failure.
If responsiveness deteriorates as you open more projects or browser tabs and improves when you close some, reduce that workload and compare again. Persistent pressure during your normal work is a better reason to assess capacity than a screenshot showing little “free” RAM. Check your model’s upgrade options before assuming its memory can be replaced.
Quit recognised apps carefully
Use the app’s own Quit command first. In Activity Monitor, selecting a process and choosing the Stop control offers Quit or Force Quit. Apple warns that Force Quit acts immediately and can lose unsaved data or affect related processes.
Reserve it for an app that is not responding after you have considered unsaved work. Do not force quit a system process merely because its name is unfamiliar. If you cannot identify it, record the name and seek an explanation before acting.
When CPU and memory do not explain it
Check whether the delay is limited to internet access, an external disk or one document. Review free storage in System Settings and keep important files backed up. Apple’s slow Mac checklist includes storage, app requirements and disk issues.
If the problem keeps returning, collect the Mac model, macOS version, affected app version and the resource pattern observed during the delay. Those details give support a reproducible starting point and help you judge whether an app fix, a storage issue or different hardware deserves attention.