APK Compatibility by Android Version (Full 2026 Guide)

APK compatibility by Android version comes down to two numbers in the app’s manifest. minSdkVersion is the floor: your Android release must be at or above it, or the install fails. targetSdkVersion is the version the developer tested against, and it changes behavior instead of blocking installs. Android 10 is API 29, Android 15 is API 35, Android 17 is API 37, and every APK declares the number it needs.

How Android Version Compatibility Works

Android checks the manifest before it copies any files, and the check takes two fields. minSdkVersion names the oldest Android release the app supports. targetSdkVersion names the release it was built and tested against. The device’s API level is compared against the first one, and the second one only affects which platform behaviors are switched on.

Three outcomes follow from that comparison:

1. Device API at or above minSdkVersion. The install proceeds to the signature and architecture checks.
2. Device API below minSdkVersion. The installer aborts. From ADB you see INSTALL_FAILED_OLDER_SDK; from the Play Store you see “This app isn’t compatible with your device.”
3. Device far above targetSdkVersion. The app installs, but Android may apply compatibility behaviors the developer never tested. That is where crashes on modern phones usually come from.

Google documents both fields in the uses-sdk element reference, and the API numbers appear in the table below.

Why an APK Refuses to Install on Your Android Version

The message you see tells you which of the three checks failed. Match your error to its row:

That fifth row is the newest one. Android 14 blocks installs targeting API 22 and lower, Android 15 raises the floor to 23, and each release keeps pushing it up. The ADB flag above is a deliberate escape hatch for sideloaded copies. The install troubleshooting guide walks through each code with screenshots.

Android Version and API Level History

Apps declare API levels rather than marketing names, because the numbers never change. This is the mapping you will see quoted on download pages:

Three details worth knowing about the tail of that table. Android 16 shipped on June 10, 2025 and Android 17 on June 16, 2026, so “the latest Android” answers change every summer. Fire OS tracks the same numbering: Fire OS 16 corresponds to API 36. And the Play Store now keys its rules to these integers rather than to version names.

How Fire OS, Wear OS, TV, and Automotive Number Android

Every Android fork reports the same API integers Google assigns to each release, so Fire OS 16 means API 36, Android TV builds match phone releases number for number, and Wear OS and Android Automotive declare the same minSdkVersion and targetSdkVersion values in their manifests. The label changes. The number does not.

Fire OS is the clearest example, because version 16 maps straight to API 36 and Android 16. Wear OS and Android Automotive run separate Play Store tracks, so an app can exist for phones and be missing from the watch. A mirror app that fails on a Galaxy Watch is usually hitting that split. That is a catalog problem.

Backward and Forward Compatibility Explained

Android runs old apps on new systems far more reliably than the reverse. The two directions fail differently.

New Android, Old APK

Old apps usually install and run. Behavior changes are gated behind targetSdkVersion, so an app built for Android 9 still behaves like an Android 9 app on Android 17. The failures people hit are removed APIs and tightened background limits, which show up as crashes or notifications that never arrive. Emergency exceptions exist for very old targets, covered in the error table above.

Old Android, New APK

The install simply does not happen. minSdkVersion is enforced before anything else, and there is no hidden override. Your real choices are:

1. Update Android. The permanent fix, assuming your device still receives updates.
2. Install an older app release. Archives keep prior versions, and older releases often declare a lower minimum. The APK update guide covers downgrading safely, including why a signature must still match.
3. Run it elsewhere. An emulator image, a second device, or a cloud Android session.

The Play Store’s Own Deadline

Google Play adds a third rule on top of the technical one. New apps and updates must target API 36 from August 31, 2026 (with extensions to November 1, 2026). Apps still below API 35 stop being offered to new users on devices running a newer Android. Existing installs keep working; discovery is what changes. Google publishes the exact dates in its target API level requirements.

Google Play Target API Deadline Timeline

Google Play requires every new app and every update to target a specific API level, and the current floor is API 36 from August 31, 2026, with a short extension window to November 1, 2026 for developers who request more time. Two deadlines matter right now.

Existing installs are never removed. Google publishes both dates in its target API level requirements, and the matching platform reference is the targetSdkVersion documentation. An app that ignores the deadline keeps working for people who already installed it.

Behavior Changes Gated by targetSdkVersion

