Convert DMG to IPA

A macOS installer may arrive as a DMG, while an iPhone or iPad deployment requires an IPA. The files cannot normally be translated because a DMG usually contains macOS software, whereas an IPA contains an iOS or iPadOS application built and signed for Apple mobile platforms.

What the DMG format is

DMG is Apple’s disk-image format for macOS. A DMG can contain a compressed or encrypted HFS+, APFS, or other disk-image volume with an application, installer package, documentation, or supporting files. macOS users commonly receive applications in DMG images and mount them in Finder or Disk Utility.

What the IPA format is

IPA is an archive used to distribute iOS and iPadOS applications. It is usually a ZIP archive with a top-level Payload directory containing an application bundle, for example Payload/MyApp.app.

An IPA exported from Xcode may be intended for development, ad hoc, enterprise, or another authorized distribution method. A device-installable package requires an iOS or iPadOS build, a compatible architecture, an Apple code signature, and provisioning or distribution data appropriate to that method. An IPA is therefore more than a renamed application archive.

How to convert a DMG to IPA

There is no general DMG-to-IPA conversion. First inspect the image to determine whether it contains an existing IPA, an iOS application bundle, or only a macOS application.

1. On macOS, open the DMG in Finder or Disk Utility, or mount it read-only with hdiutil attach -readonly /path/to/file.dmg.
2. Inspect the mounted volume for an existing .ipa file. If one exists, copy it out; no conversion is required.
3. If the volume contains an .app bundle, identify its platform before packaging it. A macOS application cannot become an iOS application by renaming the extension, compressing the bundle, or placing it in a Payload directory.

If the DMG contains a complete, already-built iOS or iPadOS .app, packaging it as an IPA is possible, but this is archiving rather than conversion. Use a working directory and preserve the bundle structure:

1. Create the required directory with mkdir -p work/Payload.
2. Copy the complete bundle with ditto /Volumes/VolumeName/MyApp.app work/Payload/MyApp.app.
3. Create the archive with cd work && zip -qry ../MyApp.ipa Payload.
4. Check its layout with unzip -l ../MyApp.ipa. The listing should start with Payload/MyApp.app/, not an extra enclosing directory.
5. Unmount the image with hdiutil detach /Volumes/VolumeName when finished.

This procedure does not sign the application or repair an invalid signature. The bundle must already be an iOS or iPadOS device build with valid signing and provisioning data. A simulator .app is not a device-installable IPA, and a macOS .app is not an iOS build.

Building a valid IPA with Xcode

For software you own and can rebuild, use the project’s iOS or iPadOS target in Xcode. Select the appropriate scheme, choose Product → Archive, open the archive in Organizer, select Distribute App, and choose the authorized export method. Xcode then produces an IPA with signing and provisioning settings for that distribution route.

If the DMG contains only a Mac application, obtain the developer’s separate iOS version or its source code; there is no tool that recompiles a macOS executable into an iOS executable. App Store applications may also use Apple distribution protections and cannot generally be reconstructed from a Mac installer.

Desktop and online tools

Disk Utility and hdiutil are the suitable macOS tools for mounting and extracting DMG contents. On Windows, 7-Zip can often extract an unencrypted DMG far enough to locate an existing IPA, but APFS, HFS+, encryption, compression variants, and macOS-specific metadata can limit compatibility. 7-Zip cannot build an iOS application or create Apple code signatures.

No reputable online converter can translate a macOS application into an iOS application or generate legitimate Apple signing. Uploading a DMG to an untrusted service can also disclose proprietary software, credentials, or licensed content, so online conversion is not appropriate for this format pair.

Compatibility limitations

A repackaged bundle works only when its executable, embedded frameworks, entitlements, bundle identifier, architecture, provisioning profile, and code signature are mutually consistent and accepted by the intended installation method. Changing a filename extension or placing a Mac application inside Payload does not satisfy any of those requirements.