How do I upload an APK and get a direct link?

Drop the .apk in the upload box on this page. When it finishes you get an install link and a QR code. Anyone who opens the link on an Android phone can install the app.

Yes. Without an account you can share an APK up to 50 MB for 3 days. A free account takes up to 150 MB with 7 day links. Pro and Team take bigger builds and keep links live while you subscribe, and Pro starts with a 7 day free trial.

Do testers need an account or an app?

No. They open the link in the phone's browser and install. No sign in and no extra app.

Why does Android block the install?

Android installs apps from outside Google Play only after the tester allows installs from their browser once. The install page shows the steps. A Play Protect warning can be passed with Install anyway when the tester trusts the source.

Can I share the APK with a QR code?

Yes. Every upload gets a QR code next to the link. Testers scan it with the phone camera and land on the same install page.

How long does the link last?

3 days without an account, 7 days with a free account, and as long as you subscribe on Pro and Team.

Can I upload an .aab file?

Yes, with a free account. AppForShare turns it into one APK that testers install from the link.

AppForShare Create a free account

APK upload online

Upload an APK and share it with a direct link

Drop your .apk in the box on this page. When the upload finishes, AppForShare gives you a direct install link and a QR code. Anyone you send the link to opens it on an Android phone, taps Install and the app installs over the air (OTA), with no Google Play listing and no account on their side.

Without an account you can share an APK up to 50 MB, and the link stays live for 3 days. A free account takes builds up to 150 MB with 7 day links, and Pro and Team keep links live while you subscribe.

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

How it works

Step 1
Upload the APK
Drag the .apk onto the upload box or press Choose file. We read the app name, version and icon from the file.
Step 2
Copy the direct link
You get an install link and a QR code. Paste the link into a chat or an email, or show the QR code on your screen.
Step 3
Testers install on Android
The tester opens the link on the phone and taps Install. The first time, Android asks them to allow installs from their browser; the install page shows the steps in their language.
Step 4
Keep track of it
Without an account, keep the private manage link: it shows installs and time left, and ends the link sooner or deletes the build. With an account, every upload of the same app lands in one project.

What the direct link opens

The link opens an install page for your build, not a bare file. On the phone it shows the app name, icon and version with an Install button that downloads the APK. Download links are signed and expire, so the file itself is not passed around without the page.

The same page works for an iPhone build: upload an .ipa and the link installs it on iPhone and iPad.

Share an IPA online

Installing an APK outside Google Play

Android installs an APK from a link once the tester allows it for the browser they use, under Install unknown apps. Google Play Protect may warn about an app it does not know yet; a tester who trusts you can choose Install anyway.

If Android says App not installed, a copy of the app signed with a different key is already on the phone. Uninstall that copy first, then install from the link again.

Allow installs from unknown sources

Have an .aab instead of an APK?

Flutter, React Native and Android Studio often build an Android App Bundle (.aab), which a phone cannot install. With a free account, upload the .aab as it is: AppForShare turns it into one APK that testers install from the link, signed with a test key made for your account, or with your own upload keystore on Pro and Team.

An APK signed with the test key cannot update the Google Play version of the app; testers uninstall that version first. The install page says so.

How .aab uploads work

Every upload is checked

Every upload, also without an account, is checked for known malware right after the link is issued. A build that matches takes no installs until a person at AppForShare reviews it. AppForShare shares app builds only: it is not a general file host and not an app store.

Good to know

Without an account a link takes 20 installs, at most 4 a day. Guest and Free builds of one app share 100 installs a month; Pro and Team have no install cap.
Links shared without an account have no password. A free account adds a password per build.
AppForShare does not re-sign or change an uploaded APK: testers install it exactly as you built it.

Questions

How do I upload an APK and get a direct link?: Drop the .apk in the upload box on this page. When it finishes you get an install link and a QR code. Anyone who opens the link on an Android phone can install the app.
Is APK upload free?: Yes. Without an account you can share an APK up to 50 MB for 3 days. A free account takes up to 150 MB with 7 day links. Pro and Team take bigger builds and keep links live while you subscribe, and Pro starts with a 7 day free trial.
Do testers need an account or an app?: No. They open the link in the phone's browser and install. No sign in and no extra app.
Why does Android block the install?: Android installs apps from outside Google Play only after the tester allows installs from their browser once. The install page shows the steps. A Play Protect warning can be passed with Install anyway when the tester trusts the source.
Can I share the APK with a QR code?: Yes. Every upload gets a QR code next to the link. Testers scan it with the phone camera and land on the same install page.
How long does the link last?: 3 days without an account, 7 days with a free account, and as long as you subscribe on Pro and Team.
Can I upload an .aab file?: Yes, with a free account. AppForShare turns it into one APK that testers install from the link.