Google Play's target API level 36 requirement for 2026

Updated

Every year Google Play raises the minimum API level an app must target, and every August some developers find out when an upload is refused. The 2026 step happened on 31 August 2026.

What does Google require now?

In Google's words: "New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play." The exceptions are by platform:

  • Wear OS and Android Automotive OS apps: API level 35 or higher.
  • Android TV and Android XR apps: API level 34 or higher.
  • Permanently private apps restricted to one organisation for internal distribution are exempt.

Apps already on Google Play have a separate, lower bar: they must target Android 15 (API level 35) or higher to stay available to new users on devices running a newer Android version. An app below that can still be used by the people who have it, but new users on newer phones cannot install it.

How do I check what my build actually targets?

Check the built file, not your config. The most common version of this problem is a project that says 36 and an upload built before the change, or a framework default that was never overridden.

For an APK, either of these prints the target SDK from the compiled manifest:

aapt2 dump badging app-release.apk
apkanalyzer manifest target-sdk app-release.apk

In the aapt2 output, look for targetSdkVersion:'36'. Both tools come with the Android SDK build tools and command-line tools.

How do I change it?

Set targetSdk to 36, and compileSdk to 36 or higher: you cannot target an API level you do not compile against.

Native Android (Gradle)

In app/build.gradle.kts:

android {
    compileSdk = 36

    defaultConfig {
        targetSdk = 36
    }
}

In a Groovy build.gradle, the same settings are compileSdk 36 and targetSdk 36.

Flutter

Open android/app/build.gradle.kts. By default it reads:

compileSdk = flutter.compileSdkVersion
// ...
targetSdk = flutter.targetSdkVersion

Those values come from your Flutter version. Flutter's documentation says you can replace them with specific numbers when you need to, so either upgrade Flutter to a version whose default is 36, or set targetSdk = 36 and compileSdk = 36 yourself.

React Native

In a React Native project the versions usually live in android/build.gradle:

buildscript {
    ext {
        compileSdkVersion = 36
        targetSdkVersion = 36
    }
}

Upgrading React Native is the cleaner route when your version is old, because the native dependencies expect the SDK levels the template was built for.

Expo

Each Expo SDK version sets its own Android SDK levels, so upgrading Expo is the usual fix. To set them explicitly, use the expo-build-properties plugin in your app config:

{
  "expo": {
    "plugins": [
      ["expo-build-properties", { "android": { "compileSdkVersion": 36, "targetSdkVersion": 36 } }]
    ]
  }
}

Then build again. Changing the config does nothing to a build you already made.

What changes when my app targets 36?

Targeting a new level turns on that level's behaviour changes for your app. For API 36 (Android 16), Google's list includes:

  • Edge-to-edge is no longer optional. The attribute apps used to opt out, windowOptOutEdgeToEdgeEnforcement, is deprecated and disabled, so your layouts must handle drawing behind the status and navigation bars.
  • Predictive back is on by default on Android 16 devices: onBackPressed is no longer called and KEYCODE_BACK is no longer dispatched, unless you opt out with android:enableOnBackInvokedCallback="false".
  • Orientation and resizability restrictions are ignored on large screens (smallest width of 600dp or more): screenOrientation, resizableActivity and aspect-ratio limits no longer apply there.
  • Body sensor permissions become granular health permissions, such as READ_HEART_RATE instead of BODY_SENSORS.

Test on an Android 16 device or emulator before you upload. Your closed testers are the right people to catch what changed.

Check it before Google does

The target API level is one line in the manifest, and so are the permissions that need a Play Console declaration. The pre-launch checklist covers the rest of what Google looks at before an app goes live.

Sources

Next steps

Still need testers? Get 12 testers for your closed test through a free test-for-test exchange - you test another developer's app, they test yours, and every opt-in is verified.

Common questions

