Google Play New Developer Account Restrictions: What You Can and Can't Do

If you registered a Google Play developer account recently, you're working under a different set of rules than developers who registered years ago. Google has added significant restrictions to new accounts — some are temporary, others are permanent features of the personal account type.

The biggest restriction: mandatory closed testing

The most impactful restriction for new personal accounts is the closed testing requirement. Before your app can go live on the public Play Store, you must:

• Run a closed testing track with at least 12 active testers
• Maintain that count for 14 consecutive days
• Then apply for production access and wait for manual review

This requirement does not apply to organization accounts (in most cases) or to developer accounts created before this policy took effect. If you ask an older developer why they didn't have to do this, that's why.

There is no way to waive or bypass this requirement for personal accounts. The 14 days are non-negotiable.

What you can do immediately after registration

Despite the restrictions, new accounts can do quite a lot before production access is granted:

• Internal testing — unlimited testers, no waiting period, releases go live in minutes. Use this for your own QA and small team testing.
• Closed testing — up to 2,000 testers per track, this is where you run the mandatory 14-day period
• Open testing — unlimited public testers, app gets an "Early access" badge on Play Store (does not count toward production access requirement)
• Build and upload AABs — no limit on how many builds you upload
• Create and edit store listings
• Set up in-app purchases and subscriptions — you can configure these before going live

What you cannot do until production access is granted

• Publish to production — the app won't appear in general Play Store search results or be installable by the public
• Run paid apps or in-app purchases at scale — while you can configure monetization, real transactions require a live production app
• Appear in Play Store rankings or charts

App limits per account

New personal accounts have a limit on how many apps they can publish. Google has not published the exact number publicly, but developers have reported being capped at around 10-20 apps before needing to request an increase. Organization accounts have higher default limits.

If you're building a portfolio of apps or a batch of tools, this can become relevant. Contact Google Play support to request a higher limit once you've established a track record with your account.

Higher scrutiny on policy violations

New accounts are reviewed more carefully than established ones. An app that might get a warning for an established developer can result in immediate suspension for a new account. This isn't an official policy — it's an observed pattern.

Practical implications:

• Be conservative with app content until you have an established track record
• Read the Google Play Developer Program Policies before submitting — especially around ads, data collection, and impersonation
• Don't publish apps that mimic other well-known apps or use trademarked terms in app names
• Make sure your privacy policy is accurate and complete — vague or missing privacy policies are a common trigger for policy violations

Account suspension risks for new accounts

New accounts are more vulnerable to permanent suspension because there's no history to appeal against. A few things that can trigger suspension:

• Publishing an app that violates content policies (even unintentionally)
• Using the same device or payment method as a previously terminated account
• Creating multiple developer accounts to bypass restrictions — this is explicitly against policy and results in termination of all accounts
• Submitting an app with deceptive metadata (misleading screenshots, keyword stuffing in the title)

If your account is suspended, appeals are handled through Play Console. The process is slow and success is not guaranteed for new accounts with no history.

Do restrictions go away over time?

The closed testing requirement is a one-time gate per app — once you complete it and receive production access for your first app, subsequent apps on the same account also require closed testing. It doesn't go away after your first app, but it does become faster once you have a network of testers.

Other restrictions (app limits, scrutiny level) improve as your account history grows. After publishing several apps without policy violations, Google tends to treat your account with more trust.

Should you use an organization account instead?

If you're building apps as a business — even a solo business — an organization account is worth considering. The closed testing requirement still applies in many cases, but organization accounts have higher app limits, show a business name instead of your personal name, and are generally treated as more established by Google's systems.

The trade-off: you need business documentation to register, and you can't convert a personal account to an organization account later. If you're unsure, start with a personal account and create an organization account later for your more serious projects.

Frequently asked questions

Related articles