Skip to content

Acquisition & backupsDevice & system

Manifest.db and Manifest.plist: iOS Backup Structure

How an iPhone backup is organised: Manifest.db, Manifest.plist, Info.plist and Status.plist, hashed file IDs, and what encrypted backups add.

Location
macOS: ~/Library/Application Support/MobileSync/Backup/<UDID>/ · Windows: %APPDATA%\Apple Computer\MobileSync\Backup\<UDID>\ or %USERPROFILE%\Apple\MobileSync\Backup\<UDID>\
Proves
Which files a backup contains and where each one came from on the device, when the backup was taken, whether it is encrypted, and device identity (name, model, iOS version, serial, IMEI, installed apps)
Timestamps
Info.plist and Status.plist dates are plist dates (UTC). MBFile records in Manifest.db hold Unix times in seconds for file birth, modification and status change
Acquisition
The backup folder on a trusted computer, or a new backup from an unlocked, trusted device. Encrypted backups need the backup password to read Manifest.db and file content
Retention
One backup set per device UDID on a host, overwritten by the next backup unless archived; older backups can survive on other computers or in host file system snapshots
Collection
idevicebackup2, pymobiledevice3 backup2, iMazing, Finder / Apple Devices

What it is

An iTunes, Finder or Apple Devices backup is a folder named after the device's UDID. It does not mirror the phone's file system: every backed-up file is stored under a 40-character hexadecimal name, and a SQLite catalogue, Manifest.db, maps those names back to an app domain and a relative path. Three property lists sit next to it and describe the device and the backup.

Knowing this layout is the prerequisite for everything else on this site that "reaches a backup": sms.db, AddressBook and Photos.sqlite in any backup, CallHistory and Safari history only in encrypted ones.

Where it lives

HostDefault backup folder
macOS (Finder)~/Library/Application Support/MobileSync/Backup/<UDID>/
Windows (iTunes from apple.com)%APPDATA%\Apple Computer\MobileSync\Backup\<UDID>\
Windows (iTunes or Apple Devices from the Microsoft Store)%USERPROFILE%\Apple\MobileSync\Backup\<UDID>\

Inside the folder:

FileContent
Info.plistDevice name, model, product version and build, serial number, IMEI (where applicable), phone number, last backup date, list of installed apps
Manifest.plistIsEncrypted, WasPasscodeSet, Date, Lockdown (device details), Applications, and BackupKeyBag plus ManifestKey when encrypted
Status.plistBackup state, IsFullBackup, snapshot date and backup UUID
Manifest.dbCatalogue of every backed-up file (SQLite; encrypted as a whole in encrypted backups)
xx/<fileID>File content, stored under the first two hex characters of its ID

What it proves

  • Which domains and files a backup holds, which tells you what the analysis can and cannot cover.
  • When the backup was taken and whether it was complete.
  • The device's identity and iOS version at backup time, and which apps were installed.
  • Per-file metadata (size, mode, timestamps, protection class) as recorded by the device.

It does not prove the backup was made by the device owner, nor on which computer, unless you also examine the host and its pairing records.

Key fields

Manifest.db, table Files:

ColumnMeaning
fileIDSHA-1 of domain-relativePath, e.g. SHA-1 of HomeDomain-Library/SMS/sms.db = 3d0d7e5fb2ce288813306e4d4636395e047a3d28
domainHomeDomain, CameraRollDomain, MediaDomain, AppDomain-<bundle id>, AppDomainGroup-<group id>, SysSharedContainerDomain-..., and others
relativePathPath inside the domain
flags1 = file, 2 = directory, 4 = symbolic link
fileBinary plist (NSKeyedArchiver) describing an MBFile: size, mode, UID and GID, birth, last modified and last status change times, ProtectionClass, and EncryptionKey for encrypted backups

Table Properties holds backup-level values.

Timestamps

Plist dates in Info.plist, Manifest.plist and Status.plist are stored in UTC and shown converted by most viewers: check which time zone your tool displays. The Birth, LastModified and LastStatusChange values inside each MBFile are Unix seconds. They describe the file on the device at backup time, which makes them useful for timeline work even when the file's content has no timestamps.

Retention

A host keeps one backup set per device UDID and overwrites it with each new backup. Older sets survive when they were archived (Finder and iTunes can rename a backup to keep it), copied to another disk, captured in Time Machine or a file system snapshot, or synced to cloud storage. Look for all of them: an old backup can contain data deleted from the phone since.

Collection

  • Existing backup on a computer: image or copy the whole <UDID> folder with timestamps and hash it. Also collect the host's pairing records (/private/var/db/lockdown/ on macOS, %ProgramData%\Apple\Lockdown\ on Windows).
  • New backup from an unlocked, trusted device: idevicebackup2 backup --full ./case/ (libimobiledevice), pymobiledevice3 backup2 backup --full ./case/ (pymobiledevice3), UFADE or iMazing. Prefer an encrypted backup with a password you set and record: it contains more data. See the acquisition guide.

Parsing

  • Unencrypted: sqlite3 Manifest.db "SELECT fileID, domain, relativePath FROM Files WHERE flags = 1;" and plutil -p Info.plist (macOS).
  • Encrypted, password known: decrypt with MVT (mvt-ios decrypt-backup -p <password> -d ./decrypted ./backup) or iphone_backup_decrypt, then parse as usual.
  • Encrypted, password unknown and recovery authorised: Hash Extractor turns the BackupKeyBag in Manifest.plist into a hashcat or John hash in the browser. Expect a slow attack: recent backups use a very high PBKDF2 iteration count.
  • iLEAPP reads backup folders directly and resolves paths through Manifest.db.

Investigator tips

  • Check IsEncrypted first. An unencrypted backup lacks call history, website history, saved passwords, Wi-Fi settings and Health data by design.
  • WasPasscodeSet and the Lockdown details in Manifest.plist help document the device's state at backup time.
  • Hash each file you extract from the backup and record its fileID, domain and path, so any finding can be traced to the backup.
  • App data in AppDomain- and AppDomainGroup- domains is only present when the app allows backup. Absence in a backup is not absence on the device.

See also