Just installed a build? The link you followed was made with BetaDrop. Drop your own .ipa or .apk below and you'll get one exactly like it — free, and your first upload needs no account.
BetaDrop is an online IPA installer: upload an iOS .ipa file and share the OTA install link it returns. Testers tap the link and install straight from Safari. No TestFlight, no cables, no App-Store review. It's free, takes files up to 500 MB, and needs no tester account.
Every iOS developer reaches a point where they need to share a build with testers, clients, or stakeholders. TestFlight isn't always the right tool.
Your build needs to go out immediately. With BetaDrop, there's no waiting for Apple's review process. Upload and share instantly.
Your client doesn't want to install another app. BetaDrop links use native iOS OTA installation. Testers just tap the link and install.
Tired of the extra steps between 'build done' and 'tester has it'? BetaDrop cuts the friction so you get feedback sooner.
Archive your app in Xcode, then in the Organizer choose Release Testing (called Ad Hoc before Xcode 15; in ExportOptions.plist the method is release-testing) or Enterprise. Make sure your testers' UDIDs are registered.
Drag and drop your .ipa file onto BetaDrop's upload area. We support files up to 500 MB, so you never have to compress or strip anything.
Copy the OTA install link or QR code and share it with testers over Slack or email. They tap the link and iOS installs the build. No cable, no App Store.
| Method | Speed | Cost | Setup Friction |
|---|---|---|---|
| BetaDrop | Instant | Free | None |
| TestFlight | 24-48h review | Free | Moderate |
| Diawi | Instant | Freemium | None |
| Firebase | Instant | Free | Complex |
Tempted to just share the .ipa from Drive or Dropbox? iOS cannot install an app from a file link. See why, and what to send instead.
Before you upload your IPA file online, make sure it's signed correctly. OTA distribution works with two types of signing:
Secure OTA Installation
Uses Apple's native itms-services
TestFlight holds external builds for review before testers see them. An IPA uploaded here is installable the moment the upload finishes.
Large games, media-heavy apps and bundled ML models fit without stripping assets. BetaDrop accepts IPA files up to 500 MB.
Testers do not install TestFlight or sign in to anything. They open the link on their device and tap install.
Every upload produces both a link and a QR code, so you can drop it in Slack or point a phone at a screen during a demo.
Files move over TLS and are reachable only through their own unguessable link. Nothing is listed publicly or indexed.
Installs use Apple's own itms-services protocol, the same mechanism enterprise distribution relies on. No profiles or shortcuts.
When a tester cannot install the IPA, it is nearly always one of these four. All are fixable without rebuilding from scratch.
The app installed but iOS will not launch it until the certificate is trusted. On the device, open Settings → General → VPN & Device Management, select your organisation, and tap Trust. This applies to Enterprise-signed builds only.
The device UDID is almost certainly missing from the provisioning profile. Ad Hoc builds only install on devices baked into the profile at signing time, so adding a device means re-signing and re-uploading. Collect UDIDs first with the UDID checker.
OTA installs run through Apple's itms-services protocol, which requires HTTPS and only works in Safari. Chrome, Firefox and in-app browsers such as Slack or Gmail will silently do nothing. Open the link in Safari instead.
Usually a provisioning or entitlement mismatch: the build requests a capability its profile does not grant. Decode the embedded profile to compare entitlements against what the app expects before re-signing.
Useful alongside this page: the UDID checker for collecting device IDs before an Ad Hoc build, the provisioning profile decoder for checking expiry and entitlements, and the IPA inspector for confirming what is actually inside a build.
Uploading in the browser is fine for a one-off build, but most teams want every green build on a device automatically. The BetaDrop CLI runs anywhere your pipeline does: GitHub Actions, GitLab CI, Bitrise, Xcode Cloud, Jenkins. It prints the install link to the build log when it finishes.
If your workflow runs through an AI assistant, the BetaDrop MCP server exposes the same publish step to Claude, Cursor, and other MCP clients, so you can ship a build without leaving the editor.
Your first upload needs no account and stays available for 24 hours, which covers a typical review cycle. Signing in lets you choose how long each build's link lives (up to 7 days on a free account) and adds a dashboard where you can see every active link, revoke one early, or re-share it.
Worth knowing: link lifetime is separate from certificate lifetime. An Ad Hoc or Enterprise provisioning profile expires on its own schedule regardless of how long the download link lives, and once it does, already-installed copies stop launching. Check the profile's expiry date before a long test cycle.
Stop waiting for TestFlight reviews. Get your iOS build into testers' hands in under a minute.
Upload IPA on BetaDrop