Mac slow to start up? Trim login items & launch agents
A slow Mac startup usually means too many login items and leftover launch agents loading at boot. Here's how to trim them safely, starting in System Settings.
If your Mac is slow to start up and stays sluggish for the first few minutes, the usual cause isn't age. It's a startup queue. Every app set to open at login, plus a layer of background "launch agents" you never see, loads while the machine boots and keeps running afterward. Trimming your login items is the fastest fix for a slow Mac startup, and it's all reversible. Here's how, from the System Settings panel down to the folders where the stubborn ones hide.
Why login items make a Mac slow to start up
When you log in, macOS starts everything on your startup list at once: cloud sync agents, updater helpers, menu-bar apps, chat clients, note apps. Each one competes for the same CPU, disk, and memory in the first minute, which is exactly why the desktop appears quickly but the machine feels stuck right after.
The catch is that many of these are leftovers. Uninstall an app by dragging it to the Trash and its background helper is often left behind, still set to launch every single boot. Over a couple of years you accumulate a startup queue full of things you no longer use. Fewer items in, faster start out.
Step 1: prune your login items in System Settings
Start with the built-in panel; no Terminal needed.
Open Apple menu → System Settings → General → Login Items & Extensions. You'll see two sections that matter:
- Open at Login: the apps that launch a visible window or menu-bar item when you sign in. Select anything you don't need starting automatically and click the minus (–) button. This does not delete the app; it just stops it auto-starting. You can always relaunch it by hand.
- Allow in the Background: a list of helpers and agents that run quietly (updaters, sync engines, device tools). Toggle off any you recognize and don't need running constantly. Turning one off is fully reversible; flip it back on and the helper resumes.
If you see an entry with a vague developer name and no idea what it is, leave it for now rather than guessing. The goal is to cut the obvious dead weight, old apps and tools you've replaced, not to strip the machine bare.
Step 2: the deeper layer, launch agents and daemons
The Login Items panel doesn't show everything. Beneath it, macOS reads three folders full of small .plist files called launch agents and launch daemons. Each one tells the system to run a program automatically: an agent when you log in, a daemon at boot, before anyone signs in.
The three you can inspect are:
~/Library/LaunchAgents: agents for your user account./Library/LaunchAgents: agents that run for every user (note the leading slash: this is the top level of your drive, not your home folder)./Library/LaunchDaemons: system-wide daemons that run as root at boot.
These are the classic spot for orphans: uninstall an app and its launch agent .plist often stays behind, so macOS keeps trying to start a helper for software that's already gone. That's wasted boot time for nothing. If you're clearing these because you removed the app, do the whole job properly; see how to completely uninstall a Mac app, which walks through every folder an app leaves behind.
To look inside, open Finder, choose Go → Go to Folder, and paste one of the paths above. Each .plist is named for what it launches (usually a com.vendor.something.plist bundle ID), so you can tie it back to an app. Only remove ones you can clearly match to software you've already deleted, and never touch anything under /System/Library, which is Apple's own and protected by the system. When you're unsure whether a file is safe to move, err toward leaving it; our guide to what you can safely delete on a Mac covers where that line sits.
For power users: launchctl (optional)
If you prefer the command line, you can see what's actually loaded right now:
launchctl list
The third column is each job's label; match it to the .plist filenames above. The durable way to stop an orphaned one is to remove (or move out) its .plist file and reboot, rather than wrestling with launchctl bootout syntax that resets on the next login anyway. The Finder method above does the same thing more safely.
When the first startup after an update is the slow one
One important exception: if the Mac was fine and suddenly takes forever to start once, right after a macOS update, that's usually not your login items. Two normal things pile onto the first boot:
- FileVault adds an authentication step at the login window before the disk unlocks and the Mac finishes starting.
- Spotlight re-indexing kicks off after an update:
mdsandmds_storesrebuild the search index, hammering CPU and disk until they finish. That first boot and the hour after it feel heavy, then settle on their own.
If that's your situation, it typically fixes itself. For the full rundown, see why your Mac is slow after an update.
The honest bottom line
A slow Mac startup is almost always a startup-list problem, and the list is longer than the Login Items panel admits. Prune what you recognize in System Settings first; then, if you want the machine leaner, check the three LaunchAgents/LaunchDaemons folders for orphans from apps you've already removed. Both layers are reversible, and neither requires a "speed-up" app making promises it can't measure.
Doing the deep pass by hand means opening three hidden folders and guessing which cryptic .plist belongs to which app. Plumby traces every startup item and background agent back to the exact file it came from and the app that installed it, shows you the path before it touches anything, and lets you disable the dead weight on your command. It never goes near your documents, photos, or projects.
