Skip to content

Where the BTM Store Lives: BackgroundItems-v*.btm

Location, file versions and format of the macOS BTM store, how its records map to users, and the legacy backgrounditems.btm used from macOS 10.13 to 12.

Published on 7 min read
On this page

TL;DR. The Background Task Management store is one file for all users: /private/var/db/com.apple.backgroundtaskmanagement/BackgroundItems-v<N>.btm, where <N> is the store format version. It is a binary plist written with NSKeyedArchiver, and it files records under each user's generated UID. Reading it on a live Mac needs root and Full Disk Access. From macOS 10.13 to 12 there was no such store: each user's login items were in ~/Library/Application Support/com.apple.backgroundtaskmanagementagent/backgrounditems.btm. Collect the whole folder, every .btm file in it, and load it on BTM Parser.

The files

macOSPathWhat it holdsWho can read it
13 Ventura and later/private/var/db/com.apple.backgroundtaskmanagement/BackgroundItems-v<N>.btmLogin items, launch agents, launch daemons, app and developer records, for every userroot, with Full Disk Access
10.13 High Sierra to 12 Monterey~/Library/Application Support/com.apple.backgroundtaskmanagementagent/backgrounditems.btmThe user's Open at Login list, as bookmarksThe user
10.12 and earlier~/Library/Preferences/com.apple.loginitems.plistThe user's login items (reported)The user

