1. Home
  2. Guides
  3. Share an APK without Play Store

Guide

How to share an APK without the Play Store

Not every app belongs on Google Play. Internal tools, client previews, school projects and event apps are often easier to hand out directly.

Updated 2026-10-183 min readBy the APK Maker team
Short answerUpload the APK somewhere that serves a direct download link (your website, cloud storage or a file host), share the link or a QR code to it, and include short install instructions. For updates, keep the same package name and signing key and raise the version code.

Where to host the APK

  • Your own website — most trustworthy for users; serve the file with the MIME type application/vnd.android.package-archive.
  • Cloud storage (Google Drive, Dropbox, OneDrive) — set sharing to "anyone with the link"; users may see an extra preview page.
  • Release pages such as GitHub Releases for open-source apps.
  • Messaging apps — fine for a few people, but files may be compressed or blocked.

Make a simple download page

A page with your icon, a big download button, the version, file size and three install steps converts far better than a bare file link. Generate one in seconds with the APK download page generator — it includes a QR code for desktop visitors.

Use QR codes for in-person sharing

At events, in classrooms or on printed menus, a QR code to the download page is the fastest path. Point the QR at the page, not the raw file, so people see what they are installing.

Help people install it

Most people have never installed an app outside Play. Send clear, brand-specific steps — the install instructions generator writes them for you. Mention the expected Play Protect prompt so nobody panics. Tell users how big the download is; check with the APK download time calculator.

Ship updates

  • Same package name and signing key, higher version code — then the update installs over the old app and keeps its data.
  • Replace the file at the same URL so old links and QR codes keep working.
  • Show the version number on your page so users know whether to update.

Let people verify the file

Publish the APK's SHA-256 checksum next to the download button so technical users can confirm the file wasn't altered:

# macOS / Linux
shasum -a 256 my-app.apk
# Windows (PowerShell)
Get-FileHash my-app.apk -Algorithm SHA256

versionName vs versionCode

versionNameversionCode
Example1.4.212
Shown to usersYesNo
Decides if an update installsNoYes — must be higher than the installed one

Increase both with every release. Show the version name on your download page.

Things to avoid

  • URL shorteners — they hide the destination and are often flagged.
  • Plain HTTP links — browsers increasingly block or warn on insecure downloads.
  • Renaming the file to hide the .apk extension — Android needs it to recognise the package.
  • Changing the signing key between versions — updates will fail to install.

Make your APK now — free

No Android Studio, no code, no watermark. Pick what you are starting from:

Frequently asked questions

Is it legal to distribute an APK outside Google Play?

Yes, for your own app. Android supports installing apps from other sources; users just need to allow it.

Why does Chrome warn that the file may be harmful?

Chrome warns for all APK downloads from outside Play. Users can tap Download anyway; hosting on your own HTTPS domain builds trust.

Will users get updates automatically?

No. Apps installed outside Play don't auto-update; tell users when a new version is available.