Reference · checked against real backups

The files in an iPhone backup

An iPhone backup folder is full of folders named 00 to ff, holding files with 40-character names like 3d0d7e5fb2ce288813306e4d4636395e047a3d28. Each name is the SHA-1 hash of where the file was on the phone. Find a name below to see what the file is, which iOS versions have it, and how to open it.

Look up a file

The files people ask about most. The same file has the same name in every backup, from any iPhone, because the name comes from the file's place on the phone, not from what's in it.

HashFileWhat it is
3d0d7e5fb2ce288813306e4d4636395e047a3d28 sms.dbHomeDomain The Messages database: every text and iMessage, who it was with, when, and which attachments go with it.
31bb7ba8914766d4ba40d6dfb6113c8b614be442 AddressBook.sqlitedbHomeDomain The Contacts database: each contact's name, company, phone numbers, email addresses and notes.
cd6702cea29fe89cf280a76794405adb17f9a0ee AddressBookImages.sqlitedbHomeDomain Contact photos: the small and full-size pictures shown for people in Contacts.
5a4935c78a5255723f707230a451d79c540d2741 CallHistory.storedataHomeDomain Call history: who called or was called, when, for how long, and whether it was answered.
992df473bbb9e132f4b3b6e4d33f72171e97bc7a voicemail.dbHomeDomain Visual Voicemail: who left each voicemail, when, and how long it is. The audio is in separate files.
4f98687d8ab0d6d1a371110e6b7300f6e465bef2 NoteStore.sqliteAppDomainGroup-group.com.apple.notes The Notes database: notes, folders and accounts from the Notes app on current iOS versions.
ca3bc056d4da0bbf88b5fb3be254f3b7147e639c notes.sqliteHomeDomain The Notes database from iOS 8 and earlier. Newer phones still have the file, but keep notes in NoteStore.sqlite.
12b144c0bd44f2b3dffd9186d3f9c05b917cee25 Photos.sqliteCameraRollDomain The Photos library database: each photo and video's file name, date, albums, and whether it's a favorite, hidden or deleted.
1a0e7afc19d307da602ccdcece51af33afe92c53 History.dbHomeDomain Safari's browsing history: every page visited, its title, and the time of each visit.
d1f062e2da26192a6625d968274bfda8d07821e4 Bookmarks.dbHomeDomain Safari's bookmarks and bookmark folders.
2041457d5fe04d39d0ab481178355df6781e6858 Calendar.sqlitedbHomeDomain The Calendar database: events, their times and places, and the calendars they belong to.
7c7fba66680ef796b916b067077cc246adacf01d ChatStorage.sqliteAppDomainGroup-group.net.whatsapp.WhatsApp.shared WhatsApp's chats: every message, group and call on the phone, with pointers to its photos, videos and voice messages.
b8548dc30aa1030df0ce18ef08b882cf7ab5212f ContactsV2.sqliteAppDomainGroup-group.net.whatsapp.WhatsApp.shared WhatsApp's copy of the address book, from older WhatsApp versions: names for the numbers in your chats.
e794f6ffcc3c222535f47684a63d5178da3c4500 LID.sqliteAppDomainGroup-group.net.whatsapp.WhatsApp.shared WhatsApp's LIDs, the IDs newer WhatsApp versions use instead of phone numbers, matched to numbers and names.
be7e71b773c6d7d4114a8acf0529f623f3884bfb group.net.whatsapp.WhatsApp.shared.plistAppDomainGroup-group.net.whatsapp.WhatsApp.shared WhatsApp's shared settings, including the phone's own WhatsApp ID and profile name.
398be25b8d2881e4a18865f018eb5d8e3c8fc962 MTLibrary.sqliteAppDomainGroup-243LU875E5.groups.com.apple.podcasts The Apple Podcasts library: shows followed, their episodes, play counts and where you stopped listening.
2e57c396a35b0d1bcbc624725002d98bd61d142b browser.dbAppDomainGroup-group.org.mozilla.ios.Firefox Firefox for iOS's older history database: sites visited and when.
ab87b1b6904c441f3814d12748a1a32750a43496 places.dbAppDomainGroup-group.org.mozilla.ios.Firefox Firefox for iOS's history and bookmarks database in current versions.
516d7e19a4a0c9475c0015fae195626377b1b810 healthdb_secure.sqliteHealthDomain Apple Health's records: steps, heart rate, workouts, sleep and every other sample the Health app keeps.

How a backup folder is laid out

Each iPhone or iPad backed up on a computer gets one folder, named after the device's ID. On a Mac it's in ~/Library/Application Support/MobileSync/Backup; on Windows, in %USERPROFILE%\Apple\MobileSync\Backup. See where iPhone backups are stored for the details. Inside, it looks like this:

