iLEAPP v2026.4.5

iLEAPP, short for iOS Logs, Events, And Plists Parser, is an open source digital forensics tool designed to analyze forensic extractions from iOS and iPadOS devices. It parses artifacts from iPhones and iPads and generates structured reports in formats including HTML, TSV, timeline, KML, and LAVA. The project currently supports iOS and iPadOS 11 through current versions.

Designed primarily for digital forensic investigators and incident response work, iLEAPP can process extracted file systems, iTunes and Finder backups, compressed archives, and individual files. It is also available with both graphical and command line interfaces.

Features

iLEAPP provides a large collection of artifact parsing modules for iOS and iPadOS forensic analysis.

Key features include:

  • iOS and iPadOS forensic artifact parsing

  • Support for iOS and iPadOS 11 through current versions

  • Graphical user interface

  • Command line interface

  • iTunes and Finder backup parsing

  • Encrypted backup support

  • Extracted file system analysis

  • ZIP, TAR, and GZIP input

  • Single file analysis

  • Raw disk image and E01 acquisition support

  • HTML reports

  • TSV output

  • Timeline generation

  • KML output

  • LAVA output

  • Custom parsing profiles

  • Case data support

  • Selective artifact modules

  • Custom artifact modules

  • Artifact path listing

  • Cross-platform support

  • Pre-built releases that do not require Python installation

The project uses individual artifact modules that can be loaded dynamically. This modular approach makes it possible to add support for new artifacts without redesigning the entire application.

Download iLEAPP v2026.4.5 - Software Mirrors

iLEAPP v2026.4.5 for Windows

iLEAPP-2026.4.5-windows-x64-portable.zip | 70.12 MB

iLEAPP-2026.4.5-windows-arm64-portable.zip | 60.03 MB

iLEAPP v2026.4.5 for macOS

iLEAPP-2026.4.5-macos-x64.dmg | 66.61 MB

iLEAPP-2026.4.5-macos-arm64.dmg | 63.87 MB

iLEAPP v2026.4.5 for Linux

iLEAPP-2026.4.5-linux-x64.AppImage | 89.31 MB

iLEAPP-2026.4.5-linux-arm64.AppImage | 85.89 MB

iLEAPP v2026.4.5 Source Code

iLEAPP v2026.4.5 Source code (zip)

iLEAPP v2026.4.5 Source code (tar.gz)

iLEAPP v2026.4.5 Release Notes:

iLEAPP v2026.4.5

  • Python 3.11 or newer is now required to run from source. Python 3.15 is listed as supported, with Windows wheels for it and for ARM64.
  • Windows downloads are now one portable file per architecture, with no installer.
  • Staged files: --hash, or the window's new checkbox, records a SHA-256 for staged files, and the times their container recorded: zip NTFS and extended timestamp fields, tar headers (including GNU and PAX access and change times and the libarchive creation time), L01 and AD1 entries, FAT and exFAT entries (as stored, with no zone applied), and the ext, APFS and HFS+ times qnxprobe 1.76 reads.
  • Zip times: on four-value extended timestamp blocks (as in GrayKey style files_full.zip) the creation time comes from the fourth value, and Cellebrite CLBX zips take their times from metadata.msgpack, since in the CLBX zips tested every extended timestamp slot holds the access time. This adds msgpack as a dependency. Background: the blog post.
  • Reading acquisitions with -t raw: qnxprobe goes from 1.58 to 1.76 and ewfprobe to 0.15.0. LVM2 logical volumes (including split, striped and RAID1 ones), LUKS containers opened with their passphrase, RAID member images read together, and FAT12 and FAT16 are read. Free space, a flash filesystem's deleted files and NTFS directory indexes are offered to artifacts that ask for them. Each file read through missing acquisition data is named.
  • Encrypted iTunes backups: files are staged at their stored length, not the manifest's Size, and the decrypted Manifest.db is staged without its padding block.
  • Tar links are read as the member they point to, and corrupt zip members are skipped instead of stopping the run. A WAL-mode SQLite database staged without its -wal is opened read-only with immutable=1.
  • Unified logs and sysdiagnose: logarchive is read from a sysdiagnose, with new artifacts for unlock, buttons, orientation, gestures, USB host, wake source, AirDrop, calls, weather, family hotspot, charging state, app snapshots, container entries and data usage. From @danjethh: URL and link opens, camera and microphone capture sessions, TCC authorization cache and location manager state, Screen Time (ManagedSettings), BatteryUI per-app runtime, and Container Manager State for iOS 27. Unified Log filtering is faster and reports progress.
  • Life360: 32 new artifacts from @CyberMike81, including crash-detection diagnostics and recovered history. Also from @CyberMike81, generic Mixpanel and Crashlytics artifacts.
  • New: Apple Watch photo collections, registry history, Mail registry and Weather Cities; Photos Graph Moment Locations, routined visits and vehicle events, and Cache Locations course, altitude and accuracy from @charpy4n6; KeepSafe photo vault; Reddit post and subreddit history; Anonymous Chat from @darren33; Emoji Recents, Usage and Preferences from @ayobamiseun; an account-wide encryption key hash artifact from @Rugikex; offline DJI TXT flight records from @Blackwater1224; Discord - Servers; Battery Center; Alarms sleep alarms; Apple Music search, Media Experience, Media Remote, Photos Recent Searches, Hashtag Images and supplementary WebKit cache parsers.
  • Snapchat messages gain Local Media ID and Created On Device from @segumarc, and Bumble works with LAVA's conversation view from @frahmco.
  • Fixes: Telegram messages no longer stop on a short media ID (@mvanhorn) and are kept when a media entry cannot be read, the Claude app's storage is found after version 1.261005.20 and ChatGPT temporary media come only from a marked ChatGPT container (@ayobamiseun), GroupMe reads every GroupMe.sqlite, iTunesMetadata dates are read as UTC, the iOS version readers run first, and Media Cache rebuilds cached video and audio.
  • An accuracy review of the artifact modules: descriptions, notes and headers were checked against the code and the data, values are reported as stored, unsupported labels are gone, and rows that were being dropped are kept.
  • Apple build ID to iOS version table updated by @Johann-PLW. Contributor docs: a helper functions guide.

