Before you start

Pricing & Distribution changes: If you make any changes to your app's Pricing & Distribution page, it affects your app's current and future production, alpha, and beta versions.

APKs

We recommend publishing an alpha/beta app before you release a production APK.

After publishing an alpha/beta APK for the first time, it may take a few hours for your test link to be available to testers. If you publish additional changes, they may take several hours to be available for testers.

Tips

Closed beta: Consider closed beta testing if you want to run a test with a smaller group (like within your company or team) or when you know the exact users you want to test your app. If you're testing an existing app that you've published before, only users in your test group will receive an update for your alpha/beta version.

Open beta: Consider open beta testing if you want to run a test with a large group and surface your app's beta version on the Play Store. If you run an open beta test, anyone can join your beta program and submit private feedback to you. Make sure your app is ready for visibility on the Play Store before choosing this option.

Keep in mind, the open and closed beta version of your app won't have public ratings.

Type a name to identify your list of testers. You can use the same list for future tests on any of your apps.

Add email addresses separated by commas or click Upload new CSV file. If you use a .CSV file, put each email address on its own line without any commas. If you upload a .CSV file, it will overwrite any email addresses you've added.

Click Save.

Check the box next to the list of testers you want to use.

Copy the "Beta opt-in URL" to share with your testers.

Next to "Feedback channel," add an email address or URL to collect feedback from testers. Your app's feedback channel will be shown to users on your tester opt-in page.

Click Save.

Share your opt-in URL with users

After you create a test, you'll get a URL link to your alpha/beta app to share with your testers.

The link uses the following format: https://play.google.com/apps/testing/com.package.name

The opt-in link only shows when an app is "Published." Apps in "Draft" or "Pending publication" won't show the opt-in link.

After clicking the opt-in link, your testers will get an explanation of what it means to be a tester and a link to opt-in. Each tester needs to opt-in using the link to be part of the beta test.

If you set up an open beta test, users can find your beta app on the Play Store. Make sure your app is ready for visibility on the Play Store before choosing this option.

For early access apps (new apps that haven't been published to production): Users can find your beta version via search on the Play Store. Once users find your listing, they can install your app normally.

For apps with a live production version: Users can opt-in to your beta program from your store listing.

You can also share a URL link on a website or email and every user with the link can download the beta version of your app.

Share your opt-in URL with users

Before your testers can opt-in to your beta test, they need to join the Google Group or Google+ Community that you've added. After they've joined the Group or Community, they also need to opt-in to your beta test.

The link uses the following format: https://play.google.com/apps/testing/com.package.name

The opt-in link only shows when an app is "Published." Apps in "Draft" or "Pending publication" won't show the opt-in link.

After clicking the opt-in link, your testers will get an explanation of what it means to be a tester and a link to opt-in. Each tester needs to opt-in using the link to be part of the beta test.

Step 2: Add an APK to your test

Step 3: Get feedback

Once your alpha or beta testers have installed your app, they'll be automatically updated to use the test version within a few minutes.

Because your testers can't leave public reviews for alpha/beta apps on Google Play, it's a good idea to include a feedback channel or let your users know how they can provide you with feedback (e.g. by email, website, or a message forum).

Alpha/Beta version codes

Alpha and beta APKs need to have a higher version code than production APKs to be available for testing.

To be available for alpha testers, alpha APKs need to have a higher version code than beta APKs.

If a beta APK is uploaded with a higher version code than an alpha APK, the alpha version will automatically be deactivated.

If a Production APK is uploaded with a higher version code than an alpha or beta APK, the alpha and/or beta version will automatically be deactivated.

Alpha testing group users are eligible for the alpha, beta, or production version of your app with the highest version code that is compatible with their device. Beta testing group users are only eligible for the beta or production version of your app with the highest version code that is compatible with their device.