Why is my Mac so slow? The five real causes and a 60-second diagnosis

What "slow" actually means on a Mac

People use one word for at least three different problems. The spinning beach ball in one app means that app is waiting on something: the CPU, the disk or a network reply. Lag everywhere, with the mouse stuttering and window animations dropping frames, means the whole system is short on a resource, usually memory or a CPU that has been throttled to stay cool. A Mac that takes minutes to boot or open apps but is fine once they are open points at the disk being nearly full or a long login-items list.

The reason this matters is that each symptom has a different cause and a different fix. A guide that gives you twenty tips in a row is asking you to try all twenty. You do not need to. You need to open Activity Monitor, look at two tabs, and read what it says. The rest of this page walks through the five causes in the order they usually turn out to be the answer, then the one safe fix for each, then the list of things that look like fixes but are not.

One honest note before the list. Macs do not get slower with age the way people assume. A 2020 M1 Air with a clean workload is as fast today as the day it shipped. What changes is the workload: more tabs, heavier web apps, bigger photo libraries, more background agents from apps you installed and forgot. That is good news, because workload is something you can see and change.

How do I check why my Mac is running slow? The 60-second diagnosis

Open Activity Monitor (press ⌘Space, type "Activity Monitor", press Return). Then follow this path. It takes about a minute and it ends at exactly one cause.

Two reading tips. First, the % CPU column counts each core separately, so on an 8-core Mac the total can reach 800. A single process at 100 means it has one core fully busy, which is enough to make that app feel stuck but not enough to slow everything else. A process at 300 or 400 is pulling the whole machine down. Second, do not trust a single glance. Many processes spike for a few seconds and settle. Watch for 30 seconds before deciding something is a hog.

Cause 1: one app or tab is eating the CPU

This is the cause more often than all the others combined. One process, usually something you can name, sits at 100 percent or more of a core for minutes and the Mac warms up, the fan comes on, and everything gets sticky. The usual suspects are a browser tab with an auto-playing video or a heavy web app, a video call that stayed open after the meeting, a sync client working through a huge folder, a photo or video export, and the occasional app that has simply hung in a loop.

Browsers deserve their own sentence. Chrome, Safari and the rest split each tab into its own process, so Activity Monitor shows "Google Chrome Helper (Renderer)" or "Safari Web Content" rather than the tab name. Each browser has its own task manager that maps those to tabs: in Chrome it is Window, Task Manager; in Safari it is the Develop menu. The which tab is using memory guide covers that in detail. The short version is that one bad tab can hold a core by itself, and closing it fixes the Mac instantly.

The fix is the obvious one: quit that app, or close that tab. If the app does not respond to ⌘Q, use Force Quit (⌥⌘Esc). You lose unsaved work in that app and nothing else. If it is a process you do not recognize, look at the parent app name in the Energy tab, which groups helper processes under the app that owns them, before you decide. If the name ends in "d" and the User column says root, it is a macOS daemon and the right move is to look up what it does rather than quit it.

Cause 2: memory pressure and swap

The second most common cause is memory, and the number that matters is not "Memory Used". macOS is designed to use almost all of your RAM all the time, so a Mac showing 7.5 GB used out of 8 can be perfectly healthy. The number that matters is the Memory Pressure graph at the bottom of the Memory tab in Activity Monitor. Green means macOS has room to work. Yellow means it is compressing memory and starting to swap to disk to keep up. Red means it is out of room and everything is going to feel like wading through mud.

When pressure is yellow or red, the Mac slows down in a specific way: switching between apps takes a beat, the beach ball appears when you click into something you have not touched in a while, and the whole system feels a step behind. That is the cost of pulling pages back from compressed memory or from swap on the SSD. One Apple Community poster with a 16 GB M2 Air described swap that "grows to crazy levels like 30GB of SWAP used for the exact same apps and browser tabs open", which is the signature of one process leaking rather than normal load.

The fix is to find the grower, not to "free RAM". Click the Memory column header to sort by size. The top entries will be your browser, WindowServer and your biggest app. If one of them is far bigger than it was an hour ago, that is the leak. Quit it and reopen it. If WindowServer is at several gigabytes, close windows and tabs, and log out and back in if it does not drop. The memory pressure guide explains green, yellow and red in detail, and the application memory dialog page covers the worst case. 8 GB Macs hit this far sooner than 16 GB ones, which is the one place where the hardware genuinely is the limit.

