Google Play Submission Checklist 2026 — Complete Pre-Launch Guide

Google Play's submission process is less documented than Apple's, but it has its own specific requirements that trip up developers who approach it as the "easier" store. The Data Safety section alone is a common source of policy violations that can get your app removed even after approval. This checklist covers every pre-submission step, including the Data Safety mapping that most guides skip.

Use this checklist alongside the free WhixFrame launch checklist tool before clicking "Publish."

Play Console Setup Checklist

• ✓ Google Play Developer account active — $25 one-time registration fee. Verify account status at play.google.com/console.
• ✓ Developer account identity verified — Google requires identity verification for all developer accounts as of 2023. This takes 1-7 days. Do not submit if verification is pending — your app may be held.
• ✓ App created in Play Console as Android App (not game, unless it is a game — affects category handling).
• ✓ Payment profile set up if your app has paid features or in-app purchases — required before you can activate billing in your app.
• ✓ Signing key managed correctly — using Google Play App Signing (recommended) or self-managed signing. For new apps, enrolling in Google Play App Signing at first upload is strongly recommended to protect your signing key.
• ✓ Target SDK version current — Google requires targeting the latest or near-latest Android SDK. In 2026, targeting API 35 (Android 15) is required for new apps and required for updates. Targeting an old API level blocks submission.

Visual Assets Checklist

• ✓ App icon uploaded: exactly 512×512px, 32-bit PNG. This is the Play Store listing icon — not the adaptive launcher icon in your APK. Upload in Store presence → Main store listing → App icon.
• ✓ Feature Graphic uploaded: 1024×500px JPG or PNG, no alpha. This appears at the top of your Play Store listing page, in certain promotional placements, and as the thumbnail when your app is featured. It is not optional for good presentation — a missing Feature Graphic leaves a blank header.
• ✓ Minimum 2 screenshots uploaded — Google Play requires at least 2 screenshots. Maximum 8 for phone, 8 for 7-inch tablet, 8 for 10-inch tablet.
• ✓ Screenshots meet dimension requirements: minimum 320px on shortest side, maximum 3840px on longest side, 16:9 or 9:16 aspect ratio, PNG or JPG, maximum 8MB per image.
• ✓ Screenshots show accurate app content — same rule as iOS: screenshots must show the actual app functionality in the current submitted version.
• ✓ No Apple or iOS references in screenshots — no iPhone UI elements, no iOS status bar, no App Store branding visible in screenshots.
• ✓ Promo video URL entered (optional) — YouTube URL only. Must be publicly viewable. Google will not accept private or unlisted YouTube videos.

Store Listing Metadata Checklist

• ✓ App title ≤ 30 characters — same limit as iOS. Google does not allow keyword stuffing in the title. Titles that are just a list of keywords ("Budget Tracker Finance Money Manager") are rejected. Check with the character counter.
• ✓ Short description ≤ 80 characters — shown in search results and at the top of the listing page. This is your most important copy. Front-load the core value proposition. Google indexes it heavily for keyword ranking.
• ✓ Full description ≤ 4000 characters — Google's Play algorithms index this for search ranking, unlike Apple which does not index the description. Use your primary keywords naturally in the first 167 characters (shown before "read more").
• ✓ Category set correctly — choose the primary category that best represents the app. Mismatched categories attract policy review.
• ✓ Content rating questionnaire completed — go to Policy → App content → Content rating → Complete questionnaire. This is mandatory. Without a content rating, your app cannot be published. The questionnaire asks about violence, sexual content, substances, gambling, etc. Answer accurately — misrating an app is a policy violation.
• ✓ Target audience and content section completed if your app could potentially attract children — you must declare whether your app is intended for children, adults, or a mixed audience. Mixed audience apps with content targeting children are subject to Families Policy requirements.
• ✓ Tags selected (optional but recommended) — Google Play allows up to 5 tags that help with discoverability in browse contexts.

Data Safety Section Checklist

This is the most commonly incomplete section for new developers. Every SDK you integrate must be reflected here.

