If your Mac is taking longer than usual to start up, the most common causes are too many login items, a full startup disk, or corrupted system files. You can fix slow boot on Mac without reinstalling macOS — a few targeted software changes are usually enough.
What's Actually Causing Your Mac to Boot Slowly?
Before jumping into fixes, it helps to understand what's happening during startup. When your Mac boots, it loads the operating system, mounts storage volumes, runs background services, and launches any login items you've added over time. Any one of these steps can become a bottleneck.
Software-Side Causes
- Too many login items and silently running background agents
- Corrupted system caches or damaged preference files
- Spotlight indexing a large library or a newly connected drive
- FileVault encryption adding overhead on older or slower storage
- Third-party kernel extensions that conflict with the current macOS version
- Mac set to boot from the wrong startup disk (an external drive, for example)
Hardware-Side Causes
- Startup disk with less than 10–15% free space
- Aging hard drive or SSD with early signs of failure
- Aftermarket SSD installed via NVMe adapter — these can develop TRIM conflicts on Monterey and later
- Low RAM forcing macOS to write heavily to a swap file during startup
Intel Mac vs. Apple Silicon — What's Different
This distinction matters because several fixes in this guide apply only to Intel-based Macs. Resetting NVRAM and SMC, for example, are Intel-only procedures. Apple Silicon Macs (M1, M2, M3, and later) handle boot configuration differently at the firmware level, and those reset steps simply don't exist in the same form.
Also worth noting: the location of Login Items changed with macOS Ventura. On Monterey and earlier, it's System Preferences → Users & Groups → Login Items. On Ventura and later, it's System Settings → General → Login Items. Both are referenced throughout this guide.
Quick Reference: Cause, Fix, and Time Estimate
Use this table to identify your likely cause and jump directly to the right fix.
|
Likely Cause |
First Fix to Try |
Intel Mac |
Apple Silicon |
Est. Time |
|
Too many login items |
Disable in System Settings |
✓ |
✓ |
5 min |
|
Startup disk nearly full |
Free up storage |
✓ |
✓ |
10–30 min |
|
Corrupted filesystem |
First Aid in Disk Utility |
✓ |
✓ |
5–15 min |
|
Boot configuration glitch |
Reset NVRAM/PRAM |
✓ |
✗ |
2 min |
|
Power or thermal management issue |
Reset SMC |
✓ |
✗ |
2 min |
|
Software or extension conflict |
Boot into Safe Mode |
✓ |
✓ |
5 min |
|
Suspected hardware failure |
Run Apple Diagnostics |
✓ |
✓ |
10 min |
|
Corrupted macOS system files |
Reinstall macOS via Recovery |
✓ |
✓ |
30–60 min |
|
Aftermarket SSD conflict |
Check SSD brand and controller |
✓ |
Rare |
10 min |
|
FileVault on slow storage |
Disable FileVault or upgrade drive |
✓ |
✓ |
Varies |
Step 1: How to Fix Slow Boot Mac — Quick Fixes First (Safe, Reversible)
Start here. These fixes resolve the majority of slow boot issues without any risk to your data.
Check and Remove Login Items
Login items are apps or background helpers that launch every time you start your Mac. Over months and years of installing software, these accumulate — and many run silently without you realising they're there.
- Ventura and later: System Settings → General → Login Items
- Monterey and earlier: System Preferences → Users & Groups → Login Items
Remove anything you don't recognise or actively need at startup. Communication apps, cloud sync tools, and printer utilities are common culprits. When in doubt, disable rather than delete — you can always re-enable.
In practice, users who have owned their Mac for more than two years often find five to ten login items they never knowingly added.
Free Up Startup Disk Space
macOS needs breathing room on the startup disk. When free space drops below roughly 10–15% of total capacity, the system struggles to manage virtual memory, temporary files, and caches during boot.
Check your storage: Apple menu → About This Mac → Storage (or System Settings → General → Storage on Ventura+).
Quick wins: empty the Trash, delete unused large apps, offload video files to external storage, and clear Downloads.
Run First Aid in Disk Utility
Disk Utility's First Aid checks your startup volume for filesystem errors — corrupted directories, permission issues, and inconsistent metadata that can stall the boot process.
Open Disk Utility (Applications → Utilities → Disk Utility), select your startup volume from the left sidebar, and click First Aid. If your Mac won't boot far enough to do this normally, restart into Recovery Mode (Command + R on Intel; hold the power button on Apple Silicon) and run First Aid from there.
Boot into Safe Mode
Safe Mode is the most reliable way to confirm whether a software conflict or third-party extension is causing your slow boot. In Safe Mode, macOS disables all third-party kernel extensions, skips most login items, and clears certain system caches.
- Intel Mac: Shut down fully, then power on and immediately hold the Shift key. Release when the login screen appears.
- Apple Silicon Mac: Shut down, hold the power button until "Loading startup options" appears, select your startup volume, then hold Shift and click "Continue in Safe Mode."
If your Mac boots noticeably faster in Safe Mode, a login item or extension is the cause. Re-enable your login items one at a time to identify which one is responsible.
Check Your Startup Disk Selection
This is one of the most overlooked causes of slow boot. If an external drive is set as the default startup disk, your Mac will attempt to boot from it — and fail, or stall, before falling back to the internal drive.
Check it: System Settings (or System Preferences) → Startup Disk. Make sure your internal Macintosh HD is selected.
Step 2: Intel Mac-Specific Fixes
These two resets apply only to Intel-based Macs. Skip this section if you're on Apple Silicon.
Reset NVRAM/PRAM
NVRAM (non-volatile RAM) stores a small set of system preferences: startup disk selection, display resolution, time zone, and kernel panic logs. A corrupted NVRAM entry can cause boot delays or misdirected startup attempts.
To reset: shut down your Mac, then press the power button and immediately hold Option + Command + P + R for about 20 seconds (until you hear the startup chime a second time, or the Apple logo appears and disappears twice on newer Intel models). Release the keys and let your Mac start normally.
This is a harmless reset. Your files are not affected.
Reset SMC
The SMC (System Management Controller) handles power delivery, thermal management, fan behaviour, and startup sequencing. A glitchy SMC can cause your Mac to hang during early boot stages before macOS even begins loading.
The reset method varies by model:
- MacBooks with a non-removable battery (2017 and later): Shut down, hold Control + Option + Shift (left side) for 7 seconds, then add the power button and hold all four for another 7 seconds. Release and start normally.
- Mac desktops: Shut down, unplug for 15 seconds, then reconnect and start.
- MacBooks with T2 chip (2018 and later): Shut down, hold Control + Option + Shift for 7 seconds, then add the power button for another 7 seconds.
If you're unsure which category your Mac falls into, check Apple's support documentation for your specific model.
Step 3: Deeper Diagnostics
If the quick fixes haven't resolved the issue, these steps help identify the specific cause.
Run Apple Diagnostics
Before assuming software is the problem on an older Mac, run Apple Diagnostics to check for hardware failures. It tests memory, storage, and other components and returns error codes if something is genuinely failing.
- Intel Mac: Shut down, then power on and immediately hold the D key.
- Apple Silicon Mac: Shut down, hold the power button until startup options appear, then hold Command + D.
The test takes about five minutes. If it returns any error codes related to storage, that changes your fix path — a failing drive needs replacement, not software repairs.
Use Verbose Boot to See Where Your Mac Hangs
Verbose mode shows the raw boot log on screen, line by line, so you can see exactly where the startup process stalls. This is useful when you suspect a specific service or kernel extension is the problem.
Intel only: Shut down, power on, and immediately hold Command + V. Watch the output for lines where the display pauses for more than a few seconds.
What's often overlooked is that hangs near the end of the verbose output — after most drivers have loaded — typically point to a login item, a network mount that can't connect, or a problem with the startup disk itself. Hangs early in the process are more likely to indicate a kext (kernel extension) issue.
Inspect LaunchAgents and LaunchDaemons
Login items are only part of what launches at startup. LaunchAgents and LaunchDaemons are background processes that start silently — and they're installed by many third-party apps without being visible in the Login Items list.
They live in:
- User-level: ~/Library/LaunchAgents
- System-level: /Library/LaunchAgents and /Library/LaunchDaemons
Open Finder, press Command + Shift + G, and paste each path to browse. Files with .plist extensions correspond to individual background services. To disable one without deleting it, move it out of the folder temporarily and test boot speed. Permanently removing a LaunchAgent tied to an app you still use may require uninstalling the app and reinstalling it properly.
Check Drive SMART Status
Open Disk Utility, select your drive from the left sidebar (the physical drive, not the volume), and look at the bottom of the window for SMART Status. "Verified" means the drive's self-reported health is normal. "Failing" means the drive is detecting internal errors and should be replaced.
What's important to understand here: a full drive and a failing drive can produce similar symptoms (slow boot, sluggish performance), but they require completely different responses. Don't replace a drive that's just full, and don't waste time clearing space on one that's failing.
Terminal Diagnostic Commands
If you're comfortable with Terminal, these commands give you a faster read on what's happening:
# Check disk usage
df -h /
# Check memory pressure and swap usage
vm_stat
# List top CPU-consuming processes
ps aux | sort -nrk 3 | head -n 10
# View system boot log
log show –predicate 'process == "kernel"' –last boot
Run these after a slow boot while things are still sluggish. The boot log in particular can show you services that failed, timed out, or retried during startup.
Step 4: FileVault and User Account Issues
FileVault Encryption and Boot Time
FileVault encrypts your entire startup disk. At boot, macOS must authenticate your password and begin decrypting the volume before anything else can load. On modern Macs with fast SSDs, this adds only a second or two.
On older Macs with slower HDDs or early SSDs, it can add meaningful time to every boot. According to Wikipedia, the I/O performance penalty for FileVault 2 is around 3% on CPUs with the AES instruction set, but is noticeably larger on older processors without it — which explains why the impact is far more pronounced on pre-2013 Intel Macs.
To check if FileVault is on: System Settings → Privacy & Security → FileVault (Ventura+), or System Preferences → Security & Privacy → FileVault (Monterey and earlier).
Disabling FileVault is worth considering on older hardware if boot time is a genuine problem and you're not storing particularly sensitive data. The decryption process after disabling it can take several hours — your Mac needs to stay plugged in and on while it runs.
Boot Hang vs. Login Hang — These Are Different Problems
This distinction matters and is rarely explained clearly. The boot phase ends when you see the login screen. If your Mac reaches the login screen quickly but then hangs for a long time after you enter your password — that's a login hang, not a boot problem.
The fix paths diverge significantly. A login hang often means the user account has corrupted preferences or a login item that crashes repeatedly. A quick way to test: go to System Settings → Users & Groups and create a temporary new user account. Log into it. If startup is fast, your original user profile has the issue, not the macOS installation.
Step 5: When Nothing Else Works
Reinstall macOS from Recovery (Non-Destructive)
This reinstalls the macOS system files without touching your personal data, apps, or settings. It's the right call when you suspect system-level corruption but want to avoid the work of a full clean install.
- Intel: Restart and hold Command + R until the Apple logo appears.
- Apple Silicon: Hold the power button until "Loading startup options" appears → click Options → Continue.
In Recovery, select Reinstall macOS and follow the prompts. The process takes 30–60 minutes depending on your internet speed and Mac model.
Clean Install macOS
A clean install erases the startup disk entirely and installs a fresh copy of macOS. This is the most thorough fix available — it eliminates every software variable — but it also means rebuilding your setup from scratch.
Only go here if a non-destructive reinstall didn't help, or if the Mac has years of accumulated clutter you want to clear out anyway. Back up everything with Time Machine before starting
Hardware Upgrades That Fix Slow Boot for Good
Software fixes only go so far on older hardware. If your Mac is more than five or six years old and still running a spinning hard drive, the drive itself is the bottleneck — no amount of cleaning login items will change that.
Replace HDD with SSD
Switching from a hard disk drive to a solid-state drive is the single most impactful hardware upgrade for boot time on older Macs. Boot times that were sitting at two to three minutes can drop to under 30 seconds. The difference is not subtle.
As reported by TechCrunch, SSD read and write speeds far surpass those of conventional hard drives — a performance gap that directly translates into faster boot times on any machine making the switch.
This is only possible on Mac models with user-replaceable storage — primarily pre-2016 MacBook Pros, Mac minis, and iMacs with non-Fusion drives.
Upgrade RAM Where Possible
When RAM is full, macOS writes overflow to a swap file on the startup disk. At boot, reading back that swap data adds significant time. If Activity Monitor consistently shows high memory pressure, adding RAM (on models that allow it) reduces swap dependency and speeds up the entire startup process.
Aftermarket SSD Warning
If you've installed a third-party SSD using an NVMe adapter — common on 2013–2017 MacBook Air and Pro models — be aware that certain SSD controllers develop TRIM and garbage collection conflicts with Monterey and later versions of macOS. This shows up as stalling during verbose boot, particularly during kernel extension loading.
Brands that generally work well in this configuration: Intel, Crucial, Western Digital. Samsung drives in NVMe adapters have been more commonly reported as problematic in this specific setup.
Maintenance Habits That Keep Boot Times Fast
- Keep at least 15–20% of your startup disk free at all times
- Review login items and LaunchAgents every few months — app installations add them without asking
- Keep macOS and apps updated; compatibility issues between old extensions and new macOS builds compound over time
- Run Disk Utility First Aid quarterly, or after any unexpected shutdown
- Check FileVault status if boot times gradually creep up on older hardware
- Periodically boot into Safe Mode as a lightweight health check — if it's notably faster, something in your startup chain needs attention
Conclusion
Most slow Mac boot issues are software-caused — login items, a full disk, or corrupted caches. Start with the quick fixes, use Safe Mode to isolate extension conflicts, and escalate to NVRAM/SMC resets or reinstallation only if needed. Hardware upgrades make sense when the drive is genuinely the bottleneck.
Frequently Asked Questions
Q1: Why is my Mac taking so long to boot?
The most common reasons are too many login items, a startup disk with less than 10–15% free space, or corrupted system files. In some cases, a failing drive or an incompatible third-party extension is the cause. Start with login items and disk space — those fix the majority of cases.
Q2: Does resetting NVRAM fix slow boot on Mac?
It can, particularly if the boot delay is related to a startup disk configuration issue or a corrupted boot preference. It's a quick, harmless reset and worth trying on Intel Macs — but it doesn't apply to Apple Silicon and won't fix issues caused by login items or disk problems.
Q3: How do I know if my drive is failing or just full?
Open Disk Utility, select the physical drive (not the volume), and check SMART Status at the bottom of the window. "Verified" means the drive is healthy. "Failing" means it needs replacement. A full drive and a failing drive can look similar in symptoms but need completely different fixes.
Q4: Can FileVault slow down Mac boot time?
Yes, particularly on older Macs with HDDs or slower SSDs. FileVault decrypts the startup volume before macOS loads, which adds time on slower storage. On modern Macs with Apple's own SSD, the impact is minimal. Check System Settings → Privacy & Security → FileVault to see if it's enabled.
Q5: What is the difference between reinstalling macOS and doing a clean install?
Reinstalling macOS from Recovery replaces system files only — your data, apps, and settings stay intact. A clean install erases the entire startup disk first, then installs macOS fresh. The non-destructive reinstall is the right first option; a clean install is a last resort that requires a full backup beforehand.
