A fair look at two tools for extracting data from iPhone backups — from someone who built one of them. Including the places iMazing is the better call.
Many people end up using both.
| OpenExtract | iMazing | |
|---|---|---|
| Price | Free, forever | Paid license per user/device |
| License | MIT (open source) | Proprietary (closed) |
| Source code auditable | Yes | No |
| Platforms | Windows · macOS · Linux | Windows · macOS |
| Processing | 100% local | 100% local |
| Encrypted iPhone backups | Supported | Supported |
| Messages (SMS / iMessage) | Extract + export | Extract + export |
| Photos & videos with EXIF | Yes | Yes |
| Call history | Yes | Yes |
| Contacts & notes | Yes | Yes |
| Voicemails | Yes | Yes |
| Safari history (encrypted) | Yes | Yes |
| Export to PDF / CSV / HTML | Yes | Yes |
| Live device management | No | Yes |
| Cross-device transfers | No | Yes |
| App / music / ringtone sync | No | Yes |
| Paid commercial support | Community · GitHub | Yes, vendor-backed |
| Manages the phone itself (apps, ringtones, live transfers) | No, reads backups only | Yes |
iMazing reads the same iTunes/Finder backup format Apple writes. So does OpenExtract. You don't need to re-back-up anything.
Manifest.db works.No. It's an independent project that reads the documented Apple iPhone-backup format. Any compliant tool can read those files.
Exports keep the date, time and sender of every message, so they read clearly when printed. Whether a court accepts them depends on your jurisdiction and your case, so ask your lawyer.
Yes. Supply the password; decryption happens on your laptop. Encrypted backups contain more data (saved passwords, Safari history).
Source is public on GitHub. Installers are code-signed. Nothing you extract is ever uploaded, and update checks are off unless you turn them on. You can verify all of that yourself.
Yes. iMazing writes standard Apple backups unless you configure it otherwise.