Scenarios & devices

How to Speed Up an Old, Slow Mac in 2026: 14 Fixes Before You Buy a New One

If your Mac has slowed to a crawl, you are not alone — and the culprit is almost never the hardware itself. Whether you're running macOS Sequoia on a 2018 Intel MacBook Pro or Tahoe on an M1 Mac mini, learning how to speed up an old slow Mac is mostly a matter of reclaiming the resources that years of everyday use have quietly consumed. The 14 fixes below are ordered from quickest to most thorough. Try them in sequence before you reach for your credit card.

1. Check What's Actually Eating CPU and RAM Right Now

Before touching anything, open Activity Monitor (in /Applications/Utilities/) and sort by CPU %, then by Memory. Look for processes you don't recognize or apps that are consuming well above their expected share. This five-minute triage tells you whether you have a software problem, a runaway process, or a genuine hardware constraint.

  • High memory pressure (red bar in the Memory tab) = your Mac is paging heavily to disk — a strong sign you need to free RAM or add storage breathing room.
  • Persistent CPU spikes from mds_stores = Spotlight is still indexing; give it a few hours after a major app install.
  • A runaway browser helper or mediaanalysisd = restart the offending process first before doing anything else.

2. Reclaim Disk Space — the Single Fastest Win

macOS needs roughly 10–15 % of your SSD free to operate efficiently. When that buffer shrinks, virtual memory swapping slows everything down. Start with the folders that accumulate the most cruft silently.

Caches

User-level caches live in ~/Library/Caches/. System-level caches live in /Library/Caches/. Both are safe to clear — apps rebuild them on next launch. For a deeper look at what these files are and which ones are safe to remove, see our guide on what cache files are on a Mac.

Developer Artifacts

Developer tools leave enormous build caches that grow unbounded:

  • ~/Library/Developer/Xcode/DerivedData/ — Xcode derived data; safe to delete entirely between builds.
  • ~/.cargo/registry/ and ~/.cargo/git/ — Rust package cache.
  • ~/.m2/repository/ — Maven local repository.
  • ~/Library/Developer/CoreSimulator/Devices/ — iOS simulator runtimes; each can be several gigabytes.

A tool like Crumb can audit all of these at once and show what's safe before you delete, so you're not guessing which folders are expendable.

Folder Size Quick Reference

Folder Typical size Safe to delete?
~/Library/Caches/ 1–20 GB Yes — apps rebuild
~/Library/Developer/Xcode/DerivedData/ 5–50 GB Yes — Xcode rebuilds on next build
~/.cargo/registry/ 1–10 GB Yes — Cargo re-downloads on next build
~/.m2/repository/ 1–15 GB Yes — Maven re-downloads on next build
~/Library/Developer/CoreSimulator/Devices/ 5–30 GB Yes — re-download specific runtimes as needed
~/Downloads/ Varies Review manually
/Library/Caches/ 0.5–5 GB Yes — requires admin password

3. Trim Login Items and Launch Agents

Every app that launches at login costs you boot time and background RAM. On macOS Ventura and later (Sequoia, Tahoe), go to System Settings → General → Login Items & Extensions. Disable anything you don't need running all day. Pay special attention to the Allow in the Background section — these are Launch Agents that run even when the app's window is closed.

For a manual audit, check:

  • ~/Library/LaunchAgents/ — per-user background processes
  • /Library/LaunchAgents/ — system-wide background processes installed by apps
  • /Library/LaunchDaemons/ — privileged system daemons

Be cautious here: some daemons are critical to system function. Only disable items you can clearly attribute to a third-party app you no longer use.

4. Free Up RAM Without Rebooting

Quitting unused apps and browser tabs is the obvious step. Beyond that:

  1. Open Terminal and run sudo purge — this flushes the disk cache back to free memory. Useful before a memory-intensive task like video export.
  2. Check for browser extensions — each extension is a separate process. Prune ruthlessly.
  3. If you have 8 GB unified memory on Apple Silicon and frequently hit high memory pressure, you are a candidate for an upgrade — but exhaust the software fixes first.

5. How to Clear and Rebuild the Spotlight Index (Step-by-Step)

A corrupt or oversized Spotlight index causes persistent high CPU from mds and mds_stores. Here's how to reset it:

  1. Open System Settings → Siri & Spotlight → Spotlight Privacy.
  2. Click + and add your startup disk (usually named Macintosh HD).
  3. Wait 10 seconds, then select the disk and click to remove it.
  4. macOS will begin reindexing automatically. CPU will spike temporarily, then settle.

Alternatively, run this in Terminal (replace Macintosh HD with your volume name if different):

sudo mdutil -E /

6. Remove Duplicate Files and Old Downloads

Duplicate photos, downloaded installers, and old disk images are silent space thieves. The Downloads folder is the usual worst offender — .dmg files left behind after app installation can each be hundreds of megabytes. Our guide on how to find duplicate files on a Mac for free covers both manual and tool-assisted approaches.

7. Manage iCloud Optimized Storage

