Managing startup applications on a Mac is one of the most effective ways to optimize boot times, reclaim system resources, and create a distraction-free workspace the moment you open your laptop. Whether you are troubleshooting a slow startup sequence or simply want your favorite productivity tools ready the instant you log in, understanding how to change startup applications on Mac gives you granular control over your macOS experience. This guide walks you through every native method—from the user-friendly System Settings to advanced command-line tools—ensuring you can curate the perfect launch environment for your specific workflow.
Understanding Login Items and Launch Agents
Before diving into the how, it helps to understand the what. macOS manages automatic launches through two primary mechanisms: Login Items and Launch Agents/Daemons.
Login Items are the most visible layer. These are standard applications (like Slack, Spotify, or your email client) that you explicitly tell the system to open when your user account logs in. They appear in the System Settings interface and are easy to toggle on or off.
Launch Agents and Launch Daemons operate deeper in the system. These are background processes (often helpers for apps like Adobe Creative Cloud, Microsoft AutoUpdate, or system utilities) defined by .plist property list files. They live in specific Library folders and can launch before you even reach the desktop. While the average user rarely needs to touch these, power users cleaning up bloatware or debugging persistent background processes will need to know where they hide.
Method 1: The Modern Way via System Settings (macOS Ventura and Later)
Apple redesigned the settings interface in macOS Ventura (13.Which means 0), moving startup management into the General pane. This is now the primary, most intuitive way to change startup applications on Mac for the vast majority of users Less friction, more output..
- Click the Apple menu () in the top-left corner of your screen.
- Select System Settings (or System Preferences on older versions).
- In the sidebar, scroll down and click General.
- On the right side, select Login Items.
You will see two distinct sections here: Open at Login and Allow in the Background Most people skip this — try not to..
Managing "Open at Login" Items
This list controls the apps that visibly launch and bounce in your Dock when you sign in.
- To remove an item: Select the application name in the list and click the minus (–) button below the list. The app will no longer launch automatically.
- To add an item: Click the plus (+) button. A Finder window will open. work through to your Applications folder, select the desired app (e.g., Notion, Things 3, Chrome), and click Open.
- To hide the window on launch: Check the Hide box next to an item. This launches the app silently in the background without bringing its main window to the foreground—perfect for menu bar utilities like Bartender or Rectangle.
Managing "Allow in the Background" Items
Introduced in macOS Ventura, this section lists apps that run background tasks (like syncing files, checking for updates, or monitoring hardware) without a visible Dock icon.
- Toggle the switch off for any app you don’t want consuming RAM or CPU cycles silently.
- Pro Tip: If you see an unfamiliar entry here, it is often a helper tool for a main app you installed. Disabling it usually won't break the main app, but it might stop automatic updates or sync features.
Method 2: The Legacy Route via Users & Groups (macOS Monterey and Earlier)
If you are running macOS Monterey (12.x), Big Sur, or Catalina, the interface lives in a different pane, though the functionality is nearly identical The details matter here. Still holds up..
- Open System Preferences from the Apple menu.
- Click Users & Groups.
- Select your user account from the left sidebar (ensure the lock icon is unlocked to make changes).
- Click the Login Items tab at the top of the window.
- Use the + and – buttons to add or remove applications exactly as described in the modern method above.
Note: The "Allow in the Background" feature does not exist in these older versions; background agents are managed solely via the Library folders described in Method 4.
Method 3: The Quick "Right-Click" Dock Shortcut
For managing a single application without opening System Settings, the Dock offers the fastest workflow. This method toggles the "Open at Login" status instantly.
- Locate the application icon in your Dock. (If the app isn't running, open it first, or drag it from the Applications folder to the Dock temporarily).
- Right-click (or Control-click) the icon.
- Hover over Options in the contextual menu.
- Look for Open at Login.
- If there is a checkmark next to it, the app is currently set to launch at startup. Click it to disable the behavior.
- If there is no checkmark, click it to enable the behavior.
This is incredibly useful for temporary changes—like enabling "Open at Login" for Zoom only on days you have back-to-back meetings, then disabling it afterward via the same menu.
Method 4: Advanced Cleanup via Finder (LaunchAgents & LaunchDaemons)
When you uninstall an application by dragging it to the Trash, it often leaves behind invisible helper files that still try to launch at startup. These orphaned .plist files can cause error messages, slow boots, or mysterious CPU usage. To truly change startup applications on Mac at the root level, you must visit the Library folders.
⚠️ Warning: Do not delete files unless you are certain they belong to software you have uninstalled. Deleting system-critical daemons can break macOS features Simple as that..
The Three Critical Folders
Hold the Option (⌥) key and click the Go menu in the Finder menu bar. Select Library (it only appears while holding Option). Inside, look for these folders:
~/Library/LaunchAgents(User-specific agents): Runs when you log in. Most third-party app helpers live here./Library/LaunchAgents(Global agents): Runs when any user logs in. Requires admin password to modify./Library/LaunchDaemons(System daemons): Runs at system boot (before login), usually as root. Requires admin password.
How to Clean Them
- Open the relevant folder.
- Sort by Date Modified or Name.
- Look for filenames matching apps you have deleted (e.g.,
com.adobe.ccxprocess.plist,com.google.keystone.agent.plist). - Drag suspicious
.plistfiles to the Trash. - Restart your Mac for changes to take effect.
Pro Tip: You can open a .plist file with a text editor (like VS Code or TextEdit) to see the Label key or ProgramArguments path, confirming exactly which app the file belongs to before deleting.
Method 5: Command Line Control with launchctl
For developers, sysadmins, or users automating setup scripts via dotfiles, the Terminal offers precise control via the launchctl utility. This interacts directly with launchd, the macOS service management framework.
List Current User Agents
To see everything currently loaded for your user session:
launchctl list
Look for entries with a PID (Process ID) number—these are currently running. Entries with
Entries with a PID number are actively running, while entries that show only a job identifier (no PID) are loaded into the system but currently idle. This distinction lets you quickly spot which launch agents or daemons are consuming resources at the moment.
Controlling launchd jobs from the Terminal
1. Unload (disable) a user agent
launchctl unload -w ~/Library/LaunchAgents/com.example.myapp.plist
The -w flag writes the change to the defaults database, ensuring the agent will not be re‑loaded on the next login.
2. Load (re‑enable) a user agent
launchctl load ~/Library/LaunchAgents/com.example.myapp.plist
If the file is already present in the system’s defaults, you can simply use launchctl load without the -w qualifier It's one of those things that adds up..
3. System‑wide daemons
To affect items in /Library/LaunchDaemons or /Library/LaunchAgents, prepend sudo:
sudo launchctl unload -w /Library/LaunchDaemons/com.apple.heavyweight.daemon.plist
You will be prompted for an administrator password; the change applies to all users on the machine Small thing, real impact..
4. Listing everything
launchctl list– shows only the agents that belong to the current user session.launchctl list -b– enumerates system daemons (those located in/Library/LaunchDaemons).launchctl list -a– combines user and system entries into a single view.
On macOS 12.3 and later, launchctl print offers a more detailed, machine‑readable snapshot:
launchctl print gui/0/com.example.myapp
This command reveals the exact Label, ProgramArguments, RunAtLoad, and KeepAlive keys, making it easier to verify configuration before unloading And it works..
5. Temporarily halting a service
If you need to stop a running daemon without removing it from the launch database, use:
launchctl stop com.example.myapp
To bring it back up:
launchctl start com.example.myapp
For jobs managed through a modern domain target, the equivalent is:
launchctl kickstart -k gui/$(id -u)/com.example.myapp
The -k flag terminates any existing instance before restarting it, which is useful when you have changed a plist and need the new configuration to take effect immediately. After any load, unload, stop, or start operation, verify the result with:
launchctl list | grep com.example.myapp
or, on newer macOS releases:
launchctl print gui/$(id -u)/com.example.myapp
If the job no longer appears, or if launchctl print returns “Could not find service,” the agent has been successfully removed from the current launchd domain.
Verifying and Troubleshooting
Before deleting a plist permanently, it is worth confirming that the associated app or service is not required for login, backup, synchronization, or hardware support. Temporarily unload the job, reboot, and observe whether anything breaks. If the system behaves normally, move the plist to a backup folder rather than deleting it outright:
mkdir -p ~/Desktop/LaunchAgents_Backup
mv ~/Library/LaunchAgents/com.example.myapp.plist ~/Desktop/LaunchAgents_Backup/
For system-level items, use the same approach with sudo and a backup location outside /Library/LaunchDaemons or /Library/LaunchAgents. Keep a note of the original path so the file can be restored if a needed service stops working.
If a launch agent reappears after deletion, check whether it is being recreated by an installer, an app update mechanism, a configuration profile, or a management tool such as MDM. In those cases, removing the plist alone is only a temporary fix; the parent application or policy must be adjusted to prevent recreation The details matter here..
Final Thoughts
Managing launch agents and daemons on macOS is ultimately about knowing what is loaded, what is running, and what will start automatically the next time you log in or boot. In practice, gUI tools such as Activity Monitor, System Settings, and third-party launchd inspectors make casual cleanup easy, while launchctl provides the precision needed for scripting and advanced troubleshooting. Whichever method you choose, work from a backup, verify the Label and ProgramArguments before deleting anything, and prefer unloading or disabling a job before removing its plist. With that disciplined approach, you can keep startup items lean, reduce unnecessary background activity, and maintain a macOS system that starts quickly and behaves predictably Most people skip this — try not to. But it adds up..
And yeah — that's actually more nuanced than it sounds.