Practical guide · Updated July 25, 2026
How to publish an app to Google Play
The practical path from an Android App Bundle to testing tracks, a compliant store listing and a monitored production release.
Before you start
You need a verified Play Console account, a stable package name, a signed Android App Bundle, support contact, privacy policy and accurate Data safety answers. New personal developer accounts may also need to meet Google Play testing requirements before production access.
Configure the app and Play App Signing
Create the app record, choose the default language, lock the package name and enroll in Play App Signing. Upload an AAB rather than treating a local APK as the production artifact.
Build the default store listing
Write the app name, short description and full description, then upload the icon, feature graphic and screenshots. Google Play currently requires a 512 × 512 app icon and provides format and size validation inside the listing form.

Complete policy declarations
Finish Data safety, app access, ads, content rating, target audience, permissions and any relevant health or financial declarations. The answers must match the shipped build and backend behavior.
Use internal and closed testing
Install the release through Google Play, not only through local tooling. Test upgrades, purchases, deep links, notifications, permission denial and slow networks. Keep tester evidence if the account must request production access.
Release and monitor
Create the production release, choose managed publishing or a staged rollout, then monitor Android vitals, crashes, ANRs, reviews and purchase failures. Google notes that review can take up to seven days or longer in exceptional cases.
Google Play app icon and review FAQ
What is the Google Play app icon size? The Play Console listing requires a 512 × 512 graphic and validates accepted format and file size.
Is an AAB required? Google Play uses Android App Bundles for new app distribution and generates optimized APKs for devices.
Why can’t I publish to production? Check identity verification, policy tasks and testing requirements attached to the developer account.
Can I control the exact go-live moment? Managed publishing can hold approved changes until you release them.