# Google Play deadline checker > Google Play deadline checker: paste Android build files to check target API 36, 16 KB page size and Billing Library deadlines. Free, nothing uploaded. Canonical: https://app369.com/tools/google-play-deadline-checker/ Paste your Android build files to see where you stand on Google Play’s three dated rules: target API 36 (since August 31, 2026), 16 KB page sizes (updates blocked from February 1, 2027) and Play Billing Library 8 and 9. The check runs in your browser; nothing is uploaded. [**Check my app**](#check) Free, no sign-up. Dates checked October 22, 2026. ## Your build files Fill in at least one box. The more you paste, the more it can check. **android/app/build.gradle or build.gradle.kts****android/settings.gradle(.kts), or the root build.gradle (for the Android Gradle Plugin version)** **Flutter version (optional)** From `flutter --version`. Needed when the file uses `flutter.targetSdkVersion` or `flutter.ndkVersion`. **pubspec.yaml (optional)** Read only to see whether you use `in_app_purchase`. ## **What it checks**
**August 31, 2026**
**Target API 36**
New apps and updates must target Android 16 (API level 36). Google’s extension to November 1, 2026 has passed. The tool reads targetSdk, and uses your Flutter version when the file says flutter.targetSdkVersion.
[Read the guide](https://app369.com/blog/google-play-target-api-36-android-16-requirement-2026/)
**February 1, 2027**
**16 KB page size**
Google says updates that don’t support 16 KB page sizes can’t be released from this date. The tool checks the Android Gradle Plugin (8.5.1 or higher) and the NDK (r28 or higher).
[Read the guide](https://app369.com/blog/google-play-16kb-page-size-flutter-android-2026/)
**August 31, 2026 and 2027**
**Play Billing Library 8, then 9**
Billing Library 8 has been required since August 31, 2026. Google’s table says version 8 stops being accepted from August 31, 2027 (extension to November 1, 2027), so plan for 9 or later.
[Read the guide](https://app369.com/blog/play-billing-library-9-migration-deadline-2027/)
## **What this tool can’t see** It reads the text you paste. It can’t see version catalogs (`libs.versions.toml`), versions that plugins resolve for you, or whether the native libraries inside your plugins are 16 KB aligned. Play Console and Android Studio’s Analyze APK look at the built app and are the final word. Using Firebase? The free [Firebase shutdown checker](https://app369.com/tools/firebase-shutdown-checker/) finds the Firebase products in your code that have a shutdown date. ## **Questions**
**Are my files sent anywhere?**
No. The check runs in your browser with JavaScript, and what you paste never leaves the page. Only an anonymous count of passes, warnings and failures is recorded for usage statistics.
**What is the Google Play target API requirement?**
Google says that since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher. Google’s extension to November 1, 2026 has passed. Google’s Android 17 post says new apps and updates will need to target API 37 in August 2027, with no day given.
**Which Flutter version targets API 36?**
Flutter 3.35 and later set flutter.targetSdkVersion to 36, per Flutter’s source. Flutter 3.29 and 3.32 set 35. If your build file uses a hard-coded number, change it to 36 yourself.
**What do I need for the 16 KB page size rule?**
Google says apps built with Android Gradle Plugin 8.5.1 or higher and NDK r28 or higher, with 16 KB compatible prebuilt dependencies, are compatible by default. Flutter 3.38 moved its default NDK to r28. Plugins that ship their own .so files need to be aligned too, which this tool can’t check.
**Which Play Billing Library version do I need?**
Version 8 or later today. Google’s deprecation table says version 8 stops being accepted for new apps and updates from August 31, 2027, with an extension to November 1, 2027, so plan for 9 or later. If you use Flutter’s in_app_purchase, the plugin brings its own Billing Library version, so check the resolved version in pubspec.lock.
**If the checker passes everything, will Play accept my update?**
Not necessarily. It reads the text you paste. It can’t see version catalogs, versions your plugins resolve, or the alignment of prebuilt native libraries, and Play Console can flag other policy issues. The built app in Play Console and Android Studio’s Analyze APK are the final check.
Sources, checked October 22, 2026: [Google Play target API level requirement](https://developer.android.com/google/play/requirements/target-sdk), [Play Console Help, target API level requirements](https://support.google.com/googleplay/android-developer/answer/11926878), [Support 16 KB page sizes](https://developer.android.com/guide/practices/page-sizes), [Play Billing Library version deprecation](https://developer.android.com/google/play/billing/deprecation-faq), [Flutter 3.38 release post](https://flutter.dev/blog/whats-new-in-flutter-3-38), [Prepare for the Android 17 orientation changes](https://developer.android.com/blog/posts/prepare-your-app-for-the-resizability-and-orientation-changes-in-android-17). ## **Can’t ship an update because of one of these?** The App Fix Ticket covers it in two fixed-price steps. A $450 Diagnosis gives you the root cause with evidence and a fixed repair quote within 3 business days, credited toward the fix. If you go ahead, the $1,200 Fix takes 5 business days and comes as a pull request. [**See the App Fix Ticket **](https://app369.com/fixed-price/flutter-firebase-bug-fix/) ## **Link to this checker** Writing about Play Console warnings, a Flutter upgrade or a README? You’re welcome to link here. The checker is free, needs no sign-up, and never uploads your files. **HTML link** ## **Fixed-price help for your app** Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed. - [**App Fix Ticket**from $450One reproducible bug in an existing mobile or web app, diagnosed and fixed.](https://app369.com/fixed-price/flutter-firebase-bug-fix/)