What is backgroundtaskmanagementd, and why is it running?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
backgroundtaskmanagementd is the macOS daemon that keeps the list of items meant to run at login or in the background, and records whether you approved them. It does short bursts of work when apps are installed, add background items, or when you change Login Items settings. It is part of macOS and should be left running.
backgroundtaskmanagementd at a glance
| backgroundtaskmanagementd | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon |
| Location | /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Resources/backgroundtaskmanagementd |
| Runs as | root |
| Started by | launchd job com.apple.backgroundtaskmanagementd |
| Can you quit it? | Not usefully. launchd starts it on demand, and login items depend on its records. |
What is backgroundtaskmanagementd?
Its man page describes it as a daemon that manages a set of items intended to run as background tasks or at login, and the policy for the user's approval to let them run. That includes items in Login Items settings, items installed with ServiceManagement, and items from managed device profiles. The man page still names the old System Preferences location; on macOS 26 the list is in System Settings > General > Login Items & Extensions.
It runs as root from the com.apple.backgroundtaskmanagementd launchd job. The per-user BackgroundTaskManagementAgent shows the notifications, and smd performs the registrations that apps request.
Is backgroundtaskmanagementd safe?
Yes. It is part of macOS inside the BackgroundTaskManagement private framework on the read-only system volume, runs as root and is started by launchd.
Why does backgroundtaskmanagementd use so much CPU?
- Apps adding or removing background items. Installing an app that brings a launch agent, daemon or login item, or uninstalling one, updates the daemon's records.
- Changing Login Items settings. Switching background activity on or off for an app, or adding and removing login items, changes the approval state it stores.
- Configuration profiles. On managed Macs, profiles that approve background items by rule are evaluated against each item. Apple's deployment guide says a matching item is approved automatically.
- After a reset. Apple's deployment guide documents
sfltool resetbtm, which resets login and background item data. Afterwards the daemon rebuilds its records as apps register their items again.
How much CPU is normal for backgroundtaskmanagementd?
Typical: idle or not running most of the time, with short activity during app installs and when Login Items settings change.
Sustained high CPU is not typical; it suggests an app that keeps registering and removing an item.
How do you check the items backgroundtaskmanagementd manages?
- Review the list in System Settings. Open System Settings > General > Login Items & Extensions and look through Open at Login and App Background Activity.
- Print the full record. In Terminal,
sfltool dumpbtmprints the status of every login and background item, including the developer and whether it is allowed. It may ask for an administrator password. - Remove leftovers of deleted apps. If the list shows items from apps you removed, look for their files in
/Library/LaunchAgents,/Library/LaunchDaemonsand~/Library/LaunchAgents, and use the app's own uninstaller where one exists. - Reset only as a last resort. Apple's deployment guide documents
sfltool resetbtmto reset login and background item data and recommends restarting afterwards. You will be asked again about items as they register.
When should you worry about backgroundtaskmanagementd?
The daemon is not something to worry about. Unknown entries in its list are: if sfltool dumpbtm or Login Items shows software you do not recognize, find and remove the app.
A file with this name outside the BackgroundTaskManagement framework would not be Apple's.
How do you check backgroundtaskmanagementd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type backgroundtaskmanagementd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every backgroundtaskmanagementd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'backgroundtaskmanagementd' | grep -v grep
How can Thrum help with backgroundtaskmanagementd?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when backgroundtaskmanagementd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about backgroundtaskmanagementd
What is the difference between backgroundtaskmanagementd and BackgroundTaskManagementAgent?
The daemon runs as root and keeps the list of items and their approval. The agent runs as your user and shows the notifications about them.
Does turning off an item in Login Items delete it?
No. Switching off background activity stops the item from running; the app and its files stay. Remove the app to remove the item completely.
Sources
- backgroundtaskmanagementd(8) man page: run man backgroundtaskmanagementd in Terminal
- Apple Platform Deployment: Manage login items and background tasks on Mac
- Apple Support: Change Login Items & Extensions settings on Mac