How to Use AppForShare to Send .apk or .ipa Files to Your Clients
By Afrah Saleem · · 4 min read
To send an .apk or .ipa file to a client with AppForShare, upload the build at appforshare.io, copy the install link or QR code it gives you, and send that to your client. The client opens the link on their phone and installs the app over the air (OTA), with no app store review and no cable.
This guide walks through the process, explains what your client needs on their side, and lists what each plan includes so you can pick the right one.
What is AppForShare?
AppForShare is a service for sharing mobile app builds for testing and review. You upload an Android .apk or an iOS .ipa, and AppForShare creates a private install page with a link and a QR code. Anyone you send the link to can install the build directly on their device.
It is built for one job: getting test builds to the people who need to try them. It is not a general file sharing service, not an app store, and it does not sign or re-sign your builds.
Before you upload
Android builds
Any installable .apk works. Android App Bundles (.aab) cannot be installed directly on a phone, so build an APK for sharing. Your client will be asked once to allow their browser to install apps from unknown sources. See How to enable unknown sources on Android for the exact steps.
iOS builds
Apple only allows OTA installs for builds signed for Ad Hoc, Enterprise, or Development distribution. App Store and TestFlight builds cannot be installed from a link. For Ad Hoc and Development builds, your client's device UDID must be in the provisioning profile, so collect it first with the free UDID finder, add it in the Apple Developer portal, and then sign the build. On iOS 16 and later, your client also needs to turn on Developer Mode to open Ad Hoc and Development builds.
How to send your build in four steps
1. Upload the .apk or .ipa
Go to appforshare.io and drop your file into the upload box, or pick it from your computer. You can upload without an account (guest upload), but a free account gives you larger files, longer link life and password protection. The file size limit depends on your plan (see the table below).
2. Wait for processing
When the upload finishes, AppForShare reads the build and shows the app name, icon, bundle or package ID, version and build number. On Pro and Team you can add release notes so your client knows what changed in this build.
3. Send the link or QR code
Copy the install link and send it by email, chat or any channel your client uses. If they are sitting next to you, they can scan the QR code with their phone camera instead. If the build is confidential, set a password on the link (available from the Free plan up) and share it separately.
4. Your client installs the app
Your client opens the link in the phone's browser (Safari on iPhone) and taps Install. On Android, the APK downloads and the system installer opens. On iPhone, iOS asks for confirmation and the app icon appears on the home screen when it finishes. The install page also shows the app details, so the client can confirm they have the right version.
How long the link stays live
Links do not live forever. How long a link works depends on the plan of the person who uploaded it:
- Guest (no account): 3 days, up to 20 installs per link and 4 per day.
- Free: 7 days.
- Pro and Team: as long as the subscription is active.
Every upload is a new build with its own link, so you can send a fresh link for each version. More detail is in How long will links be available on AppForShare?
Plans at a glance
| Guest | Free | Pro | Team | |
|---|---|---|---|---|
| Price | $0 | $0 | $12/month or $120/year | $39/month or $390/year |
| Max file size | 50 MB | 150 MB | 2 GB | 4 GB |
| Storage | n/a | 2 GB | 25 GB | 150 GB |
| Link life | 3 days | 7 days | While subscribed | While subscribed |
| Bandwidth | 20 installs per link | 10 GB/month | 40 GB/month | 150 GB/month |
Free includes password protected links, QR codes and the UDID finder. Pro adds release notes, install analytics, CI upload tokens and webhooks. Team adds a shared workspace with roles, invited testers, a custom domain for install links and a white-label install page with your own logo and colours. Full details are on the pricing page.
Sharing builds with clients under your own brand
If you send builds to clients often, the Team plan lets you serve install links from your own domain and replace AppForShare branding on the install page with your logo and colours. You can also keep projects private so only testers you invite can open them, and AppForShare emails those testers when a new build arrives.
Frequently asked questions
Does my client need an AppForShare account to install the build?
No. Your client only needs the link or QR code and a phone. Accounts are for the person uploading builds. On the Team plan, private projects can only be opened by testers you invite.
Can I send an App Store or TestFlight build through AppForShare?
No. iOS only allows installs from a link for builds signed Ad Hoc, Enterprise or Development. App Store and TestFlight builds cannot be installed this way, and AppForShare does not re-sign builds.
What is the largest file I can upload?
Guest uploads can be up to 50 MB, Free up to 150 MB, Pro up to 2 GB and Team up to 4 GB.
Can I protect the install link with a password?
Yes. Password protected links are available on the Free, Pro and Team plans. Guest uploads get a QR code and link without a password option.
How long will my client be able to use the link?
Guest links last 3 days, Free links 7 days, and Pro and Team links stay live while the subscription is active.
