Online IPA installer: how an install link puts a test build on an iPhone
· 8 min read
"Online IPA installer" is a popular search, and the results are mixed. Some pages explain how developers share test builds. Many others promise to put any app on any iPhone without a computer. This article is only about the first case: you, or your team, built and signed an app, and you want a tester to install it on an iPhone from a link. If you are looking for a way to install modified, cracked or repackaged apps, this is not the page for that, and AppForShare refuses those uploads.
Several services describe themselves this way. InstallOnAir's home page, as read on their site in November 2026, calls it "the online IPA installer for iPhone and iPad" (see installonair.com). AppForShare works the same way for the part described below. The rules come from Apple, not from any one service, so they apply to every tool.
What an install link really does
An iPhone cannot install an .ipa file you download like a photo. It installs apps from the App Store, from TestFlight, or through a small instruction file that tells iOS where the app is. An install link uses that last route. In plain words:
- You upload the .ipa. The service reads the app name, bundle ID and version from it.
- The service publishes a manifest, a short file that says "this app, this version, download it from here".
- The install page has a button with a special address that starts with itms-services:// and points at that manifest.
- When the tester taps it in Safari, iOS asks "Install this app?", downloads the .ipa and starts installing it on the home screen.
- Before the app opens, iOS checks the signature: who signed it, with which profile, and whether this iPhone is allowed to run it.
The last step is the one that matters. The link service does not decide whether the app installs. iOS does, based on how the app was signed. A link service that does not re-sign files, like AppForShare, can only deliver what you uploaded. That is why the type of build is the first thing to check.
Which .ipa files can install from a link
| How the build was signed | Installs from a link? | What it needs |
|---|---|---|
| Ad Hoc | Yes | The iPhone's UDID must be in the provisioning profile |
| Development | Yes | The UDID in the profile, and Developer Mode on iOS 16 and later |
| Enterprise (in-house) | Yes | An Apple Developer Enterprise Program account; the tester trusts the developer once in Settings |
| App Store | No | Use App Store review, or TestFlight for testing |
| TestFlight | No | Testers install through the TestFlight app |
| Unsigned | No | Sign it first |
Ad Hoc is the usual choice for testing outside TestFlight. It works on up to 100 devices of each type per Apple membership year, and every tester's iPhone has to be registered before you build. If you want the full process, read registering devices for Ad Hoc builds.
AppForShare's install page checks some of this for you. If the build is App Store signed or unsigned, or its profile has ended, the page says so above the Install button, so the tester does not try and fail.
What we will not host
An install link is for your own builds. We refuse a few kinds of upload on purpose:
- Builds whose app ID belongs to a large company that never ships test builds through us, such as Google, Meta, Microsoft, Apple, Amazon, Spotify, Netflix, TikTok and similar. These are usually modified copies of popular apps.
- Known malware app IDs.
- Guest uploads whose app name reads like a hack, mod, cheat, injector or cracked app. If it really is your own app, sign in and upload it from your account.
To be clear about limits: this is a check of app IDs and names, not a malware scan. We also do not sign or re-sign .ipa files, and we do not offer help with sideloading tools or with getting around Apple's signing. If an app is not signed for the tester's iPhone, the fix is to sign it properly, which only its developer can do.
Installing a test build, step by step
For the developer
- Export the build with Ad Hoc, Development or Enterprise signing. For Ad Hoc and Development, make sure the tester's UDID is in the profile.
- Upload the .ipa on appforshare.io. No account is needed for files up to 50 MB; a Free account takes 150 MB and lets you set a password. If your build tool gives you a .app folder instead, zip it and upload the .zip (see zipped .app upload).
- Send the tester the link or the QR code.
For the tester
- Open the link in Safari on the iPhone. Links opened inside chat apps or other browsers often do not start the install.
- Tap Install and confirm. Nothing seems to happen in Safari, which is normal.
- Go to the home screen and watch the app icon. It shows a progress ring while it downloads.
- Developer Mode. On iOS 16 and later, Ad Hoc and Development builds need Developer Mode turned on: Settings, Privacy and Security, Developer Mode, then a restart.
- Enterprise builds: open Settings, General, VPN and Device Management, and trust the developer once.
If the icon stays grey or a message says the app cannot be installed, the cause is almost always the signing, not the link. Two guides cover the details: app icon stays grey after install and "integrity could not be verified". The install page also has an Install help list with the same fixes, in 7 languages (see install help).
When the iPhone is not in the build
This is the most common reason an Ad Hoc install fails. The iPhone's UDID is not in the profile, so iOS refuses the app. There is nothing the tester can do on the phone to change that. The developer has to add the device and build again.
Getting the UDID is the part that used to need a computer. It does not anymore:
- The tester opens the free UDID finder on the iPhone and installs a small signed profile. The page shows the UDID and model, and the tester can email it to the developer. Lookups are deleted after 1 day.
- On the result page the tester can tap Remember this device. From then on, every iOS install page on appforshare.io says whether that iPhone model is in this build or not in it yet, before the tester taps Install. Nothing new is stored on our side; it is a signed cookie in that browser. See Remember my iPhone.
- The developer adds the UDID in the Apple Developer portal, remakes the profile and builds again. On Pro and Team, with an App Store Connect connection, saved UDIDs can be registered from the Devices page (see iOS device registration). On Team, Hands free device setup can do the registration and profile remake when testers come through the onboarding link (see hands free device setup).
Before you send a link, you can also check which devices a build includes. The free IPA inspector reads the .ipa in your browser and lists every UDID in its profile, the signing type and when the profile expires. The file is not uploaded.
Why "no computer at all" is not realistic for the developer
Many pages promise to install an IPA without a computer. For the tester, that is true: with a properly signed build, an iPhone and Safari are all they need. For the person who makes the app, it is not. Building and signing an iOS app needs Xcode, which runs on a Mac, or a cloud Mac such as a GitHub Actions runner. The signing identity and profile come from an Apple Developer account. A website cannot do that step for you, and one that claims to usually means it re-signs apps with its own certificate, which is not something AppForShare does or supports.
InstallOnAir's own upload page, as read on their site in November 2026, shows phone visitors a notice that builds are usually made on a computer. That matches what we see: many people who search for an online IPA installer are testers who were sent a file, not developers. If that is you, ask the developer for an install link instead of the .ipa file, and send them your UDID.
If you build on GitHub, AppForShare can set up an iOS workflow that runs on your own GitHub Actions minutes and uploads the result for you (Pro and Team). See GitHub Actions builds.
Picking a service for this
Every honest service follows the same Apple rules, so the difference is in what happens around the install. Things worth checking: file size, how long the link lasts, whether you can set a password, whether the page explains failures, and whether it shows ads. Our free InstallOnAir alternative guide compares the free tiers, and InstallOnAir limits lists theirs in detail.
Common questions
Can I install any IPA file on my iPhone from a link?
No. Only builds signed Ad Hoc with your UDID, Development with your UDID, or Enterprise. App Store and TestFlight builds cannot be installed from a link.
Can AppForShare sign my IPA?
No. We do not sign or re-sign .ipa files. The developer signs the build in Xcode or in CI and uploads it.
Do I need a computer to install a test build?
The tester does not. The developer does, or a cloud Mac, to build and sign the app.
Why was my upload refused?
Builds with the app ID of a large company, known malware IDs, and guest uploads named like a hack or mod are refused. If it is your own app, sign in and upload it from your account.
Is an online IPA installer the same as sideloading?
Not in the sense used here. An install link delivers a build that Apple's signing already allows on that iPhone. It does not get around signing, and we do not help with tools that do.