Cause 3: Spotlight is indexing after an update or a big import

If your Mac got slow right after a macOS update, after you restored from a backup, after you plugged in a large external drive, or after you dumped tens of thousands of photos or files onto it, Spotlight is almost certainly the answer. The processes are mds_stores, mdworker and corespotlightd, and together they read every new file so you can search it later. They run hot, they run for a while, and they are supposed to.

How long is "a while"? For everyday use, 10 to 30 minutes. After a macOS update, or when you add a very large volume of files, it can be a few hours. During that time the fan is on, the Mac is warm, and anything disk-heavy is slower than usual. One Apple Community poster watched mds_stores "consistently using more than 85% of the CPU" and assumed something was broken. Usually nothing is. It finishes, the CPU drops, and the Mac is back to normal with nothing to show for it except a working search box.

The fix is to wait, and to plug the Mac in so it is not trying to index on battery. If you want it to finish faster, close heavy apps so Spotlight gets the cores. If it has been more than a day and the same processes are still at the top, something is making it restart: usually a folder of constantly changing files such as a build directory, a VM disk image or a huge mail cache. You can tell Spotlight to skip those folders in System Settings, Siri & Spotlight, Spotlight Privacy, which is the one safe setting change here. Do not delete the index by hand and do not run commands you found in a forum against it.

Cause 4: heat throttling, which shows up as kernel_task

This one confuses more people than any other. You open Activity Monitor, and a process called kernel_task is at 300, 500 or 800 percent CPU. It looks like a runaway system process. It is the opposite. kernel_task is macOS holding your Mac back on purpose: when the chip gets too hot, the kernel occupies CPU time with nothing so other processes cannot drive the temperature higher. One MacRumors poster described exactly this: "Activity Monitor is telling me that a process called "kernel_task" is using 87-93% CPU power." The Mac was not broken. It was hot.

So the question is not "how do I stop kernel_task" but "why is my Mac hot". The answers are usually boring: it is on a blanket or a lap with the vents covered, it is in direct sun, it is charging through a hot adapter while running a heavy app, the room is warm, or one of the causes above (a hung app, Spotlight, a video call) has been running the chip flat out for half an hour. Intel MacBooks also throttle when charging on the left side ports under load, a quirk that showed up in many forum threads over the years.

The fix is to find what is making the Mac hot and ease it, then wait. Quit the heavy app, get the Mac onto a hard flat surface, let the fan do its job. Throttling lifts a few minutes after the workload eases. You cannot and should not quit kernel_task. If the Mac is hot with nothing running and the fan never spins, that is the rare hardware case: dust in the vents on an older Intel machine, or a fan that has failed, and that is a repair question, not a software one. The overheating guide goes deeper.

Cause 5: the startup disk is nearly full

macOS needs free space to work. It writes swap files there when memory is tight, it writes temporary files for every app, and APFS, the file system, keeps local Time Machine snapshots there too. When free space drops below roughly 10 to 15 percent, all of those start fighting over the remainder, and the Mac slows in a general, hard-to-pin-down way. Below a few gigabytes free, apps start failing to save and macOS starts warning you.

Check it in Apple menu, About This Mac, Storage (or System Settings, General, Storage). If the bar is almost full, the biggest category is usually "System Data", which is a bucket for things like local snapshots, app caches, iOS backups and developer tools. It is often 50 to 200 GB and it is the one category you cannot click into. The System Data guide explains what is in it and what is safe to remove. The free up space guide gives the full order.

The safe fix, in order: empty the Trash, clear out Downloads, delete old iOS backups from Finder, uninstall big apps you no longer use, and move large media to an external drive or iCloud. Restart, then give macOS a day: it thins local snapshots itself when space is tight. Do not delete anything inside the Library folders by hand to "make room". Most of it regrows, and some of it is the only copy of your mail, messages or app data.

What to do about a slow Mac, in order

1. Sort Activity Monitor by % CPU and quit the hog

   CPU tab, click the % CPU header. If one app or tab is at 100 percent or more for over a minute, quit it with ⌘Q or close that tab. If it will not quit, Force Quit it with ⌥⌘Esc. That is the fix for cause 1, and it resolves most slow Macs on the spot.