Next to the store, two other places help you read it:

  • /private/var/db/com.apple.xpc.launchd/ holds launchd's own override files (disabled.plist, disabled.<uid>.plist) and, on some Macs, loginitems.<uid>.plist files for helpers enabled with the older Service Management call. See BTM vs launchd overrides.
  • /private/var/db/dslocal/nodes/Default/users/*.plist holds the local accounts, with the generateduid that names each user's section of the store.

The version number

The v<N> in the file name is the version of the store format. Objective-See's DumpBTM documentation reports BackgroundItems-v7.btm on macOS 13.1, and its instructions also mention a BackgroundItems-v4.btm file from the Ventura period. Howard Oakley reports BackgroundItems-v16.btm on a recent release, and the FIN-MBP-03 sample, set on macOS 26, uses v16. Apple does not publish the list.

Two consequences:

  • Do not date a Mac by the number. Several releases can share one format. Take the version from /System/Library/CoreServices/SystemVersion.plist.
  • Collect the whole folder. When the format changes, the daemon migrates the store. Strings in recent builds of backgroundtaskmanagementd refer to migrated stores and to a second name pattern with a suffix after the version number. Whether an older file stays behind depends on the release; if it does, it is earlier evidence.

The format

The .btm file is a binary property list (it starts with bplist00) produced by NSKeyedArchiver, the Foundation class that writes objects as a keyed archive. An archive is not a readable tree. It is a flat array, $objects, in which objects refer to each other by index, plus a $top entry that says where to start, $archiver (NSKeyedArchiver) and $version (100000). Index 0 of $objects is $null. A reference uses the plist UID type, which many tools show as CF$UID, and each object's $class points to an entry naming its class. plutil -p will print it, but you see the table, not the records.

Unarchiving rebuilds the objects by following those references from $top. Common Foundation types have known encodings: an NSURL is stored as NS.base and NS.relative, an NSUUID as 16 bytes in NS.uuidbytes. Unarchived, recent stores look like this:

Storage
  version
  itemsByUserIdentifier
    <user generated UID>  →  [ ItemRecord, ItemRecord, … ]
  userSettingsByUserIdentifier
  mdmPayloadsByIdentifier

Storage and ItemRecord are class names seen in recent builds of the daemon. Item properties seen there include uuid, name, developerName, teamIdentifier, type, disposition, identifier, url, executablePath, bundleIdentifier, associatedBundleIdentifiers, container, generation and embeddedItems, and, in recent builds, signing data such as a lightweight code requirement. Apple has renamed classes and keys between versions and does not document any of them. For that reason BTM Parser recognises a record by its shape (an object with a type and a URL, identifier or executable path) and reads fields under their known aliases, rather than expecting fixed names. A store from a Mac under investigation is also untrusted input: references can point anywhere, form cycles or nest deeply. BTM Parser checks every reference, stops at cycles and limits the depth.

Times in the store

The item records have no documented registration time. Recent builds of the daemon define properties for the modification times of an item's plist and executable (modificationDate, executableModificationDate). If your store has them, they are file times the daemon noted, not the moment the item was registered. An NSDate in a keyed archive is stored in NS.time as Mac absolute time, seconds since 2001-01-01 00:00:00 UTC; a plain number may use another reference, so check it against a time you know.

The store file's own modification time is reliable in one narrow sense: it shows when the store was last written. In the FIN-MBP-03 sample, it matches the moment backgroundtaskmanagementd registered the planted agent, 2026-09-14 10:13:02.512 UTC.

Users in the store

Records are filed under the user's generated UID, a UUID, not under the numeric UID. To name the user, match the key to the generateduid attribute in the dslocal account plists, or on a live Mac run dscl . -read /Users/<name> GeneratedUID. Two fixed values are worth knowing:

Generated UIDAccount
FFFFEEEE-DDDD-CCCC-BBBB-AAAA00000000root (UID 0)
FFFFEEEE-DDDD-CCCC-BBBB-AAAAFFFFFFFEnobody (UID -2)

Apple's Endpoint Security documentation notes that the user of a BTM item may be nobody (-2), so do not be surprised by a section for UID -2. In sfltool dumpbtm output, each section starts with Records for UID <n> : <generated UID>.

In the FIN-MBP-03 sample, all records sit under 6E1C7B52-3F0A-4D21-9B8E-2C5A7D9E4F13, the generated UID of dana.whitlock (UID 501). When you load the account plists with the store, BTM Parser names the user behind each UUID. It reads names, UIDs and generated UIDs from those plists and never reads password hashes.

The legacy backgrounditems.btm

From macOS 10.13 to 12, the Open at Login list of each user was kept in backgrounditems.btm in the user's Library. It is also a keyed archive, but each item is mostly bookmark data: the binary form macOS uses to find a file again after it moves. A bookmark contains the path and the volume, and often the name, so the app behind each item can usually be recovered.

It differs from the modern store in ways that matter:

  • Per user, owned by the user. No root or Full Disk Access is needed to read your own.
  • Login items only. Launch agents and daemons were never in it.
  • No developer, team or disposition. There is no attribution.
  • No per-item dates. Use the file's own times, FSEvents and logs.

On a Mac upgraded to Ventura or later, the old file may still be present. Collect it if it is: it shows what opened at login before the upgrade. BTM Parser reads names and paths from it on a best-effort basis, because bookmark contents vary. The open-source bgiparser reads both the legacy and the modern files.

Access on a live Mac

/private/var/db/com.apple.backgroundtaskmanagement is privacy-protected. On a recent release, listing it from a Terminal that lacks Full Disk Access fails with "Operation not permitted", with or without sudo. The copying process needs both root and Full Disk Access. On a mounted image on an analysis host, neither restriction applies.

sudo sfltool dumpbtm is the other way in: it prints the records without you copying the file. The two are complementary, and the commands for both are in collecting the BTM store.

FAQ

Where is the BTM database on macOS?

In /private/var/db/com.apple.backgroundtaskmanagement/, as BackgroundItems-v<N>.btm. There is one store for all users. On macOS 10.13 to 12, login items were in each user's ~/Library/Application Support/com.apple.backgroundtaskmanagementagent/backgrounditems.btm instead.

Can I tell the macOS version from the v number?

No. The number is the store format version. It has risen across releases (v7 is reported on macOS 13.1, v16 on recent releases), but several releases can share one number. Take the macOS version from SystemVersion.plist.

What format is a .btm file?

A binary property list written with NSKeyedArchiver: a flat table of objects that point to each other, which has to be unarchived before the records can be read. plutil -p shows the raw table; sfltool dumpbtm, DumpBTM, bgiparser or BTM Parser show the records.

Why can I not list the folder even with sudo?

The folder is privacy-protected. The process doing the reading, for example Terminal, needs Full Disk Access as well as root. Without it, the read fails with Operation not permitted.

Frequently asked questions

Where is the BTM database on macOS?

In /private/var/db/com.apple.backgroundtaskmanagement/, as BackgroundItems-v<N>.btm. There is one store for all users. On macOS 10.13 to 12, login items were in each user's ~/Library/Application Support/com.apple.backgroundtaskmanagementagent/backgrounditems.btm instead.

Can I tell the macOS version from the v number?

No. The number is the store format version. It has risen across releases (v7 is reported on macOS 13.1, v16 on recent releases), but several releases can share one number. Take the macOS version from SystemVersion.plist.

What format is a .btm file?

A binary property list written with NSKeyedArchiver: a flat table of objects that point to each other, which has to be unarchived before the records can be read. plutil -p shows the raw table; sfltool dumpbtm, DumpBTM, bgiparser or BTM Parser show the records.

Why can I not list the folder even with sudo?

The folder is privacy-protected. The process doing the reading, for example Terminal, needs Full Disk Access as well as root. Without it, the read fails with Operation not permitted.