How to Install an .ipa File on an iPhone: Every Legit Way (2026)

You can't just double-click an .ipa to install it on an iPhone — iOS only runs apps that are properly signed and delivered through an approved path. For testing, the legitimate ways to install an .ipa are TestFlight, an ad hoc over-the-air (OTA) link, Xcode, Apple Configurator, and OTA distribution tools. This guide covers each, plus why an install fails and how to fix it.

Every method here is for developers and testers installing builds they're authorized to run. None of this involves jailbreaking or pirated apps — those are a different (and unsupported) world.

First: the build must be signed for the device

The single most common reason an .ipa won't install is signing. An ad hoc build only runs on iPhones whose UDID was registered in the provisioning profile before the build was made. If a tester's device wasn't included, the install fails no matter which method you use. (See finding and registering a UDID and provisioning profiles explained.)

The legitimate ways to install an .ipa

1. TestFlight

Upload the build to App Store Connect, invite the tester, and they install through the TestFlight app. No UDID needed, but external testers wait on Beta App Review and builds expire after 90 days.

2. Ad hoc OTA link

Host the signed .ipa with a manifest.plist over HTTPS and open an itms-services:// link on the device — iOS installs it directly. This is the mechanism distribution tools automate (see how OTA installation works). No Mac required on the tester's side.

3. Xcode (Devices and Simulators)

Connect the iPhone to a Mac, open Xcode → Window → Devices and Simulators, select the device, and drag the .ipa into Installed Apps. Good for developers with the device in hand.

4. Apple Configurator

On a Mac, add the device in Apple Configurator, then add the app to push the .ipa. Useful for provisioning several devices at once.

5. OTA distribution tools

Tools like Appisto wrap the ad hoc/OTA mechanism into a one-tap flow: you upload the .ipa, the tester opens a link, and — crucially — their UDID is collected automatically so the build can be signed for them without the manual back-and-forth. It also handles Android .apk files from the same place.

Why it won't install — quick troubleshooting

• "Unable to Install" / nothing happens: the device UDID isn't in the profile → re-register and rebuild.
• "Untrusted Developer": trust the profile under Settings → General → VPN & Device Management (full fix).
• "A valid provisioning profile for this executable was not found": the profile is missing or expired → rebuild with a current ad hoc profile (signing guide).

To be clear: no jailbreak, no cracked apps

Every method above installs builds you're entitled to run for development or testing. Installing pirated or cracked .ipa files, or jailbreaking to bypass signing, is neither supported nor covered here.

Frequently asked questions

Can I install an .ipa without a Mac? Yes — OTA installation (TestFlight, an ad hoc OTA link, or a tool like Appisto) needs no Mac. Only the Xcode and Apple Configurator methods require one.

How do I install an .ipa over the air? Host the .ipa with a signed manifest.plist over HTTPS and open an itms-services link, or let a distribution tool do it. The build must be signed for that device's UDID.

Why does my iPhone say the app can't be installed? Usually the build isn't signed for that device, or the profile/certificate expired. Re-register the UDID, rebuild, and trust the developer profile.

Key takeaways

• You can't double-click an .ipa; installing needs a signed build and an approved path.
• The legit methods are TestFlight, ad hoc OTA, Xcode, Apple Configurator and OTA tools.
• Most failures are signing problems — the device UDID must be in the profile before the build.
• Appisto removes the manual UDID step and installs builds over the air on iOS and Android. For the full picture, see how to distribute an iOS app without the App Store.