How to Upload an App to Google Play: 2026 Guide

Uploading an app to Google Play takes five steps: (1) open a Google Play Console developer account for a one-time $25 fee, (2) prepare your signed AAB, (3) complete the store listing (name, description, graphics), (4) fill in the data safety and content rating forms, and (5) submit for review. Review takes anywhere from a few hours to 7 days, and new personal accounts must pass a mandatory closed test before production. This guide walks through every step as it works in 2026.

1. Open a Google Play Developer Account

The first step is opening a developer account in Google Play Console. Registration costs a one-time $25. Personal accounts require identity verification; organization accounts require your company’s D-U-N-S number and official details, and approval usually takes a few days. For commercial apps we recommend an organization account. For the fee details and the App Store comparison, see our app publishing fees guide.

2. Prepare the Signed App Bundle (AAB)

For new apps Google Play requires the AAB (Android App Bundle) format, not an APK. The bundle is signed with your upload key, while the store signature is managed by Play App Signing — use it, as it protects you against losing your key. Your app’s identity and version live in the build file:

// android/app/build.gradle
android {
  defaultConfig {
    applicationId "com.yourcompany.app" // permanent store identity, cannot change later
    versionCode 1      // must increase with every upload
    versionName "1.0.0" // user-facing version
  }
}

If you build with React Native, `cd android && ./gradlew bundleRelease` produces a release-ready AAB; we covered the full build process in Android development with React Native.

3. Complete the Store Listing

The store listing is the page users see on Google Play, and it directly drives your ranking in store search (ASO):

• App name: up to 30 characters — the strongest signal in store search.
• Short description: 80 characters; full description: 4,000 characters. Use keywords naturally.
• App icon: 512×512 PNG.
• Feature graphic: 1024×500 — shown in listings and promotions.
• At least 2 phone screenshots; add tablet screenshots if you support tablets.

4. Fill In the Mandatory Forms

Google Play will not accept a submission until four declarations are complete: the data safety form (what data you collect and how you process it), the content rating questionnaire, the target audience declaration and the ads declaration. A reachable privacy policy URL is also mandatory. The critical rule here is honesty: if what you declare in the data safety form does not match the app’s actual behavior, the app can be taken down.

5. The Closed-Testing Rule: Critical for New Personal Accounts

Personal developer accounts created after November 2023 must first run a closed test with at least 12 testers for 14 uninterrupted days before they can push an app to the production track. Organization accounts are exempt. Recruiting testers, inviting them and completing the 14 days has a real impact on the schedule.

For a new personal account uploading its first app to the Play Store, the realistic end-to-end timeline is 3-4 weeks: account approval + the mandatory 14-day closed test + review. Plan your launch date accordingly.

6. Submit for Review and Release

Once every form is complete and the AAB is uploaded to the production track, you submit the app for review. Review usually concludes within a few hours to 7 days. When releasing, we recommend a staged rollout: open the app to 10-20% of users first, so a critical bug can be fixed before full distribution. After launch, every update goes through the same review process.

The Most Common Mistakes

• Trying to upload an APK: the Play Store only accepts AAB for new apps.
• Losing the signing key: without Play App Signing, a lost key means you can never update the app again.
• Filling in the data safety form differently from actual behavior: when detected, the app is removed.
• Having no privacy policy page, or a link that does not resolve.
• Leaving the closed-testing requirement out of the plan: the launch date slips by at least two weeks.

Conclusion

Uploading an app to the Play Store is a well-defined process — account setup, AAB preparation, store listing, mandatory declarations and review — and with the right preparation you go live on the first attempt. For the bigger picture including the iOS side, see our App Store and Google Play publishing guide. If you would like us to handle development and the store process end to end, take a look at our mobile app service and request a quote.