How to publish an app on Google Play

You’ve built an Android app. Now Play Console has an account to verify, forms to complete, and a release to review. We’ll take those in order. Account verification, bundle acceptance, production access, and release approval each have their own checks.

You’ll need a working app and someone who can change its build, backend, and store declarations. If your account requires closed testing, start recruiting testers early.

1. Create and verify the publisher account

Choose the right account type for the app’s owner, then register with Google Play. Complete identity, contact, organization, and physical-device checks where required.

Check that the account’s verification tasks are complete. You may still need approval for production access later.

2. Create the app record and complete its forms

Create the app in Play Console. Gather listing assets and rating answers, then complete Data safety, deletion and login requirements, and the declarations your app needs.

Check audience, user-content, and payment rules where they apply. Your listing should match the app, and you should be able to account for every App content task.

3. Upload a signed bundle

Follow the Android signing and first-upload steps. Check API and compatibility requirements and resolve any upload errors.

Make sure Play accepts the right bundle into the right app and track.

4. Test and apply for production access

Choose the testing track that fits your release. If the new personal-account requirement applies, complete closed testing and the production-access application.

Other accounts should still test, but shouldn’t assume that particular minimum applies to them. Before preparing production, check that testers can use the app and Play Console allows you to proceed.

5. Submit the production release

Prepare the release and provide working reviewer sign-in details. Send all required changes from Publishing overview. Saving the release alone may leave them unsent.

Check that the production changes you intended to submit are in review.

6. Publish and try a public installation

Respond to review decisions, complete any final publishing action, and check public availability. Read the launch controls carefully; first releases and updates have different options.

Try the production listing and installation as a public user in the intended region. Confirm that you get the version you meant to publish, record the release, and watch the feedback.

Publishing an update or stuck partway through?

Use the exact dashboard task or status to find the relevant guide. For an existing app, keep the package identity and signing continuity, check registration and policy notices, and test the update before expanding availability.