2. Check the Memory Pressure graph

   Memory tab, look at the graph at the bottom. Yellow or red: sort by the Memory column, find the biggest grower (often a browser or WindowServer), quit and reopen it, and close windows you are not using. Do not install anything to "free" memory.

3. If mds_stores or corespotlightd is on top, wait

   Plug the Mac in and let Spotlight finish. Minutes for everyday changes, a few hours after an update or a big import. If it is still going after a day, add the folder that keeps changing to Spotlight Privacy in System Settings.

4. If kernel_task is on top, cool the Mac down

   Move it to a hard flat surface, quit whatever is heavy, unplug a hot charger for a bit. Throttling lifts a few minutes after the chip cools. Never try to quit kernel_task.

5. Free disk space if you are under 10 to 15 percent

   Trash, Downloads, old iOS backups, unused big apps, media to an external drive. Restart and let macOS thin its own snapshots. Nothing from inside Library by hand.

6. Restart

   A restart clears leaked memory, drops swap to zero, and ends any process that got stuck. If you have not restarted in weeks, do this before anything else on the list and see if the problem is gone.

7. Update macOS and the apps that are busy

   Leaks and runaway loops get fixed in point releases. Software Update in System Settings, then update the app that keeps turning up at the top of the list.

What does not help (and sometimes makes it worse)

Cleaner apps. They remove caches, logs and "junk". None of that is what makes a Mac slow, and the caches come straight back because apps rebuild them, which is itself a small amount of work your Mac now has to redo. Several of them also install background agents that run all the time. A MacRumors poster who tried one found "it proposed to delete stuff that clearly shouldn't be deleted". The long-running Apple Community volunteer John Galt calls cleaning apps "the quickest way to ruin a perfectly good Mac." If you want the full argument, the cleaner comparison page has it.

"RAM boosters" and memory cleaners. These force macOS to drop cached data so the "free" number goes up. That cached data was there because macOS expected to need it, so you have just made the next thing you click slower. Memory pressure, the number that matters, is unchanged or worse. The memory cleaner apps page explains why.

Deleting caches by hand. Same problem as the cleaner apps, with the added risk of removing something an app needed. The should I clear cache page covers the one or two cases where it genuinely helps (a single misbehaving app) and the many where it does nothing.

Reinstalling macOS. It does not change the workload that made your Mac slow. If the cause is a leaking browser, a hot room or a full disk, you will have spent an afternoon and ended up in the same place. Reinstalling is for a Mac that is genuinely broken, not one that is busy.

Turning off visual effects, Spotlight, or Time Machine. These are commonly listed tips. On any Mac from the last decade the visual effects cost nothing you can measure. Spotlight indexing finishes and then costs nothing. Time Machine runs its backups in the background at low priority. Turning them off trades real features for no measurable speed.

Which process is it? Look it up

If Activity Monitor shows a name you do not recognize at the top of the list, type it here. You get what it is, whether it is normal for it to be busy, and whether it is safe to quit.

The general rule: names you recognize are apps, and quitting them is always safe. Names ending in "d" running as root are macOS daemons, and quitting them does nothing useful because launchd restarts them, or does something unhelpful like logging you out. For anything in between, the process pages on this site say what normal looks like and when to worry. Safe to Quit, the Mac app this site belongs to, does the same job without opening Activity Monitor: it watches each process over hours and points at the one that is actually making the Mac hot, loud or slow.

When a slow Mac is actually a hardware problem

Rarely, but it happens. The signs that point away from software and toward hardware are: the Mac is slow in Safe Mode with nothing running, the fan screams with Activity Monitor showing nothing above a few percent, the disk shows SMART errors in Disk Utility, or the battery is swollen enough to press on the trackpad. An Intel Mac from before 2018 with a spinning hard drive or a Fusion Drive is a special case: those drives are the bottleneck for everything, and an SSD upgrade turns an unusable machine into a fine one.

For everything else, including "it is about the same as my old Intel Mac" complaints that turn up on Apple Community about brand new Apple silicon machines, the cause is nearly always one of the five above. One poster with a "2023 MacBook Pro M2 / 16GB / 256GB" called it "very dead slow" on the Apple Developer Forums. That combination of a small disk and a developer workload is cause 5 and cause 3 stacked on top of each other, and it clears up when space is freed and indexing settles.