If you use iCloud Drive with Optimize Mac Storage enabled (System Settings → Apple ID → iCloud → iCloud Drive → Optimize), macOS automatically offloads older files to iCloud when disk space is low. This is beneficial — but if your internet connection is slow, opening those files causes noticeable stalls. Consider disabling optimization if you have adequate local storage and a slow connection.

8. Update macOS and All Apps

This sounds generic, but it is genuinely important. Apple Silicon performance optimizations, memory management improvements, and Metal rendering fixes ship in point releases. Running a two-year-old version of macOS on modern hardware means you are leaving performance on the table. Check System Settings → General → Software Update and enable automatic updates for security responses at a minimum.

9. Reset NVRAM and SMC (Intel Macs Only)

On Intel Macs, stale NVRAM entries can cause slow boot times and erratic fan behavior. To reset NVRAM: shut down, then power on and immediately hold Option + Command + P + R for about 20 seconds. The Mac will appear to restart twice.

To reset the SMC on Intel MacBooks with a T2 chip: shut down, hold Control + Option + Shift on the left side for 7 seconds, then add the power button and hold all four for another 7 seconds.

Apple Silicon Macs do not have NVRAM or SMC in the same sense — a normal restart achieves the equivalent reset.

10. Check Storage Health

An aging SSD with many reallocated sectors will appear slow even after cleaning. Open Terminal and run:

diskutil info disk0 | grep SMART

A result of SMART Status: Verified means the drive is healthy. Failing means you should back up immediately and plan a drive replacement or machine replacement.

11. Reduce Visual Effects

On older Intel Macs with integrated graphics, macOS animations consume measurable GPU time. Go to System Settings → Accessibility → Display and enable Reduce Motion and Reduce Transparency. The interface becomes more utilitarian, but window switching and Mission Control will feel snappier on older hardware.

12. Uninstall Apps You No Longer Use

Dragging an app to the Trash leaves behind preference files, support files, and sometimes Launch Agents in ~/Library/LaunchAgents/. These remnants do not slow you down dramatically on their own, but they accumulate over years. For thorough removal, see our guide on how to completely uninstall apps on a Mac.

13. Audit node_modules and Other Project Dependency Caches

If you do web development, node_modules directories can collectively consume tens of gigabytes across dormant projects. Run this in Terminal from your projects root to find the biggest offenders:

find ~/Projects -name node_modules -type d -prune | xargs du -sh 2>/dev/null | sort -rh | head -20

Delete node_modules folders for projects you are not actively working on — npm install or pnpm install rebuilds them in seconds when you return.

14. Consider a RAM or Storage Upgrade (Intel Macs)

On Intel MacBook Pros and Mac minis from 2019 and earlier, RAM is upgradeable on some models and the SSD is replaceable. Adding RAM is the single highest-impact hardware upgrade for a machine that frequently hits memory pressure. Apple Silicon Macs have unified memory soldered to the SoC, so software optimization is the only path short of buying new hardware — which makes the 13 steps above even more important for M-series users on tight budgets.

A Note on Baseline Maintenance

Most of the slowdowns described here are the result of neglect rather than hardware aging. A Mac that gets a cache clear, login-item audit, and duplicate purge twice a year will stay fast for many more years than one that is left to accumulate cruft unchecked. The fixes above are all reversible and carry no risk of data loss when followed as described.

Reclaim your disk in one click

Crumb audits your whole Mac, tells you what's safe to delete, and frees the space in seconds — private, local, and Apple-notarized.

Download Crumb for macOS

Frequently asked questions

Is it safe to delete the contents of ~/Library/Caches/?
Yes. The ~/Library/Caches folder holds temporary files that apps generate themselves and rebuild as needed. Deleting its contents will not cause data loss. Some apps may take slightly longer to launch the first time after the cache is cleared, but they will function normally.
How much free space should a Mac have to run well?
Apple recommends keeping at least 10-15% of your total SSD capacity free. On a 256 GB drive that means roughly 25-40 GB free at all times. When free space drops below this threshold, macOS must work harder to manage virtual memory and temporary files, which causes noticeable slowdowns.
Will clearing Xcode DerivedData delete my source code or project files?
No. DerivedData contains only compiled build artifacts — not your source code or project settings. Deleting ~/Library/Developer/Xcode/DerivedData/ simply means Xcode will need to recompile your project the next time you build. Your actual project files are wherever you saved them.
Do these fixes work on both Intel and Apple Silicon Macs?
Most fixes apply to both architectures. Steps like clearing caches, removing duplicate files, trimming login items, and deleting developer artifacts work identically on Intel and Apple Silicon. The NVRAM and SMC reset steps in Fix 9 apply only to Intel Macs; Apple Silicon handles equivalent resets through a standard shutdown and restart.
How long does Spotlight reindexing take after a reset?
On a typical 512 GB SSD with a moderate amount of data, Spotlight reindexing takes 30 minutes to a few hours. CPU usage from mds_stores will be elevated during this period, which is normal. You can continue using your Mac while indexing completes, though Spotlight search results will be incomplete until it finishes.