How do I upload an APK and share it?

Drop the .apk file in the box at the top of this page. You get an install link and a QR code. Testers open the link on their Android phone and download the app. Android may ask them to allow installs from their browser the first time.

How do I share an IPA without TestFlight?

Upload an IPA signed for ad hoc, development or enterprise distribution. Testers open the link in Safari on their iPhone or iPad and tap Install. For ad hoc and development builds, each device UDID must be in the provisioning profile; the free UDID finder reads it in a few taps.

Yes. Without an account you can share builds up to 50 MB and links last 3 days. A free account raises that to 150 MB, links last 7 days and you get 2 GB of storage. Pro and Team add bigger builds and links that stay up while you are subscribed.

How is this different from TestFlight?

TestFlight needs the build uploaded to App Store Connect and only covers Apple devices. AppForShare takes the IPA or APK file you already have and gives your testers one link, for iOS and Android alike.

AppForShare

iOS and Android test builds

Share your app build with one link.

Upload an APK or IPA online and get an install link and QR code in seconds. Testers install straight from their phone, no store review.

Free to start, no account needed
Works with ad hoc, development and enterprise iOS builds
Used by 6,800+ developers since 2021

Create a free account for uploads up to 150 MB, 7-day links, passwords and version history. See plans

How it works

From build to phone in three steps

Upload

Drop an .ipa or .apk. We read the app name, version, icon and the devices it can run on.

Send the install link to your testers or let them scan the QR code.

Install

Testers open the link on their phone and tap Install. No store review, no extra apps.

Features

Everything a test build needs

iOS and Android

Over the air installs for ad hoc, development and enterprise iOS builds, and direct APK downloads on Android.

Version history

Every upload of the same app lands in one project, so testers can step back to an earlier build.

Device check

See how many devices an iOS build is provisioned for, and which iOS version it needs.

Private links

Protect a build with a password. Download links are signed and expire, so they cannot be passed around.

Big builds welcome

Uploads resume after a dropped connection, so large games and SDK heavy apps get through.

Store readiness check

Each build is checked against current App Store and Google Play rules, like SDK and target API levels, privacy manifests and 16 KB pages, with a plain fix for each issue.

What changed and release notes

See what changed since the last build, from version to permissions and SDKs, and get a draft of tester notes and store "What's New" text.

Launch kit

Answer a few questions and get your App Store and Google Play listing: name, subtitle, keywords and full descriptions, cut to each store's limits, with the notices the stores expect for subscriptions, in-app purchases, background location, Bluetooth, health features, required devices and more.

Store connections

Connect App Store Connect and Google Play with an API key, never a password. Pick the apps a workspace may use, see every call in an activity log, and send clients a link to connect their own accounts.

Release status

See review, approval, TestFlight and rollout state of every shared app on one page. Apple changes arrive the moment they happen, and you get an email or a Slack message when a version is approved or rejected.

Reviews inbox

App Store and Google Play reviews of every shared app in one inbox, kept from the day you connect. Get an AI draft in the reviewer's language, edit it, and post the reply yourself.

Client projects

Share an app's progress with the client you build it for: a task board, deliveries with every version (an install link, a file or a link) and feedback on each one. Your client signs the kickoff agreement and signs off versions online, both sides get a sealed PDF anyone can check at /verify, and you can download an evidence report of the whole project. Your client signs in with an emailed link, no account needed.

Upload from CI

A command line tool and GitHub Action publish every build with release notes, straight from your pipeline.

Questions

How do I upload an APK and share it?: Drop the .apk file in the box at the top of this page. You get an install link and a QR code. Testers open the link on their Android phone and download the app. Android may ask them to allow installs from their browser the first time.
How do I share an IPA without TestFlight?: Upload an IPA signed for ad hoc, development or enterprise distribution. Testers open the link in Safari on their iPhone or iPad and tap Install. For ad hoc and development builds, each device UDID must be in the provisioning profile; the free UDID finder reads it in a few taps.
Is it free?: Yes. Without an account you can share builds up to 50 MB and links last 3 days. A free account raises that to 150 MB, links last 7 days and you get 2 GB of storage. Pro and Team add bigger builds and links that stay up while you are subscribed.
How is this different from TestFlight?: TestFlight needs the build uploaded to App Store Connect and only covers Apple devices. AppForShare takes the IPA or APK file you already have and gives your testers one link, for iOS and Android alike.

Need a device UDID? Use the free UDID finder. More on plans on the pricing page.

Keep your builds together

A free account raises the upload limit, groups versions into projects and adds passwords. Pro keeps links up for as long as you are subscribed.

Create a free account