• ✓ Data Safety form completed in Play Console → Policy → App content → Data safety.
• ✓ All data types collected declared — including data collected by third-party SDKs. Go through your integrated SDKs: Firebase Analytics (app interactions, device IDs), Crashlytics (crash logs, device IDs), FCM (device IDs), Firebase Auth (email address if used), AdMob (advertising ID, device info).
• ✓ Data sharing declared correctly — for each data type, declare whether it is shared with third parties. Firebase data is shared with Google LLC. AdMob data is shared with Google LLC and potentially other advertising partners.
• ✓ Data purposes declared — for each data type, select all applicable purposes: Analytics, App functionality, Advertising, Fraud prevention, Account management, Personalization, Developer communications.
• ✓ Security practices answered — declare whether data is encrypted in transit (it is, if you use HTTPS/Firebase), whether users can request deletion, and whether you follow a recognized security standard.
• ✓ Data Safety section consistent with privacy policy — this is critical. Google cross-checks these. If your privacy policy says you collect email addresses but your Data Safety section does not declare Contact Info → Email Address, that is a policy violation. They must match exactly.

Content Policy Compliance Checklist

• ✓ No hate speech, harassment, or bullying content — including user-generated content that your app does not moderate. If users can post content, you need moderation policies and tools. (Google Play Hate Speech Policy)
• ✓ No malware or deceptive behavior — your app does what it says. No background data collection not disclosed, no premium SMS charges, no unauthorized system modifications. (Malware Policy)
• ✓ Financial services policy — if your app offers loans, insurance, investment advice, or cryptocurrency: specific policy requirements apply including licensing requirements in some jurisdictions. High-risk rejection area.
• ✓ Gambling policy — real-money gambling apps require pre-approval from Google. Simulated gambling is subject to content ratings. Do not include real-money features without explicit Google approval.
• ✓ VPN policy if applicable — VPN apps have specific requirements including only using VPN APIs for legitimate VPN functionality and not monetizing user data from VPN traffic.
• ✓ Account deletion accessible outside the app — since 2023, Google requires that users can request account deletion via a webpage even if they have lost access to the app. Your privacy policy must link to this web-based deletion request method.

Technical Checklist

• ✓ App Bundle (.aab) submitted not APK — Google Play requires Android App Bundle format for new apps. APK submission is no longer accepted for new app listings as of August 2021.
• ✓ 64-bit support — 64-bit native libraries required since August 2019. If your app uses native code, ensure 64-bit ABI is included.
• ✓ Target SDK ≥ current requirement (API 35 in 2026) — check play.google.com/console/about/targetsdkrequirements for the current minimum.
• ✓ App tested on multiple Android API levels — particularly the minimum SDK version you declare. An app that crashes on Android 10 when you claim compatibility to API 29 is a policy issue.
• ✓ Pre-launch report reviewed — after uploading, go to Android vitals → Pre-launch report in Play Console. Google runs automated testing on your APK and flags crashes, security issues, and performance problems. Fix critical issues before publishing.
• ✓ No requested permissions not used — requesting permissions your app does not actually use is a policy violation. Permission requests must be directly tied to core app functionality explained to the user.

Privacy Policy Checklist

• ✓ Privacy policy URL entered in Play Console → Policy → App content → Privacy Policy.
• ✓ Privacy policy URL loads without login — test in an incognito window. Google's systems check that the URL is accessible.
• ✓ Privacy policy content matches Data Safety declarations — every data type in the Data Safety section must also appear in your privacy policy. Generate or update your policy at whixframe.com/tools/privacy-policy-generator.
• ✓ Account deletion instructions included in privacy policy — both the in-app method and a web-based method that works without app access.
• ✓ Contact information for privacy requests included — a working email address or web form.

Pre-Launch Report

Before clicking Publish, use Google's built-in automated testing:

1. Upload your App Bundle to an internal testing or closed testing track first (not production).
2. In Play Console, go to Android vitals → Pre-launch report. Wait 10-30 minutes for the report to generate.
3. Review the Stability section — fix any crashes that Google's automated test found before promoting to production.
4. Review the Security section — Google scans for known security vulnerabilities. Fix critical security issues before publishing.
5. Review the Accessibility section — optional but valuable. High accessibility scores positively impact visibility in Play Store recommendations.
6. Once the pre-launch report is clean or acceptable, promote from the testing track to production.

Frequently Asked Questions