Skip to content
webtoapkfree

What minimum Android version should my app support?

For most new apps, a minimum Android version of 8.0 (API 26) reaches about 99% of devices. Go to API 24 only if a real share of your users needs it.

GuidesNookesh Karri

Light cover card with the title 'What minimum Android version should my app support?' in dark text and a green accent bar

For most new apps in 2026, a minimum Android version of 8.0 (API level 26) is the sensible default. It reaches about 99% of active devices and drops a long tail of old phones that are hard to test on. Go lower, to Android 7.0 (API 24), only when your own audience data shows people on those phones.

What the minimum Android version actually controls

The minimum Android version is the minSdkVersion value in your app’s manifest. Android’s uses-sdk reference defines it as the lowest API level the app needs to run, and the system won’t let anyone install the app on a phone below that level.

Leave it out and Android assumes a default of 1, telling every device your app runs on all versions. Add a library or two and that’s almost never true.

The minimum is a different setting from the target API level. Google Play’s target API rule says new apps and updates must target Android 16 (API 36) since August 31, 2026. That rule says nothing about the oldest phone you support. I covered it in what target API level Google Play requires.

How many devices each minimum reaches

Each step up in minSdk costs you a slice of devices, and the slices get bigger the higher you go. The table below uses cumulative reach from a distribution chart last updated on 1 October 2026, which says its data comes from Google’s servers.

minSdk Oldest Android version Share of devices that can install
API 23 Android 6.0 99.7%
API 24 Android 7.0 99.4%
API 26 Android 8.0 99.0%
API 28 Android 9 97.0%
API 29 Android 10 93.9%

Going from API 23 to API 26 costs well under one percent of devices. Going from 26 to 29 costs about five percent, which is why 26 is the comfortable middle.

Why the floor keeps rising

The oldest Android versions lose Google’s own support first, so your floor drifts up whether you plan it or not. In July 2024 Google ended Play services updates for Lollipop (API 21 and 22), saying those versions were under 1% of active devices.

Today the Play services setup guide says Play services updates itself automatically on Android 7.0 (API 24) and higher. If you rely on Google sign-in, maps or Firebase, that is a practical floor already.

Third-party SDKs push the floor too. One analytics vendor’s deprecation notice raised its minimum from API 21 to 23 for releases after April 26, 2025. In a r/androiddev thread, developers said an ad SDK moved one of them from 21 to 23, and a payment provider required 29.

A decision table for choosing your minSdk

Pick the lowest level that every library you use accepts, then raise it only for a feature or a testing reason.

Your situation Suggested minimum
New app, broad audience, no special needs API 26 (Android 8.0)
Audience in markets with many older budget phones, and data to prove it API 24 (Android 7.0)
Uses Google Play services features heavily API 24 or higher
An ad, payment or analytics SDK demands more Whatever that SDK’s floor is
Internal tool for a company with managed, recent phones API 29 (Android 10) or higher

My take: start at API 26 and move it only with evidence. Testing on Android 7 hardware is hard to do well, and almost nobody will miss it.

How to check what your own users run

Your own users matter more than global averages. A shop app aimed at a region full of budget phones can look nothing like the worldwide numbers.

  1. In Play Console, open the device catalog for your app.
  2. Pick a device model and read its summary, which the device catalog help page says shows its distribution by RAM and Android version for your app.
  3. Compare that with the table above before you raise minSdk.
  4. If you only need to block a handful of problem phones, set an exclusion rule instead of raising the minimum for everyone.

Excluded devices can’t see or install your app on Google Play, so treat exclusions as a scalpel, not a broom.

What changes for WebView apps

In a WebView app, your pages render in the phone’s built-in web engine, not in your own code. A site that uses modern CSS or JavaScript can look broken on an old phone even when the app installs fine.

The Chrome system requirements list Android 10 or later for Chrome on Android. That covers the browser app, not the WebView component, but it shows which versions Google still targets with new web features.

Apps built with webtoapkfree.com use a fixed floor: generated apps require Android 8.0 or newer (minimum SDK 26). You can’t lower that in the current release. If your audience needs Android 7, a free browser-based builder with a fixed template won’t reach them, and you’ll have to build the wrapper yourself in Android Studio.

Whichever way you build, install the release APK on the oldest phone you can borrow. My guide to testing an APK on your phone lists the checks, and if Android refuses the file, the “App not installed” error guide covers the minSdk case among others.

What happens when you raise the minimum later

Raising minSdk in an update doesn’t uninstall anything. People who already have the app keep the version they installed. They just can’t install the new update, and new users on those phones can’t find it on Google Play.

Plan the raise with your version code and release notes in mind. If old phones are a meaningful share of your installs, warn those users in the app first.

FAQ

Does Google Play require a minimum Android version?

No. Google Play sets a rule for the target API level, not for minSdk. Since August 31, 2026, new apps and updates must target Android 16 (API level 36), but you choose the oldest version that can install the app.

What happens to people whose phone is older than my minSdk?

Android won’t let them install the app. On Google Play, devices that don’t meet the requirement are marked unsupported and can’t install it, while people who already have an older version keep that copy.

Is API 26 too high for a new app?

Not for most apps. Data last updated on 1 October 2026 puts the reach of API 26 at 99.0% of devices, compared with 99.4% for API 24.

What happens if I don’t set minSdkVersion at all?

Android assumes a default of 1, which means the app claims to work on every version. Always set it, because your libraries almost certainly need a higher level.

Sources