Mac login items live in Apple menu > System Settings > General > Login Items & Extensions. To manage login items and background apps on Mac, review Open at Login, App Background Activity, and Extensions as separate lists. Identify the owner and purpose of each item, temporarily suppress login items with Shift when diagnosing startup, and disable only one nonessential item at a time before signing in again or restarting.

Key Takeaways

Open at Login, background activity, and extensions have different jobs and should not be treated as one startup list.

Identify an item's publisher, parent app, and purpose before changing it.

Holding Shift during login can temporarily prevent login items from opening without deleting them.

Disable one nonessential item, test, and restore it if the symptom does not change.

Keep required sync, update, backup, security, accessibility, driver, and organization-management helpers enabled.

If this is a newly configured computer, first compare the new Mac setup checklist. If slow startup is only one part of a wider problem, use the device troubleshooting guide. This guide uses supported settings; it does not delete LaunchAgents or LaunchDaemons manually.

How do you Manage Login Items and Background Apps on Mac?

The labels describe different moments and capabilities:

Control	What it does	Example reason to keep it
Open at Login	Opens an app, document, folder, volume, or connection after you sign in	A tool you intentionally use every session
App Background Activity	Lets an app perform work while its main window is closed	Syncing files or checking for updates
Extensions	Adds a defined capability to Finder, sharing, cameras, drivers, security, or another system surface	A storage provider or approved security extension

Apple says the Open at Login list can contain apps, documents, folders, and server connections. It separately describes background activity as tasks such as software update checks or data syncing.［1］ The Extensions area includes several categories, including Finder, file-provider, driver, camera, and endpoint-security extensions.［2］ A visible item is therefore not automatically wasteful or suspicious.

Do not use Activity Monitor alone to decide what should start. A process name may belong to a signed helper whose user-facing app is obvious only after you inspect its path or publisher. Conversely, closing a window does not prove that background work should stop; cloud storage, backup, messaging, licensing, and security tools often need a helper.

How do you identify Mac background apps and their owners?

Make an inventory before changing switches.

Open System Settings > General > Login Items & Extensions.
Record the names under Open at Login and App Background Activity. Expand an entry or use its information control when available.
Match each item to an app you installed, an employer or school tool, a peripheral, a cloud service, or macOS itself.
Open the parent app and review its own preferences for “launch at login,” syncing, updates, menu-bar operation, or helper behavior.
Check the publisher's official documentation when the name is abbreviated. Avoid trusting a search result that offers a removal utility before explaining the component.
Note whether removing the parent app left a yellow warning or orphaned login item. Apple says a yellow triangle can mean the item was moved or deleted.

Use three categories: required, optional, and unknown. Required includes security controls, device-management agents, backup, active file sync, accessibility tools you depend on, and peripheral drivers. Optional includes apps you recognize but do not need immediately after login. Unknown means “investigate,” not “disable.”

On a managed Mac, policy can restore or require an item. Do not remove profiles, endpoint-security extensions, or organization agents to test performance. Record the item and ask the administrator what it controls.

How do you stop apps opening at startup on Mac temporarily?

Use the Shift test when you want evidence without altering the saved list. Apple provides two paths. If the login window is visible, hold Shift while clicking Log In and release it when the Dock appears. If you normally bypass the login window, restart, hold Shift when the startup progress bar appears, and release it after the desktop appears.

This temporarily suppresses automatic login items for that session. It is not Safe Mode, does not uninstall software, and does not permanently turn off background activity or extensions. Use it as a comparison:

Measure the normal symptom: login duration, repeated window, crash, or high resource use after sign-in.
Save work and log out or restart normally.
Perform the Shift login exactly once.
Wait the same amount of time and repeat the same low-risk observation.
Record which symptom disappeared, remained, or changed.

If nothing changes, the cause may be a system service, background permission, extension, storage pressure, user data, or hardware rather than an Open at Login item. Do not conclude that every saved item is innocent, but do not delete the list either.

How do you disable one nonessential login or background item?

Make a reversible, one-variable change.

Choose an item you recognize and do not need for the next test.
For Open at Login, select it and click the remove button. This removes the automatic opening instruction; it does not necessarily uninstall the app. Apple documents add and remove controls for this list.
For App Background Activity, turn off only the selected app. Expect its sync, update checks, notifications, or other background tasks to stop.
Prefer the parent app's own “open at login” option when it clearly controls the same behavior. Keep the System Settings result as the final check.
Log out and back in or restart, then reproduce the same observation under the same conditions.
If the symptom does not change, restore the item before testing the next candidate.

Avoid turning off all background apps at once. A faster login after a mass disable would not identify the cause, while missed backups, stale security definitions, unsynced files, and failed updates could appear later. Do not judge an item solely by unfamiliar naming or current CPU use.

If an app immediately re-adds a login item, open the app and disable its launch setting there. If a managed policy restores it, contact the administrator. If there is no recognizable owner and it returns without explanation, preserve evidence and use the Mac malware check rather than deleting system persistence files by hand.

