Home / Guides / Target SDK
GOOGLE PLAY RELEASE GUIDE · REVIEWED OCT 2026

2026 target API checks before submitting an Android update

Check 2026 target API requirements without confusing new submissions with existing-app availability.

A target API check needs two pieces of context: what kind of Android application you are submitting, and whether you are submitting a new app or update versus evaluating an already published app. Different device categories have different thresholds.

What matters

  • From August 31, 2026, new apps and updates for standard Android phones/tablets must target Android 16 (API 36) or higher, subject to applicable exceptions.
  • For new apps and updates, Wear OS and Android Automotive OS require at least API 35; Android TV and Android XR require at least API 34.
  • Google documents a separate availability requirement for existing apps. Do not treat that as the same rule as a new submission.

Step-by-step investigation

1. Identify device categoryDetermine whether the candidate is a phone/tablet app, Wear OS app, Android Automotive OS app, Android TV app or Android XR app.
2. Read candidate targetSdkUse the actual build metadata. Do not confuse compileSdk, minSdk and targetSdk.
3. Choose the correct ruleFor a submission, compare the targetSdk to the category-specific new-app/update threshold. Check current Google policy for deadline changes or extensions.
4. Review platform behaviorEven after meeting the numeric threshold, test runtime permission behavior, foreground services, notifications and platform-specific changes relevant to the app.
5. Verify in Play ConsoleConfirm the exact release and device category and act on any Play Console warning or exception guidance.

A worked example (synthetic)

Example: phone update targeting API 35

For an ordinary phone app submitted after August 31, 2026, candidate targetSdk 35 is below the generally stated API 36 submission minimum. For an Android TV app, the same targetSdk would meet the listed numeric minimum of API 34. Context matters.

Compare the previous and candidate releases

Keep a record of what you actually know. In the free browser tool, enter a verified previous-release snapshot and candidate-release snapshot. Run the comparison to inspect changed fields and export a report. Unknown information should stay unknown.

Use the release comparison tool

No account or real release required to try a sample. Your entered snapshots are processed in your browser.

Open free comparison tool →

What this guide cannot verify

This page summarizes official guidance checked October 28, 2026. Rules and extensions can change, so review Google’s current target API documentation before publishing.

Official documentation

Editorial note: Content checked against the linked official sources on October 28, 2026. This independent guide is informational, not legal advice or a guarantee of Google Play approval.