Mac startup apps: how to stop things opening at login
You log in, and for the next ninety seconds your Mac isn't yours. Slack bounces, an updater checks in, a cloud drive starts syncing, and three apps you don't remember installing put icons in the menu bar. Mac startup apps accumulate quietly — most of them were never a decision you made, just a checkbox in an installer you clicked through. The good news is that macOS finally shows you nearly all of them in one place. The catch is that it's two lists, they behave differently, and only one of them lets you remove anything.
Where Mac startup apps actually live
Open Apple menu → System Settings → General → Login Items & Extensions. On current macOS you get two sections that look similar and aren't:
| Section | What's in it | What you can do |
|---|---|---|
| Open at Login | Full apps, documents, folders and servers that launch when you log in | Add with +, remove with − |
| App Background Activity | Helpers, updaters and daemons installed by apps | Toggle each on or off — you can't remove them |
On macOS Ventura through Sequoia the second section was labelled Allow in the Background; it's the same list under a clearer name. Below both sits the Extensions list — Finder extensions, Quick Look plugins, share sheet items and so on — which is worth a scroll through once, but isn't what's slowing your login.
The first list is the one you own. Click an item, click −, done. It takes effect at the next login and nothing else changes.
The list you can't delete from
App Background Activity is where most of the surprise lives. When you install something that ships a helper — a menu-bar agent, an auto-updater, a sync daemon — macOS registers it here and, since Ventura, tells you about it with a notification. You get a switch per item, not a delete button, because the item belongs to an app that's still installed. Turn the switch off and the helper stops launching; the entry stays, greyed, as a record of what's there.
Two things worth knowing before you start flipping switches:
- Names are often useless. You'll see bundle identifiers and vendor names rather than the app you recognise. Expand the group under a vendor's name to see which app it belongs to before deciding.
- Some of them are the app. Turning off a backup tool's background agent doesn't slim your login, it stops your backups. If you can't tell what an item does, leave it and uninstall the parent app instead — that removes the entry properly.
The four other ways an app launches itself
Not everything that greets you at login is a login item. Before you go hunting through folders, rule these out:
- The app's own preference. Most well-behaved apps have a "Launch at login" checkbox in their own settings. Ticking or unticking it usually writes the Open at Login entry for you, so this is the cleanest place to change it.
- The Dock. Right-click any running app's Dock icon → Options → Open at Login. It's a checkbox, and it's the fastest way to add something deliberately — or to discover you added it by accident months ago.
- Reopen windows when logging back in. The checkbox in the restart/shut down dialog. When it's ticked, macOS relaunches whatever was running before — which looks exactly like a startup-app problem but is really a session being restored. macOS remembers how you last set it, so one stray tick keeps applying until you untick it. There's a related switch in System Settings → Desktop & Dock → Close windows when quitting an application for the per-app version of the same behaviour.
- Launch agents on disk. The old mechanism: property lists in
~/Library/LaunchAgents,/Library/LaunchAgentsand/Library/LaunchDaemons. Anything that predates the modern API, or was installed by a package rather than an app, can hide here. Read the files before you touch them — theLabelandProgramArgumentskeys tell you who owns each one.
When an item keeps coming back
A stubborn entry almost always means the parent app is still installed and re-registering itself on every launch. The fix is to uninstall the app properly (use its own uninstaller if it has one) rather than to fight the list.
If the list itself looks broken — ghost entries for apps you deleted,
toggles that don't stick — the last-resort reset is sudo sfltool resetbtm followed by a reboot, which clears macOS's background task
database. Treat it as a genuine last resort: every legitimate background
item gets re-registered afterwards and you'll be re-approving
notifications for a while. Try a normal restart first; a surprising
number of stuck toggles are just a settings pane that needs relaunching.
Build a startup set on purpose
Once the list is clean, the useful question isn't "how few can I get away with" — it's which apps you'd otherwise launch by hand within five minutes of sitting down. Those have earned a slot. Everything else can wait until you need it.
For most people the keepers are: whatever holds your passwords, your clipboard history, your backup or sync agent, and one or two menu-bar utilities you touch constantly. That's the honest test — frequency, not category. A window manager you use fifty times a day belongs at login; a video converter you use twice a year does not. (Ours sit in that first group by design: Let's Tile and Let's Switch live in the menu bar, launch at login, and stay out of the way otherwise — no Dock icon, no account, no telemetry.)
One thing a tidy login list won't fix: your apps come back, but their windows don't come back arranged. macOS restores each app's own windows, not your layout across displays, which is why a clean boot still means a minute of dragging. The keyboard fix is in our guide to saving and restoring window layouts.
Frequently asked questions
Do fewer login items make my Mac boot faster? They make the login faster, which is the part you experience. Startup itself is mostly firmware and kernel work you can't influence. Cutting five heavy items from Open at Login is noticeable; cutting one small menu-bar utility is not.
Why is an app in App Background Activity when I never opened it? Because its installer registered a helper — usually an updater or a sync agent. That's normal, not malware. If you don't recognise the vendor at all, search the name before disabling it.
I removed it from Open at Login and it still launches.
Check the app's own settings first, then the "Reopen windows when
logging back in" checkbox, then ~/Library/LaunchAgents. One of those
three explains nearly every case.
Is it safe to turn everything off in App Background Activity? No. You'll break backups, sync, VPNs and auto-updates. Go one at a time, restart, and see what you miss.
Where did "Allow in the Background" go? Nowhere — it was renamed App Background Activity. Same list, same per-item switches.
More macOS workflow guides in the Let's Suite blog.