Target SDK Checker

About Target SDK Checker

Check your app's targetSdkVersion against Google Play's per-form-factor target-API requirements (reviewed 22 September 2026), and what raising the target SDK means for your next update.

Target SDK Checker is part of APKLint’s manifest & configuration toolkit — Audit your AndroidManifest and security config. It’s free to use and needs no account.

Your privacy is the default: what you submit is processed on our servers over an encrypted connection for that request only — it isn’t written to file or object storage, and never shared.

What Target SDK Checker checks

• Reads targetSdkVersion from the manifest
• Compares it to Google Play's per-form-factor target-API requirements (reviewed 22 September 2026)
• Notes the Wear/TV/Automotive/XR exceptions
• Shows whether the manifest meets the standard target-API threshold

Good to know: For standard mobile/tablet apps, new apps and updates must target API 36 (Android 16) and existing apps must stay on at least API 35 (Android 15) to remain available to new users on newer devices. Wear OS, TV, Automotive, and XR use the separate thresholds in the table above. Requirements change over time, so verify the latest in Play Console. This checks the manifest value only.

When to use Target SDK Checker

Best for

Checking a pasted manifest's targetSdkVersion against Google Play's per-form-factor target-API requirements (reviewed 22 September 2026) and what raising it means.

Not the right tool for

Not a device-reach estimate (use the Min SDK tool) and not a live Play Console status.

What you get back

Whether your target meets the date-stamped rule, with the Wear/TV/Automotive/XR exceptions noted.

How it differs from related APKLint tools

It is about the target-API submission rule; the Min SDK tool is about how low you can go for device coverage.

Limitations

Play requirements change, verify the current rule in Play Console before release.

How to use Target SDK Checker

1. Paste your file — Paste your AndroidManifest.xml.
2. Send for analysis — APKLint checks it on our servers over an encrypted connection.
3. Review the findings — Work through each result with a short explanation of why it matters.
4. Nothing is stored — Your pasted text is processed for this request only — it isn't written to file or object storage, logged for analytics, or shared.

Target-API thresholds by form factor

Google Play sets different target-API thresholds for different device types. This checker reads your manifest's <uses-feature> declarations to make a best-effort inference of the form factor (Wear OS, Android TV, Automotive, or XR — otherwise standard mobile/tablet) and applies the matching thresholds. The Play Console release track remains authoritative, especially for Android Automotive OS and shared multi-form-factor artifacts. As of August 2026:

New submissions and updates must meet the “new app / update” level; the “existing-app floor” is the minimum for an already-published app to stay available to new users on newer devices. Paste a full AndroidManifest.xml (including any <uses-feature>) so the checker can infer the form factor — a bare targetSdkVersion is treated as standard mobile/tablet. This is a best-effort inference, not a guarantee; the Play Console release track is authoritative. Verify the current rule in the Play Console before release.

Temporary 2026 extension: if Google Play approves a target-API extension for your app, the applicable enforcement deadline may be deferred through November 1, 2026. This checker reports the standard thresholds above and does not verify account-specific extensions. Review the approved scope and deadline in your Play Console before submitting an update or relying on continued distribution. See Google Play's target API requirements.

Why use APKLint

Frequently asked questions

Related tools