Static compilation requires an additional linker flag
The only change listed for img4tool Build 226 concerns static compilation. The release note says that “-lcompression” must be passed to the next project, adding a linker requirement for this build scenario.
This is build guidance rather than a change to img4tool’s documented file-handling features. The release notes list no other changes, so users working with an existing build should not expect a newly documented command or format capability from Build 226.
Ubuntu and macOS archives are included
Build 226 includes buildroot_ubuntu-latest.zip and buildroot_macos-latest.zip archives. These identify the supplied host-platform builds as Ubuntu and macOS versions of the utility.
The build was published under the exact identifier 226 on November 14, 2026. The release information does not provide installation or update instructions, so the archives are best understood as the available build artifacts for this release.
What img4tool handles
img4tool is a command-line utility for manipulating IMG4, IM4P and IM4M files. Its documented operations include printing file contents, extracting components, creating IMG4 and IM4P files, changing an IM4P type, converting SHSH data to IM4M, and verifying signing data against a BuildManifest.
For inspection, the tool can print an IMG4, IM4P or IM4M, with options to print all IM4M information or only the embedded IM4P. Extraction commands can retrieve an IM4P or IM4M from an IMG4, an IM4P from SHSH data, or a payload from an IM4P.
The documented creation workflows assemble an IMG4 from an IM4P, optionally adding an IM4M or SHSH file. The tool can also create an IM4P with a specified type, such as ibss, and can attach a custom description. A separate rename operation changes the IM4P type of an existing file.
Payload extraction supports both ordinary output and decryption when the required initialization vector and key are supplied. The README also documents verification of IM4M or SHSH APTicket data against a BuildManifest, along with verification that an IMG4 containing an IM4P and IM4M is correctly signed for that manifest.
What changes for users
Build 226 is most relevant when producing a static build or passing img4tool into another compilation step. In that situation, the documented “-lcompression” requirement is the release’s practical action point. For users simply using the supplied Ubuntu or macOS build artifacts, the release notes describe no functional changes to the commands or file operations listed in the README.