<device ID>/
├── Manifest.db
├── Manifest.plist
├── Info.plist
├── Status.plist
├── 00/
├── 01/
│   …
├── 3d/
│   └── 3d0d7e5fb2ce288813306e4d4636395e047a3d28   ← sms.db
│   …
└── ff/

Every file from the phone is stored under its hash, in the folder named after the hash's first two characters, with no extension. So sms.db is 3d/3d0d7e5fb2ce288813306e4d4636395e047a3d28. Backups from iOS 9 and earlier have no two-character folders: their files sit directly in the backup folder, and Manifest.mbdb lists them instead of Manifest.db.

A backup that's still being made, or that stopped partway, also has a Snapshot folder. The iPhone creates it at the start of every backup and removes it at the very end, so a finished backup made by Finder, iTunes or Apple Devices has none.

The four files at the top

Manifest.db is the index: a SQLite database with a row for every file, folder and link in the backup. Its Files table has the fileID (the hash), the domain and relativePath it stands for, flags (1 for a file, 2 for a folder, 4 for a symbolic link) and file, a binary property list with the file's size, dates and permissions. In an encrypted backup, file also holds the key for that file. There's one more table, Properties.

Manifest.plist says whether the backup is encrypted (IsEncrypted), when it was made (Date) and whether the phone had a passcode (WasPasscodeSet). It lists the apps (Applications), has the device's iOS version, build, name, serial number and ID under Lockdown, and holds the keybag (BackupKeyBag) that the password unlocks. Encrypted backups also have ManifestKey, the key to Manifest.db.

Info.plist describes the device for Finder, iTunes and Apple Devices: Device Name, Product Type (the model, such as iPhone12,1), Product Version (iOS), Serial Number, IMEI, Phone Number, Last Backup Date, the installed apps, and which program and computer made the backup. It's never encrypted, so it's readable even when the rest of the backup isn't.

Status.plist records the backup's state: SnapshotState (finished once the iPhone has completed it), IsFullBackup, Date, UUID and Version.

How a file gets its name

The name is the SHA-1 hash of the file's domain and its path within that domain, joined by a hyphen. sms.db is in HomeDomain at Library/SMS/sms.db, so its name is the SHA-1 of HomeDomain-Library/SMS/sms.db. You can work one out yourself in a terminal on a Mac or Linux:

printf '%s' 'HomeDomain-Library/SMS/sms.db' | shasum
3d0d7e5fb2ce288813306e4d4636395e047a3d28  -

To go the other way, look the hash up in Manifest.db, which is plain SQLite in a backup that isn't encrypted:

SELECT domain, relativePath FROM Files
WHERE fileID = '3d0d7e5fb2ce288813306e4d4636395e047a3d28';

We checked the rule on all 58,071 entries in the file lists of six real backups, iOS 13.3.1 to 17.3: every name is the SHA-1 of its domain and path. An entry for a domain's top folder has an empty path, so its name is the hash of the domain and a hyphen.

The domain says which part of the phone a file belongs to. The ones on these pages:

Encrypted backups

An encrypted backup has the same folders and the same file names, but every file's contents are encrypted with a key of its own, and Manifest.db is encrypted too. The keys are in Manifest.plist, locked by the backup password, so nothing in the backup can be read without it. A tool that knows the password, such as OpenExtract, decrypts each file when it needs it.

Encrypted backups also hold more. Apple lists five kinds of data that only an encrypted backup can include: saved passwords, Wi-Fi settings, website history, Health data and call history. That's why CallHistory.storedata, Safari's History.db and healthdb_secure.sqlite are marked as needing an encrypted backup. For the rest, see why encrypted backups are better.

How we checked

Every file on these pages was found in real backups: public forensic test images made by Joshua Hickman on iPhones running iOS 13.3.1 and 13.4.1, iOS 15.3.1, and iOS 16.1.2 and 17.3, and the file list of an iOS 16.0 backup from ANSSI's FCSC 2025 challenge. All of them are encrypted. Hickman's were opened with the passwords he published; the FCSC backup's password isn't public, so only its list of files was checked.

The check reads each database's table and column names and nothing else: no messages, names, numbers or other contents. It uses ios-backup-core, the open-source library inside OpenExtract, and the script is scripts/verify-backup-files.py. A version we haven't checked can differ. If you find a file that's different, or one you'd like listed, open an issue on GitHub.

Read the backup, not the hashes.
OpenExtract opens these files for you. Free, open source, nothing uploaded. Mac · Windows · Linux.
Download OpenExtract →