New Contributors

  • @CyberMike81 made their first contribution in #2431
  • @ayobamiseun made their first contribution in #2426
  • @frahmco made their first contribution in #2317
  • @segumarc made their first contribution in #2472
  • @danjethh made their first contribution in #2311
  • @darren33 made their first contribution in #2166
  • @ForensikITGmbH made their first contribution in #2491
  • @dajiaohuang made their first contribution in #2525
  • @Blackwater1224 made their first contribution in #2536
  • @mvanhorn made their first contribution in #2564
Full Changelog: v2026.4.4...v2026.4.5

Which file to download

  • Windows 10 or 11, 64-bit Intel or AMD: -windows-x64-portable.zip
  • Windows 11 on ARM: -windows-arm64-portable.zip
  • macOS, Apple silicon: -macos-arm64.dmg
  • macOS, Intel: -macos-x64.dmg
  • Linux, 64-bit Intel or AMD: -linux-x64.AppImage
  • Linux on ARM: -linux-arm64.AppImage
Every download holds one program, ileapp. Started without arguments, from the Applications folder or a double-click, it opens the window. Given arguments in a terminal, it is the command line. On macOS the command line is inside the app:
bash
/Applications/iLEAPP.app/Contents/MacOS/ileapp --help
For tools that run iLEAPP themselves. The options, output and exit codes of ileapp are those of earlier releases, but there is no ileappGUI any more, since ileapp without arguments opens the window. On Windows the zip holds the whole program as one file, ileapp.exe, which can be put wherever the tool expects it; there is no installer. The executable inside the macOS app needs the folder it came in; on Linux the AppImage is the whole program. ileapp.exe on Windows unpacks itself to a temporary folder each time it starts, so it takes a few seconds to start, and it does not run where a policy (AppLocker, WDAC) forbids running programs from the temporary folder. There, run iLEAPP from source; the README has the steps.

First launch

The macOS disk images are signed with a Developer ID and notarised by Apple, so they open without a warning. The Windows binaries are not signed yet, so SmartScreen says "Windows protected your PC" the first time. Choose More info, then Run anyway. On Linux, make the AppImage executable once (chmod +x iLEAPP-*.AppImage). It needs FUSE to start; where FUSE is not available, run it with --appimage-extract-and-run. If you would rather not clear a warning, run from source instead; the README has the steps.

Verify what you downloaded

SHA256SUMS.txt covers every file in this release. On macOS or Linux, from the folder you downloaded into:
bash
grep  SHA256SUMS.txt | shasum -a 256 -c -
Use sha256sum in place of shasum -a 256 on Linux. On Windows, in PowerShell:
powershell
(Get-FileHash -Algorithm SHA256 .\).Hash
and compare it with the line in SHA256SUMS.txt, which is lower case.

Linux

The build is made on Ubuntu 22.04, so it needs glibc 2.35 or newer and will not start on an older distribution.

Code signing policy

The code signing policy covers Windows signing, team roles and privacy.

iLEAPP is a practical tool for investigators who need to turn raw iOS forensic data into information that can be reviewed and analyzed more easily.

Its biggest strength is the breadth of artifact parsing. Instead of manually searching through plist files, databases, logs, and other application data, iLEAPP processes known artifact locations and produces structured output. This can significantly reduce the amount of repetitive work involved in an iOS forensic examination.

The GUI makes the application accessible to investigators who do not want to work exclusively from a terminal. You can select the input type, source path, output directory, and modules to process directly from the interface. For repeatable workflows and automation, the command line interface provides more control.

Support for iTunes and Finder backups is particularly useful because these backups are a common source of forensic data. Encrypted backups are also supported, with the GUI able to request the backup password when encryption is detected.

