Mac Slow After a macOS Update? Find Out What Is Still Running
A Mac can feel slower just after a macOS update because work continues after the restart. The update can trigger Spotlight indexing, while Photos or a cloud app may have data to sync. The timing alone does not prove that macOS is the cause: an app that no longer works well, a login item, or a nearly full startup disk can produce the same symptom. Check what is happening before clearing caches or changing system settings.
Compare the same task
Pick one task that has become slow, such as opening a local folder, launching an app, or exporting a file. Note when the pause happens and whether the whole Mac or only that app responds slowly. Open Activity Monitor while the problem is visible and check the CPU, Memory, and Disk tabs. If only an online action stalls, check the app's connection as well. One reading taken after the Mac feels normal will not explain the earlier pause.
Check whether background work is moving forward
Apple says Spotlight indexing can run after a software update. Open Spotlight and look for its indexing progress indicator, then compare it with mds or mdworker activity in Activity Monitor. Indexing may take hours or days depending on the data, so a fixed waiting period is not a useful test. If the work gradually settles and the same task becomes responsive again, it was likely temporary. If CPU and disk activity keep returning without progress, check the changing folder or volume before considering an index rebuild.
If Photos is busy, open its Library, choose All Photos, and scroll to the bottom. Apple documents a library status showing the last iCloud update, current syncing, and items that could not sync. A paused or failed status needs its stated cause checked; switching iCloud Photos off is not a general speed fix. For other cloud apps, use their own sync status instead of assuming that network traffic means useful progress. Let finite work finish with the Mac powered and connected, and observe whether the workload improves.
If the slowdown persists, isolate one cause
Check System Settings › General › Storage for available space on the startup disk. Apple lists insufficient space among the causes of a slow Mac. If the task needs room to write or swap, move or remove files you recognize and recheck that task; do not delete an unfamiliar System Data folder because its category is large.
Next, look at Activity Monitor's Memory Pressure and the process list during the pause. If a recently updated app alone is unresponsive or repeatedly dominates CPU, quit it and check the developer's compatible version. If the trouble begins at login, review System Settings › General › Login Items & Extensions. Apple describes testing login items by removing them and adding them back one at a time. Record the original items first, change one known item at a time when possible, and confirm that its app still works. A slowdown isolated to one app calls for that app's update or support, not a system-wide cleanup.
Retest before changing anything else
Run the original task again under similar conditions. Compare its delay and the CPU, memory pressure, disk activity, and sync status you saw earlier. If the task is responsive and the finite background work has subsided, stop there. If it is still slow with no clear owner, restart once to rule out a stuck session, then repeat the comparison. Persistent disk errors, an app that cannot open, or missing search results deserve their own diagnosis; a blanket Spotlight rebuild, cache purge, or SMC reset is not a routine post-update step. For a broader resource-by-resource investigation, see why a Mac runs slowly.