How to extract app data from an iPhone backup on Mac

Every app that has a container in a local iPhone backup is stored under its own domain in Manifest.db, named AppDomain- plus the app's bundle ID. You can query that index with sqlite3 on an unencrypted backup and copy out the hashed files by hand, or open App Files in Yado's backup browser, which lists each app by name and exports its files at their original paths. Either way you get what the backup kept, which is less than everything the app shows on the phone.
What a local backup holds for each app
A computer backup contains almost all of the phone's data and settings, and for an app that mostly means the files in its own container. Apple's developer documentation says Documents/ and Library/ are backed up, with the exception of Library/Caches, and that tmp/ is not (File System Programming Guide). The same page says a developer can exclude any file from the backup, and that files which can be re-created or downloaded should be. So a downloaded video library or an offline map inside an app is often absent on purpose.
Two further limits come from Apple's own page on what a computer backup includes. Data already synced and stored in iCloud, such as iCloud Photos and Messages in iCloud, is left out, and so is content from the App Store, Apple Books and Mail (Apple Support). An app that keeps its history on a server or in its own iCloud container will therefore have a small footprint in the backup, whatever the app shows on screen.
How the manifest maps an app's files
In the backup folder, every file is stored under a 40-character hexadecimal name inside a subfolder named after its first two characters. Manifest.db is the index. Its Files table has a fileID that points at that hashed file, a domain that says which area it belongs to, and a relativePath that says where it sat in that area. Yado reads only the rows whose flags is 1, which are regular files.
For an app's own container the domain is AppDomain-<bundle id>, for example AppDomain-com.apple.mobilesafari for Safari, and the relative path starts from the container's top, such as Documents/... or Library/Preferences/.... Apps that share data with their extensions or with other apps from the same developer also have a domain beginning AppDomainGroup-. Yado does not list those under App Files, because several apps can share one.
App names are not in the manifest at all. Yado takes the display name from the Applications entry in the backup's Info.plist, which holds the App Store metadata, and falls back to the bundle ID when there is none.

Find an app's files in an unencrypted backup
Copy the whole backup folder somewhere first and work on the copy, as in how to view an iPhone backup on Mac. Then list which apps have a container, with how many files each holds. Replace the path with your copy's folder.
sqlite3 -readonly -header -column "/path/to/copied-backup/Manifest.db" \
"SELECT domain, COUNT(*) AS files
FROM Files
WHERE flags = 1 AND domain LIKE 'AppDomain-%'
GROUP BY domain
ORDER BY files DESC;"
Pick a bundle ID from the result and list its files.
sqlite3 -readonly -header -column "/path/to/copied-backup/Manifest.db" \
"SELECT fileID, relativePath
FROM Files
WHERE flags = 1 AND domain = 'AppDomain-com.example.app'
ORDER BY relativePath;"
To copy one file, take its fileID, open the subfolder named after its first two characters, and copy the file inside to a new name of your choice, with the original extension from relativePath.
cp "/path/to/copied-backup/ab/abcdef0123456789abcdef0123456789abcdef01" ~/Desktop/notes.sqlite
A plain copy gives you the bytes but not the modification date the file had on the phone. If the file is a database, the app may also keep recent writes in -wal and -shm companions, so copy those too under matching names before you open it. This route is fine for one or two files and tedious for a whole app.
Why an encrypted backup needs its password
An encrypted backup protects Manifest.db as well as the files. Without the password you cannot run the queries above at all, and the hashed files are ciphertext that renaming will not turn into anything. Yado unlocks the backup's keybag with the password, decrypts the manifest, and then decrypts each file with its own key when you export it. The names in Info.plist stay readable in an encrypted backup, which is why App Files can still show app names after the unlock.
Apple's page on encrypted backups says you need the password to use the backup, and that if you reset it you can make a new backup but cannot use the earlier encrypted ones. If you are choosing whether to encrypt, encrypt an iPhone backup on Mac covers the trade-offs.
Browse and export app files in Yado
In the Overview tab, open the backup card's Manage button, find the backup under Existing Backups, move the pointer over its row and click Browse Contents. The Browse Contents link at the end of the phone's backup line at the top of that panel opens the same page.
- If the backup is encrypted, enter its password and click Unlock.
- In Backup Contents, open App Files. The number beside it is how many apps have a container in this backup.
- Each row is an app, with its name over its bundle ID. Use Search to match an app's name, its bundle ID or any file path inside its container.
- Open an app to see its files by path, each with the size the backup recorded. Move the pointer over a row and click Export to copy that one file to a folder you choose.
- Click Export All at the bottom to copy the whole app. Yado makes a folder named after the app and writes every file at the path it had in the container.
A single file lands under its own name beside whatever the folder already holds, with a number added if that name is taken, never over an existing file, and keeps its original modification date. When the export finishes, Finder shows the result. On the list of apps, Export All copies every app's files into one App Files folder, one subfolder per app, which can be large.
Yado checks each path before writing it. A path that would climb out of the destination folder or pass through a link is refused, and if any file fails the export reports that it could not finish. The sizes shown come from the backup's record, and a database the app was writing during the backup can be a little different from that number while the file itself is intact.
Everything is read from the backup on your Mac, so no iPhone has to be connected. The decrypted copies exist only in a scratch folder until you close the browser. For messages, contacts and notes, which have their own readers, see view an iPhone backup on Mac and export iPhone messages to Mac.
When the app or its files are missing
The app is not in the list. App Files shows an app only if the backup holds at least one regular file in its AppDomain- container. An app installed after the backup, an unfinished backup, or an app whose data lives in a group container will not appear. Check the backup's date in the browser's header, and try an earlier backup from Existing Backups.
The app is there but the files you want are not. Look for the cause in order. The file may live in Library/Caches or tmp, which are not backed up. The developer may have excluded it as re-creatable. The data may be in iCloud or on the app's own servers, which a computer backup leaves out. A short list with small sizes usually means this, and the fix is in the app's own export or sync, not in the backup.
You can read the file but it looks like gibberish. Many apps store their data in SQLite databases or property lists, and some encrypt their own databases with a key kept outside the backup. Exporting gives you the bytes the backup holds, and what they mean depends on the app. Open a copy of a database with sqlite3, not the original.
The export fails. Make sure the destination folder is writable and has room, then try the single file first to see which one is the problem.
FAQ
Can I get an app's data into the same app on another iPhone?
Exporting files is not a restore. A restore from the backup puts all the data back on a phone, as described in restore an iPhone from a backup.
Does the iPhone have to be connected?
No. Both the sqlite3 route and Yado work from the backup folder on the Mac alone.
Why is the app's name shown as a long ID?
The manifest stores only the bundle ID. Names come from the App Store metadata in Info.plist, and an app without an entry there shows its bundle ID.