Skip to content

Communications

AddressBook.sqlitedb: iOS Contacts Database

iOS contacts in AddressBook.sqlitedb: ABPerson and ABMultiValue tables, backup location, timestamps, accounts, and how to join contacts to messages and calls.

Location
/private/var/mobile/Library/AddressBook/AddressBook.sqlitedb (backup: HomeDomain, Library/AddressBook/AddressBook.sqlitedb, fileID 31bb7ba8914766d4ba40d6dfb6113c8b614be442)
Evidence area
Proves
Which people and organisations the owner stored, with phone numbers, emails, addresses, notes and the account each contact came from, plus when each record was created and last modified
Timestamps
Cocoa time in seconds (add 978307200 for Unix time), UTC, on ABPerson.CreationDate and ModificationDate
Acquisition
Unencrypted backup is enough (HomeDomain). A full file system extraction adds the -wal file and freelist pages
Retention
Until the contact is deleted locally or through a synced account (iCloud, Exchange, Google); deleted rows may survive in freelist pages for a while
Collection
idevicebackup2, iMazing, Full file system extraction

What it is

AddressBook.sqlitedb is the SQLite store behind the Contacts app and every app that reads contacts through Apple's frameworks. It holds one row per person or organisation, each with any number of phone numbers, email addresses, postal addresses, URLs, related names and dates. A companion database, AddressBookImages.sqlitedb, stores contact photos.

In a case it rarely proves anything alone. Its value is as a lookup table: it turns the bare handles in sms.db, CallHistory and third-party messengers into names, and its creation and modification dates can show when a relationship was recorded on the device.

Where it lives

SourcePathNotes
Full file system/private/var/mobile/Library/AddressBook/AddressBook.sqlitedb (+ -wal, -shm)Main store
Full file system/private/var/mobile/Library/AddressBook/AddressBookImages.sqlitedbContact pictures and thumbnails
iTunes / Finder backupHomeDomain, Library/AddressBook/AddressBook.sqlitedb31/31bb7ba8914766d4ba40d6dfb6113c8b614be442
iTunes / Finder backupHomeDomain, Library/AddressBook/AddressBookImages.sqlitedbcd/cd6702cea29fe89cf280a76794405adb17f9a0ee

If the owner syncs contacts with iCloud, Exchange or Google, the local store is a synchronised copy. A contact deleted on another device disappears here too, and the authoritative history may sit with the account provider rather than on the phone.

What it proves

  • The names and details the owner (or a sync source) stored for a person or organisation.
  • When a contact record was created and last modified on this device or account.
  • Which store each contact belongs to (local "On My iPhone", iCloud, an Exchange or CardDAV account).
  • Free-text notes, nicknames and job titles, which sometimes carry the most interesting content.

A name in the address book is what the owner typed, not a verified identity. Two contacts can share a number, and a number can be saved under a nickname: say so in the report.

Key fields

Table / columnMeaning
ABPerson.ROWIDContact identifier used by the other tables
ABPerson.First, Last, Middle, Nickname, Organization, JobTitleName fields
ABPerson.NoteFree-text note
ABPerson.CreationDate, ModificationDateRecord timestamps (Cocoa seconds)
ABPerson.StoreIDForeign key to ABStore (the account the contact belongs to)
ABMultiValue.record_idForeign key to ABPerson.ROWID
ABMultiValue.propertyKind of value, e.g. 3 = phone number, 4 = email address
ABMultiValue.labelForeign key to ABMultiValueLabel.ROWID (_$!<Mobile>!$_, _$!<Home>!$_, custom labels)
ABMultiValue.valueThe number or address as typed
ABMultiValueEntryComponents of structured values such as postal addresses
ABGroup, ABGroupMembersContact groups

The property codes above are the ones most parsers rely on; confirm them on a test device if a value type matters to your conclusions.

Timestamps

CreationDate and ModificationDate are Cocoa time in seconds. A sync can rewrite ModificationDate without any user edit, and restoring a device from backup or signing in to a new account can reset both. Treat them as "no later than" markers.

SELECT p.ROWID, p.First, p.Last, p.Organization,
       datetime(p.CreationDate + 978307200, 'unixepoch') AS created_utc,
       datetime(p.ModificationDate + 978307200, 'unixepoch') AS modified_utc,
       CASE mv.property WHEN 3 THEN 'phone' WHEN 4 THEN 'email' ELSE mv.property END AS kind,
       l.value AS label, mv.value
FROM ABPerson p
LEFT JOIN ABMultiValue mv ON mv.record_id = p.ROWID
LEFT JOIN ABMultiValueLabel l ON mv.label = l.ROWID
ORDER BY p.ROWID;

Retention

Contacts persist until they are deleted locally or through a synced account. Deleted records are removed from ABPerson, but their bytes can remain in unallocated SQLite pages and in the WAL until the database is vacuumed. A full file system extraction gives you those pages; a backup gives you only the logical database.

Collection

  • Backup: a standard iTunes or Finder backup includes both databases in HomeDomain. Resolve them through Manifest.db or by their file IDs.
  • Full file system: collect AddressBook.sqlitedb with its -wal and -shm files, and AddressBookImages.sqlitedb.
  • Work on hashed copies only. Opening the original in a SQLite tool can merge the WAL and destroy recoverable records.

Parsing

  • iLEAPP produces a contacts report from a backup or an extraction.
  • sqlite3 or DB Browser for SQLite with the query above.
  • iMazing shows contacts from a backup in a GUI, useful for a quick review with non-technical stakeholders; export for analysis rather than screenshotting.

Investigator tips

  • Normalise every number to E.164 before joining with handle.id in sms.db or ZADDRESS in CallHistory. Saved numbers are stored as typed, with spaces and local prefixes.
  • A contact that exists in messages but not in the address book was never saved, or was deleted: check freelist pages and the WAL before concluding.
  • Compare StoreID across contacts. A block of contacts created in the same second usually came from an account sync or an import, not from manual entry.
  • Contact photos in AddressBookImages.sqlitedb can identify a person when the name field is a nickname.

See also