What target API level does Google Play require in 2026?
From 31 August 2026, new apps and app updates must target Android 16 (API level 36) or higher, except Wear OS and Android Automotive OS apps (API 35) and Android TV and Android XR apps (API 34).
Can I get more time to update my target API level?
Yes. Google says you can request an extension to 1 November 2026, through a form in Play Console.
What happens to my existing app if I do not update it?
An existing app must target at least API level 35 to stay available to new users on devices running a newer Android version. Below that, new users on newer devices cannot find or install it.
Does compileSdk have to change too?
Yes. compileSdk must be at least as high as targetSdk, so set both to 36 or higher.

Apps currently in closed testing

Real developers running the test described above. Test one, and get testers for your own app back.

Closed testing

In Between is a free card game. Join the group, opt in, install, open it and play a hand. Keep it 14 days. Not available in South Korea. I test your app back the same day.

Games

Available in all countries

Open to testers · 14-day test

Closed testing

# BAYAA — Closed Testing: Instructions for Testers Thank you for participating in the BAYAA (بياع) closed testing program. BAYAA is a Mauritanian marketplace designed to connect customers with shops, restaurants, pharmacies, hotels, and service providers. ## 1. What testers are expected to do - Install BAYAA through the official Google Play closed-testing link. - Keep the app installed throughout the 14-day testing period. - Open and use the app regularly during the testing period. - Create an account and test registration and login. - Browse available shops, products, and services. - Test search and navigation. - Test merchant features if you have a merchant account. - Check WhatsApp contact options where available. - Report bugs, errors, confusing screens, and suggestions. ## 2. What feedback should you provide? Please tell us: - What worked correctly? - What did not work? - Were any pages slow or difficult to use? - Did you experience crashes or unexpected errors? - What features would you like us to improve? Honest feedback is very important. You do not need to give positive feedback if you encounter a problem. ## 3. Important testing rules - Use the app with your own tester account. - Do not share your login credentials. - Do not enter real payment or sensitive personal information. - Do not make fake purchases or transactions. - Do not uninstall the app during the testing period unless instructed. - Keep your Google Play testing enrollment active. ## 4. Reporting problems Send your feedback and screenshots of errors to the BAYAA development team. Thank you for helping us improve BAYAA and prepare it for its official launch in Mauritania. **BAYAA — بياع | Supporting Mauritanian Businesses**

Shopping

Available in all countries

Open to testers · 14-day test

Closed testing

PocketLedger helps you know your money and own your month — without handing your financial life to anyone. Everything stays on your phone. There is no account to create, no bank login, no SMS reading and no internet access at all. PocketLedger works fully offline. TRACK EVERY RUPEE (OR DOLLAR, EURO, POUND) • Add income and expenses in seconds, with category, account, date, merchant and notes • Mark refunds so they reduce your spending instead of counting as income • Search by merchant or note, filter by type, and tap any category to see its transactions for the month • INR, USD, EUR and GBP supported — amounts in different currencies are never mixed or converted SEE YOUR MONTH AT A GLANCE • Net cash flow, total income and total expenses for any month • Spending by category with an interactive chart • Recent transactions and account balances on one screen BUDGETS THAT KEEP YOU HONEST • Set a monthly limit for any category • See what you have spent, what is left, and when you go over ALL YOUR ACCOUNTS • Cash, bank accounts, UPI, credit cards and wallets • Pick from popular banks (SBI, HDFC, ICICI, Axis, Kotak and many more) and UPI apps, or type any name • Live balance for every account NOTHING IS EVER LOST • Every transaction keeps a full version history: see exactly what changed, when • Deleted transactions can be restored • An activity log records every add, edit, delete and setting change PRIVATE BY DESIGN • No sign-up, no ads, no tracking, no analytics • No internet permission — your data physically cannot leave the app • Not backed up to the cloud PocketLedger is a personal budgeting and expense-tracking tool. It does not offer loans, payments, banking or investment services and does not connect to any bank. Made by Technopreneurs Technolabs.

Finance

Available in all countries

Open to testers · 14-day test

Related guides

May we use analytics and ad measurement? Analytics (Vercel, and Ahrefs on our public pages) count page views without cookies. Ad measurement lets Google's tag on our public pages see which visits came from our Google ads, using a Google cookie. The site works the same either way. Cookie Policy · How Google uses data ·