Another useful feature is the ability to use profiles to limit which artifact modules are processed. This can reduce unnecessary processing when an investigation is focused on a particular type of evidence.

The raw image functionality is also notable. iLEAPP can work directly with supported disk images and EnCase EWF acquisitions without requiring them to be mounted first. The tool reads only the files requested by the relevant artifact modules, which can make targeted analysis more convenient.

The main limitation is that iLEAPP is a forensic parser, not a complete forensic investigation platform. It does not replace a full forensic suite for acquisition, evidence management, advanced timeline analysis, or broader case management.

It also requires some understanding of iOS artifacts and forensic methodology. The generated reports are useful, but investigators still need to understand what individual artifacts mean and how reliable they are within the context of a case.

For professional iOS artifact analysis, however, iLEAPP provides a strong combination of automation, flexibility, and broad artifact coverage.

Performance and Compatibility

iLEAPP is available for Windows, macOS, and Linux. Pre-built releases are provided for Windows x64, macOS Intel, macOS Apple Silicon, and Linux x86_64.

The tool can process several types of forensic input, including extracted file systems, ZIP archives, TAR archives, GZIP files, iTunes and Finder backups, and individual files. Current source documentation also supports raw disk images and E01 acquisitions.

Processing time will depend on the size of the extraction, number of artifacts, storage performance, and modules selected. Large forensic extractions can naturally require substantial disk I/O and processing time.

The ability to select modules and load profiles can help reduce unnecessary processing when only specific artifacts are relevant to an investigation.

System Requirements

The easiest option is to use one of the pre-built releases, which does not require a separate Python installation.

For running iLEAPP from source, the project currently requires:

  • Python 3.10 through 3.14

  • Git

  • Python dependencies from requirements.txt

  • Tkinter for the GUI on Linux

On Ubuntu and similar distributions, Tkinter can be installed through the distribution package manager.

Pre-built packages are available for:

  • Windows x64

  • macOS Intel

  • macOS Apple Silicon

  • Linux x86_64

Pros and Cons

Pros

  • Free and open source

  • Designed specifically for iOS and iPadOS forensics

  • Supports iOS and iPadOS 11 through current versions

  • Large collection of artifact modules

  • GUI and CLI interfaces

  • Supports encrypted iTunes and Finder backups

  • Supports multiple extraction formats

  • Generates several useful report formats

  • Supports custom parsing profiles

  • Cross-platform

  • Pre-built releases available

  • Supports raw disk images and E01 acquisitions

  • Active development and contributions from the DFIR community

Cons

  • Intended for forensic users rather than general users

  • Requires forensic knowledge to interpret results correctly

  • Not a complete digital forensics suite

  • Large extractions can require significant processing time

  • Artifact coverage depends on the available modules and the data present in an extraction

How to Install

The simplest installation method is to download a pre-built iLEAPP release for the operating system being used. These packages include the required application components and do not require Python to be installed separately.

Windows users can use the GUI or CLI package. macOS users can choose between Intel and Apple Silicon builds, while Linux users can use the provided AppImage.

For developers or investigators who need the latest source changes, iLEAPP can also be installed from source using Python. The project recommends creating a virtual environment and installing the dependencies from requirements.txt.

Once installed, select the appropriate input type, provide the extraction or backup path, choose an existing output directory, and start the parsing process. The resulting reports can then be reviewed using the generated HTML, TSV, timeline, KML, or LAVA output.

Frequently Asked Questions

What is iLEAPP?

iLEAPP is an open source forensic tool for parsing iOS and iPadOS logs, events, property lists, databases, and other forensic artifacts.

What does iLEAPP stand for?

iLEAPP stands for iOS Logs, Events, And Plists Parser.

Which iOS versions does iLEAPP support?

The project currently supports iOS and iPadOS 11 through current versions.

Can iLEAPP analyze iPhone backups?

Yes. iLEAPP supports iTunes and Finder backup folders, including encrypted backups.

Does iLEAPP support encrypted backups?

Yes. Encrypted iTunes and Finder backups are supported. The GUI can prompt for the backup password when encryption is detected.

Does iLEAPP have a GUI?

Yes. iLEAPP provides both a graphical interface and a command line interface.

Can iLEAPP run on Windows?

Yes. Pre-built Windows x64 GUI and CLI packages are available.

Can iLEAPP run on Linux?

Yes. A Linux x86_64 AppImage is available, and the software can also be run from source with Python.

Can iLEAPP analyze E01 forensic images?

Yes. Current versions can process raw disk images and EnCase EWF E01 acquisitions directly.

Is iLEAPP a complete forensic suite?

No. iLEAPP focuses on parsing iOS and iPadOS artifacts. It is best used as part of a broader digital forensics workflow rather than as a complete acquisition and case management platform.

iLEAPP v2026.4.5
Free
Software Informations:
Developer:

Operating System:
Windows / macOS / Linux
Date Added:
2026-10-24T21:07:22.593Z
Categories:

Post a Comment/Report Broken Link: