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 lets you upload an Android .apk file and share the install link it returns in seconds. Testers install straight from their phone's browser. No Play Store, no developer account, no review queue. It's free, takes files up to 500 MB, and needs no tester account.
Android installs change on 30 September 2026
Google is introducing developer verification: an app has to come from a verified developer before it can be newly installed on a certified Android device. It starts in Brazil, Indonesia, Singapore and Thailand on 30 September 2026, and goes worldwide during 2027.
This is Google's rule about who signed the app, not a limit on how you share it, so it applies wherever you send a build from — BetaDrop included. If your testers are in those countries, verify your developer identity in the Android Developer Console before then. Otherwise an install will simply be refused on their phone, which looks exactly like a broken link.
Verification is a one-time $25 fee for a full-distribution account, or free with a Limited Distribution account capped at 20 devices. Installs over ADB are exempt. More on what each platform now requires.
Distributing Android apps through the Play Store is standard for production, but it's often the wrong tool for testing and rapid feedback.
Google Play internal testing tracks can still take time to propagate and sometimes require review. BetaDrop gives you an install link the second your upload finishes.
Don't force your clients or testers to sign in to a Google account just to see a prototype. BetaDrop links work for anyone with the URL.
Automatically upload your debug builds and get a fresh link for every commit. It's the friction-free way to keep stakeholders in the loop.
Generate your APK from Android Studio, Gradle, or your CI/CD pipeline. Debug or release builds both work, whichever you need to test.
Drag and drop your .apk file onto BetaDrop's upload area. Files up to 500 MB are supported, so you do not need a workaround.
Copy the install link or QR code and share it with testers through Slack, email, WhatsApp, or any channel you prefer.
Skip Google's review and internal testing tracks. Upload your APK and share it directly with anyone who needs to test.
Large games, media-heavy apps, embedded ML models all fit. BetaDrop handles APK files up to 500 MB with no compression needed.
Unlike Play Store internal testing, testers don't need a Google account or email invitation. Just share the link.
Any Android device can install apps from BetaDrop links. Testers just enable 'Install unknown apps' in their device settings.
Files are transferred over TLS, stored securely, and accessible only through unique links. You control distribution.
Every upload generates a QR code alongside the install link. Perfect for in-person testing and demo sessions.
Most Android distribution options attach a deadline to your build. Play Console links stop working after 60 days and cap you at 100 testers; Firebase keeps builds for 150 days but needs console and SDK setup first.
| Method | Link Lifetime | Tester Limit | Setup Friction |
|---|---|---|---|
| BetaDrop | 24 hours as a guest, up to 7 days with a free account | Unlimited | None |
| Play Console internal sharing | 60 days | 100 | Developer account |
| Firebase App Distribution | 150 days | Unlimited | Complex |
| Diawi | 1 day free, 3–15 days paid | 2 installs/app free | None |
Still sending builds as Drive links or email attachments? Why an install link beats a file link, including the cases where the file is fine.
Most failed APK installs come down to one of four things. Each has a quick fix.
Almost always a signing conflict: a build signed with a different key is already on the device. Uninstall the existing copy first. Android refuses to replace an app when the signing certificate changes, even if the version code is higher.
The browser doing the download needs permission to install apps. On Android 8 and later this is granted per-app under Settings → Apps → Special access → Install unknown apps. Older versions expose a single “Unknown sources” toggle in Security.
Expected for any APK distributed outside the Play Store. Testers can tap “Install anyway”. The warning reflects that Google has not scanned the build, not that anything is wrong with it.
Usually an incomplete download on a flaky connection, or an app bundle (.aab) renamed to .apk. An AAB is not installable on a device. Generate a universal APK from it first, then upload that.
Uploading through 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, 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 guest 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 the free-account ceiling, and adds a dashboard where you can see every active link, revoke one early, or re-share it.
Every APK moves over TLS and is reachable only through its own unguessable link. Nothing is listed publicly and nothing is indexed by search engines. When a link expires the file stops being downloadable, so an old build cannot keep circulating after you have moved on.
Visit BetaDrop and drag your .apk file onto the upload area. You'll get an instant shareable link and QR code. Paste either into Slack, a ticket, or a release note. Hosting the file costs nothing and your first guest upload needs no account. Testers open the link on their Android device and install the app directly.
Yes. BetaDrop lets you upload an APK and share it via a direct download link. Testers install the APK by enabling 'Install from unknown sources' in their Android settings, and no Play Store listing is needed.
BetaDrop accepts APK files up to 500 MB, accommodating large Android applications with complex assets, native libraries, and bundled resources.
Yes. Files are transferred over TLS-encrypted connections, stored securely, and accessible only through unique, obfuscated links. You control who receives the link.
No. Testers just need to open the BetaDrop link on their Android device and download the APK. No Google account, no Play Store, and no additional apps are needed.
Build a signed APK from Android Studio or your CI pipeline, upload it to BetaDrop, and share the install link it generates. Testers enable "Install unknown apps" for their browser, tap the link, and the APK installs directly. No Play Store listing, no developer account. Our safe Android sideloading guide covers the permission steps.
Get your Android build into testers' hands in under a minute. No Play Store, no review, no waiting.
Upload APK on BetaDrop