Many macOS users unknowingly load apps during system boot, which can slow startup times and consume memory. Understanding which programs run automatically helps you streamline the login experience and keep your machine responsive.
This guide walks through common locations, system settings, and third-party tools that control what launches with your user session. You will see concrete examples and configuration options you can apply right away.
| Startup Location | Scope | How to View or Edit | Use Case |
|---|---|---|---|
| User Login Items | Single user only | System Settings → General → Login Items | Personal apps like messaging or mail |
| Launch Agents (~/Library/LaunchAgents) | Single user, loaded by launchd | Open in Finder or list with launchctl | Background daemons and helper tools |
| Launch Daemons (/Library/LaunchDaemons) | All users, system-wide | Files edited with admin privileges | Services that start before login |
| System Extensions and Login Plugins | Kernel or system extensions | Enabled via System Settings or defaults | Screen savers, Finder plugins |
How Login Items Work on macOS
Login items appear in System Settings and are managed per user account. When you unlock your screen, macOS starts these apps in the background so they are ready when you need them.
Each entry stores a path to the application or script and may include flags that control whether the app opens windows immediately or runs silently. You can reorder items so that critical tools launch first and less important tools launch later.
Removing unnecessary entries reduces CPU and disk activity at login, which often shortens the time before you can click and type comfortably.
Managing Login Items in System Settings
The quickest way to manage startup apps is through the Login Items section of System Settings. macOS displays a clear list where you can toggle visibility and change the order of execution.
Dragging items up or down adjusts the launch sequence, which matters when one program depends on another or when multiple utilities compete for resources. You can also minimize apps at login so they hide until you click their icon in the menu bar.
For shared Macs, remember that changes here only affect the current user account unless you configure other accounts separately.
Working with Launch Agents and Daemons
Launch agents and daemons are text files that tell launchd how to start background processes. Placing a properly formatted file in the right directory activates it without needing a graphical interface.
Launch agents run in the context of a specific user, while daemons launch early under the system root and are available to everyone. Because these files use property list syntax, a small syntax error can prevent the service from starting or even cause instability.
Backing up existing files before editing and testing changes with a fresh user account helps you avoid surprises on your main system.
Third-Party Utilities and Scripting
Power users often rely on tools that offer richer controls than System Settings, such as scheduling, dependency management, or detailed logging. These utilities can simplify enabling or disabling complex startup configurations.
Scripts placed in folders like ~/Library/Application Scripts can also launch at login when combined with agent files. This approach is common for utilities that need to coordinate multiple steps before showing a user interface.
Whatever method you choose, document your changes so you can reverse them later if performance or compatibility issues appear.
Refine What Starts with Your macOS Sessions
- Review login items monthly and remove anything you no longer need at startup
- Prefer launch agents over background apps when you only need a helper process
- Place critical tools earlier in the launch order if they affect other apps
- Document every change to launchd files and store backups in a versioned folder
- Test performance after major macOS updates to catch regressions early
FAQ
Reader questions
Why does my Mac feel slow after I add several apps to login items?
Each login item consumes memory and CPU cycles during startup, and too many apps can create contention for disk and network resources. Try removing nonessential items or moving some background helpers out of login items to speed up the initial login phase.
Can a misconfigured launch agent break macOS updates or system settings?
Yes, a malformed launch agent or daemon can interfere with system services, slow boot times, or cause apps to behave unexpectedly. Always validate plist files and keep a backup so you can revert changes that cause problems after an update.
Do login items still start if I enable FileVault on my Mac?
Login items run after your user session is unlocked, so they generally continue to work with FileVault enabled. However, items that depend on early authentication may fail if the necessary keys or network access are not yet available during the unlock process.
How can I prevent third-party apps from adding themselves to startup without my knowledge?
Review login items regularly in System Settings and audit new entries after installing software updates. You can also use parental controls or configuration profiles to restrict which applications are allowed to insert themselves into your login session.