How should you review Login Items & Extensions on Mac?

Extensions provide scoped capabilities and can have wider consequences than opening a window. Apple's list includes endpoint-security and driver extensions as well as Finder and file-provider integrations. Turning one off can remove device access, cloud files, Quick Actions, camera functions, or security monitoring.

Before changing an extension, answer:

Which app or organization installed it?
What feature will stop if it is disabled?
Is it required for storage, accessibility, security, work, school, or hardware?
Is there a supported switch inside the parent app?
Can you safely restore it without losing access to files or input devices?

Do not disable endpoint-security, device-management, authentication, encryption, backup, or required accessibility components merely to reduce the list. Do not manually remove files from /Library/LaunchAgents, /Library/LaunchDaemons, or user Library folders. Those locations can contain legitimate system-wide and per-user services, and deleting a file can break uninstallers, updates, or policy enforcement.

For an optional Finder or sharing extension, turn off only that named extension, test the specific Finder or Share behavior, and restore it if unrelated. For a peripheral driver, use the manufacturer's supported management or uninstall path and keep a wired input option if the device is essential.

How do you verify the result and restore required work?

Use a repeatable login test rather than a vague impression.

Record the time from login submission to a usable desktop, but also note when required sync and security tools become ready.
Check whether the original unwanted window, error, or high resource use returns.
Open the parent app and verify its core task.
Confirm that cloud files sync, backups run, updates check, notifications arrive, peripherals work, and organizational access remains available.
Review Login Items & Extensions again to see whether the tested item remained off or was restored by the app or policy.
Restore every required helper that was disabled during a controlled test.

A shorter login is not a complete success if files stop syncing or endpoint protection stops reporting. Likewise, a background process using resources briefly after login may be completing legitimate indexing, sync, or update work. Compare after a consistent settling period.

If the Mac is slow because storage is nearly full, changing login items is unlikely to be sufficient. Use the Mac storage full guide and preserve backups before cleanup. If a known app is the cause, update it, change its own launch preference, or use its official uninstaller rather than deleting helpers individually.

What signs need escalation instead of routine cleanup?

Stop normal tuning when an item has no identifiable owner, returns after its parent app is removed, imitates a system name, opens unwanted pages, requests unexpected accessibility or screen-recording access, or appears with other compromise signs. Take notes of the displayed name, publisher, location if safely available, time, and related alerts.

Do not run a random “startup cleaner,” paste terminal deletion commands from a forum, or disable security to inspect the item. Disconnect from sensitive workflows if compromise is plausible, preserve evidence, and follow the malware guide or your organization's incident process.

For a normal app bug, give the developer the app version, macOS version, item name, and the controlled test result. For a managed component, give the administrator the same evidence. The goal is to remove uncertainty without weakening the Mac.

FAQ

Is every background app slowing down my Mac?

No. Many wait idle until they need to sync, update, back up, or respond to an event. Use Activity Monitor and a one-item test as evidence, but identify the owner and purpose before changing permission.

Does removing an Open at Login item uninstall the app?

Normally it removes the automatic-open instruction, not the app itself. The app can still run manually and may have a separate background permission. Use the app's supported uninstall process if removal is actually intended.

What does holding Shift during login do?

It temporarily prevents automatic login items from opening for that login session. It is a reversible comparison and does not permanently delete the list, disable every background helper, or replace Safe Mode.

Why did a login item come back?

The parent app may have its own launch preference, an update may restore the helper, or an organization policy may require it. Check the app and management context. Unexplained repeated persistence deserves a malware review, not manual system-file deletion.

Can I turn off every item under App Background Activity?

Do not do that as a troubleshooting shortcut. You could stop sync, backups, updates, licensing, notifications, security, or managed access while learning nothing about the actual cause. Test one known optional item at a time.

Should I delete LaunchAgents or LaunchDaemons manually?

No. Manual deletion can break legitimate apps, updates, security tools, and uninstallers. Use Login Items & Extensions, the parent app's settings, or its official uninstall instructions. Escalate unknown persistence safely.

Are extensions the same as login items?

No. Extensions add defined capabilities to system surfaces such as Finder, files, cameras, drivers, and security. Disabling one can remove functionality even when no app window opens at login.

When should I restore a helper?

Restore it immediately when the test does not change the symptom or when required sync, backup, updates, security, accessibility, hardware, or organization access stops. Verification includes those downstream functions, not just login speed.

Related guides

Sources

Apple, “Open items automatically when you log in on Mac” — https://support.apple.com/guide/mac-help/open-items-automatically-when-you-log-in-mh15189/mac
Apple, “Change Login Items & Extensions settings on Mac” — https://support.apple.com/guide/mac-help/change-login-items-extensions-settings-mtusr003/mac

Sources checked 4 October 2026.

Manage Login Items and Background Apps on Mac Safely