Mac Startup Items: How to Manage Login Items on macOS

macOS supports two categories of automatic startup entries. Login items are applications or executables that open when a user signs in. These are managed through System Settings > General > Login Items and appear as toggleable entries in a straightforward list.

Launch agents and launch daemons are property list (plist) files stored in specific Library directories. Launch agents run in the context of a logged-in user, while launch daemons run at the system level regardless of whether anyone has signed in. Both types load automatically unless explicitly disabled.

Many applications register a launch agent during installation without notifying the user. Over time, these background processes accumulate and consume resources at every boot, even if the parent application is never opened.

The Login Items panel in System Settings shows applications you or an installer added to the startup sequence. Each entry has a toggle switch that enables or disables it without deleting the configuration entirely.

Launch agents at the user level reside in ~/Library/LaunchAgents. System-wide launch agents live in /Library/LaunchAgents, and system-wide daemons are stored in /Library/LaunchDaemons. Opening these folders in Finder (Go > Go to Folder) reveals the plist files that define each background process.

Terminal provides another method. Running launchctl list displays all loaded launch agents and daemons with their process IDs and labels. This command shows entries that may not appear in System Settings because they were registered directly through launchctl rather than through the GUI.

System Settings offers the simplest removal method. Open System Settings > General > Login Items, select the application, and click the minus button to remove it. Toggling the switch off disables the item without removing it, allowing you to re-enable it later.

Launch agents require manual removal. Navigate to ~/Library/LaunchAgents or /Library/LaunchAgents in Finder and move the unwanted plist file to the Trash. Before deleting, run launchctl unload followed by the file path to stop the agent gracefully. Removing a plist without unloading it first leaves the process running until the next reboot.

Exercise caution when modifying LaunchDaemons. System-level daemons often support critical macOS functionality. Only remove files you can identify by their bundle identifier label, such as com.adobe.AdobeCreativeCloud or com.spotify.webhelper, which belong to third-party applications.

Every startup item competes for CPU cycles and memory during login. macOS must load each application into RAM, initialize its frameworks, and establish network connections. When a dozen apps launch at once, the CPU can sustain 80% or higher utilization for several minutes after the desktop appears.

RAM consumption from login items persists throughout the session. Cloud sync agents (Dropbox, Google Drive, OneDrive), messaging apps (Slack, Teams), and creative tool helpers (Adobe Creative Cloud) each consume 100 MB to 500 MB of memory. On a Mac with 8 GB of RAM, five background apps can consume a quarter of available memory before the user opens anything.

Disk I/O spikes during login as macOS reads application binaries from the SSD. Excessive startup items cause the desktop to appear responsive while background loading continues, creating a misleading impression that the Mac has finished booting when it is still under heavy load.

MoniThor begins monitoring the moment macOS loads the menu bar. CPU percentage and memory pressure appear instantly, giving you a real time view of how startup items affect system resources during the login sequence.

The top processes panel identifies which applications consume the most CPU and RAM after boot. Sorting by CPU reveals login items that spike resource usage during initialization, while sorting by memory shows which background agents claim the largest share of available RAM.

Per core utilization bars distinguish between P-Core and E-Core load, making it clear whether startup items are triggering performance cores or running efficiently on efficiency cores. Color coded thresholds shift from green to yellow to red as resource consumption increases.

Application helper agents are the most common safe candidates for removal. These include updater services for apps like Adobe Creative Cloud, Spotify, Microsoft AutoUpdate, and Google Software Update. Removing them simply means those apps will not check for updates automatically; you can update manually instead.

Cloud sync agents for services you no longer use (Dropbox, OneDrive, Box) are safe to remove entirely. If you still use the service but do not need instant sync, disabling the login item reduces memory usage while allowing you to open the app manually when needed.

Never remove plist files with an com.apple prefix. These belong to macOS system services and removing them can cause instability, prevent features from working, or trigger repeated system prompts. If you are unsure about a launch agent, search its label online before deleting it.