Launch prep hub

Internal vs closed vs open testing

Compare when Google Play's internal, closed, and open testing tracks are each the right choice.

Check these first

  • Internal testing (up to 100 people) ships instantly without review, so use it for build checks during development.
  • Only closed testing satisfies the production requirement (12 testers / 14 days) for new personal accounts. Internal testing does not count.
  • Open testing is visible on the store, so use it after closed testing when you want broader feedback.
  • Tester lists are managed per track, so record who you invited to which track.

Read alongside the official docs

Platform policy changes, so treat this page as a reference checklist and confirm the official documentation before your final submission.

Frequently asked questions

Q. Can internal testing satisfy the 12-tester requirement?
No. For new personal developer accounts, the production promotion requirement can only be met on the closed testing track. Internal testing is a development track that ships without review.
Q. How do I move from internal to closed testing?
Promote the internal testing build to the closed testing track in Play Console. The first closed testing release goes through Google review, so allow a day or more.
Q. Can I update the app during closed testing?
Yes. Uploading a new build during the test window does not reset the 14-day count. Still, prioritize critical fixes like install failures or sign-in problems to avoid losing testers.

Post whatever is blocking you

Include your app name, platform, current launch stage, and the docs you already checked — it helps answerers narrow down the cause.

Write a question