targetSdkVersion decides which platform behaviors Android applies to an app, so a package built for API 29 installs on Android 16 yet keeps the storage rules, notification rules, and background limits from its own era rather than the newest platform rules. That is why an old app can fail on a brand new phone.

None of those rows block an install. The app arrives, launches, then fails the moment it touches a restricted API. Only the developer can raise targetSdkVersion, so an update is the fix.

How to Check an APK’s Minimum Android Version

Four methods, ordered by how much effort they cost.

Read the Store or Download Page

Google Play lists Requires Android on every app page. Archives and mirrors print the same value on their download pages. This answers the question in five seconds for anything you have not downloaded yet.

Use Android Studio’s APK Analyzer

Open Android Studio, choose File then Profile or Debug APK, and read minSdkVersion from the manifest summary. This works on any local file, including one you received over a messaging app.

Read the Manifest With ADB

Install the app on a device, then run:

adb shell dumpsys package com.example.app | grep -E "minSdk|targetSdk|versionName"

It prints the values Android is actually enforcing for that installed copy.

Check the Architecture at the Same Time

The same inspection should tell you which native libraries ship inside the package, which matters on Chromebooks and PCs. Architecture, ABI names, and split packages are covered in APK file size and architecture.

Split APKs, XAPK Files, and adb install-multiple

Google Play turns an Android App Bundle into several small APKs instead of one file, and a plain adb install command accepts only one file at a time, so a bundle needs the install-multiple command to arrive complete on the device. One file is never the whole app.

install-multiple takes every path in a single call and treats them as one package, so the files must match each other. Send only an x86 split to an arm64 phone and ADB returns INSTALL_FAILED_NO_MATCHING_ABIS. Command examples are in APK file size and architecture.

How to Check Your Android Version

Open Settings, scroll to About phone or About tablet, and read Android version. Tap the version number if you want the Easter egg, but the number itself is what you need. Map it using the table above.

On a TV the path differs slightly: Settings, then Device Preferences or System, then About. On Wear OS, Settings, then System, then About. The same number applies everywhere, because it comes from the same Android base.

If the settings screen shows a build number only, you are looking one line too far down. Compatibility reads the Android version, not the security patch date.

What to Do If an APK Needs a Newer Android

Three options in order of how often they work:

1. Update the device. Settings, System, System update. Devices released within the last three years usually receive two to three years of updates, so a 2022 phone may already be at its ceiling.
2. Roll back to an older app version. The prior release frequently declared a lower minimum. Install it from an archive, but keep the signature consistent with the copy already on the device or uninstall first.
3. Use an emulator. On a computer, an emulator image runs any current API level, which makes it the answer when the phone is stuck. See the PC guide for setup.

Do not attempt to modify minSdkVersion by rebuilding the manifest. A repacked APK fails the signature check and gets rejected by INSTALL_FAILED_UPDATE_INCOMPATIBLE.

How to Downgrade to an Earlier App Version

To roll back an app you remove the newer copy first, then install an older release signed with the same key, because Android refuses to place a lower version code over a higher one and Android returns the INSTALL_FAILED_VERSION_DOWNGRADE error when you try. Uninstalling first clears both the version check and the saved data.

1. Uninstall the app. Settings, then Apps, then the app, then Uninstall. For a system app, choose Uninstall updates, which restores the factory version.
2. Confirm the signing key. An older release signed with a different key fails with INSTALL_FAILED_UPDATE_INCOMPATIBLE, which is what happens after a developer turns on Play App Signing.
3. Install the older package. Run adb install old-app.apk, or open the file from a file manager on the phone.
4. Expect data loss. Uninstalling removes logins and saves, so export what you can before step one.

Debuggable builds also accept the adb install -d flag, which relaxes the version check for packages that allow it. Release builds rarely do, so uninstalling stays the reliable route. Prior versions live in archives, and how to update APK files lists the safe order.

What to Do If an APK Needs an Older Android

Almost never a problem. Apps declaring a floor below your version run fine, because Android runs new apps on old behavior through targetSdk gating. The rare failures are hardware features the app declares as required, such as a specific camera or sensor, which is a device mismatch rather than a version mismatch. The permissions checklist in how to check APK permissions covers that inspection.

Test your device against the full device support list, then run the version check above on the app you actually want.