IPAHow to send an app to a client for testing
To send an app to a client for testing: upload your .ipa (iOS) or .apk (Android) at ipalinked.com, then send the client the generated link or QR code. They open it on their phone and install in one tap — iOS installs over the air from Safari. It is free, needs no account on either side, and links can be password-protected. For iOS the build must be signed for the client's device (ad-hoc with their UDID, or enterprise).
The fastest way (no accounts, no store)
- Build your app — export an .ipa for iOS or .apk for Android.
- Upload it at ipalinked.com — drag and drop, up to 500MB.
- Send the link — paste it in email/WhatsApp/Slack, or let the client scan the QR code.
- Client installs — Android downloads and installs directly; a signed iOS build installs over the air from Safari.
For iOS clients: the signing requirement
Apple only lets an ad-hoc iOS build install on devices whose UDID is registered. Ask the client for their UDID first — they can get it in 30 seconds with our free UDID finder — then build ad-hoc with it included. Otherwise they'll see "Unable to Install". Enterprise-signed builds skip the UDID step.
Why not just email the file or use a cloud drive?
Email blocks .ipa/.apk attachments, and cloud drives show a generic file page with no install flow. IPALinked gives a proper install page with a QR code, an OTA button for iOS, a download counter so you know the client actually installed it, and links that auto-expire after 7 days so old builds don't linger.
Keeping client builds private
Turn on password protection when you upload, and share the password separately. Only people with both the link and password can install.