How to upload an app on the Play Store in 2027: account, testing and review

Summary. To upload an app on the Play Store, open a Google Play Console developer account (a one-time US$25 fee; you must be 18 or over), verify your identity, create the app, upload a signed Android App Bundle (AAB), complete the store listing and App content declarations, and roll out a release. If your personal account was created after 13 November 2023, you first need a closed test with at least 12 testers opted in for 14 days in a row, then apply for production access, which Google says usually takes seven days or less to review. Organisation accounts skip that test but need a free nine-digit D-U-N-S number, which can take up to 30 days. Since 31 August 2026, new apps and updates must target API 36 (Android 16), and Google's blog says API 37 follows in August 2027. Every app on a closed, open or production track needs a Data safety form and a privacy policy. New accounts must also declare whether they are a trader under EEA and UK consumer law; existing accounts have until 1 February 2027. Google recommends at least a week between submitting and going live.

About this article. For first-time Android developers, founders and IT teams, in India and elsewhere. We checked every step, fee, limit and menu path against Play Console Help, developer.android.com and the Android Developers Blog on 11 November 2026, using the Play Console web interface as those pages describe it; device verification needs a phone on Android 10 or later. Play Console labels change, so a button may read slightly differently in your account. This is general information, not legal or tax advice, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.

Play Store upload requirements at a glance

The table summarises the rules as Google's help pages state them on 11 November 2026.

Step 1: Choose a personal or organisation account

Both types share core features and can earn money through a payments profile; the checks and public details differ.

If a business is behind the app, choose an organisation account: the app stays in the company's name and the personal-account testing rule does not apply.

Step 2: Register, pay the fee and verify your identity

1. Sign in with a Google Account and open the Play Console sign-up page.

1. Accept the Google Play Developer Distribution Agreement.

1. Pay the US$25 registration fee with Mastercard, Visa, American Express, Discover (US only) or Visa Electron (outside the US). Prepaid cards are not accepted.

1. Choose the personal or organisation account type.

1. Verify your identity. Your legal name and address come from the Google payments profile linked at sign-up. Google may ask for a government ID and a card in your legal name; if they prove invalid, the fee is not refunded.

1. Verify your contact email, contact phone and developer email (and, for organisations, the developer phone) with one-time passwords, and keep them working for the life of the account.

1. Declare your trader status under Manage account > Account details > About you. New accounts do this at creation; existing accounts have until 1 February 2027, after which Google may block updates and remove apps worldwide. If you do not distribute in the EEA or UK, you can declare as a non-trader. A trader on a personal account must show a phone number and address publicly.

For organisations: get the D-U-N-S number first. Dun & Bradstreet issues this nine-digit identifier. Search for an existing one first, since many companies already have one. Applying is free, and Google warns about third parties that charge for it. It can take up to 30 days, and you cannot create an organisation account without it.

The legal name and address in your payments profile must match your Dun & Bradstreet record. If they drift apart, Play Console flags that your organisation name or address is no longer verified; miss the deadline it gives and the account can be restricted, removing all your apps. Government agencies without a D-U-N-S number, and organisations in regions Dun & Bradstreet does not cover, should contact Play support before creating the account.

Step 3: Complete device verification and check developer verification

Device verification (personal accounts). On the Play Console Home page, find the task asking you to verify access to an Android mobile device and click View details. Scan the QR code to install the Play Console mobile app, sign in as the account owner, select your developer account and tap Verify. Any non-rooted physical phone on Android 10 or later works, and Google says it takes under a minute.

Android developer verification. This separate platform programme ties apps on certified Android devices to a verified developer. Protections began on 30 September 2026 for users in Brazil, Indonesia, Singapore and Thailand who install from participating stores on certified devices running Android 7 or later, and Google plans to extend the capability to all apps on certified devices worldwide in 2027.

For Play developers the extra work is small: Google says Play registered 99% of apps automatically, and a new app's package name is registered to your account when you create it, with Play Console asking for another name if it is taken. Apps distributed only outside Play are registered in the Android Developer Console, where students and hobbyists can open a free limited distribution account; Google's guide, updated 28 October 2026, allows up to 50 authorised devices, though its overview still says 20. Our guide to developer verification for apps outside Play covers the sideloading side.

Step 4: Create the app in Play Console

1. Sign in to Play Console and click Create app.

1. Enter the app name as it should appear on Google Play (you can change it later).

1. Enter the package name. It must match the applicationId in your build, which identifies the app on devices and on Play; change it after publishing and Play treats the upload as a different app. Package names are unique and permanent, and cannot be deleted or reused.

1. Select a default language.

1. Choose app or game, and free or paid. A free game also appears on Google Play Games on PC by default.

1. Add a contact email for users.

1. In the Declarations section, acknowledge the Developer Program Policies and US export laws, and accept the Play App Signing Terms of Service.

1. Click Create app. The Dashboard then lists the setup tasks in order.

Step 5: Prepare the release build

Play Console accepts only builds that meet its technical rules. Our guide on how to develop an Android app covers the build in Android Studio; the checklist is:

• Android App Bundle. Build a signed .aab file. New apps have had to publish as AABs since August 2021, and TV apps since June 2023. Apps still on APKs are held to a legacy 100 MB limit.

• Play App Signing. Google holds the app signing key and you sign uploads with an upload key, which Play Console can reset if lost. If you manage your own app signing key and lose it, Google cannot recover it and you cannot update the app.

• Target API level. Since 31 August 2026, new apps and updates must target API 36. Wear OS and Android Automotive OS apps need API 35, and Android TV and Android XR apps API 34. The extension Google offered ran only to 1 November 2026. A 13 February 2026 Android Developers Blog post says Play will require API 37 for new apps and updates in August 2027; the Play Help page had not added that date on 11 November 2026. Our note on the August 2027 API 37 deadline tracks the timeline.

• Version code. Raise versionCode with every upload and keep it at or below 2,100,000,000.

• Size. Play measures compressed download size: 500 MB for the base module and for each feature module, 1.5 GB per asset pack, 4 GB in total for modules and install-time asset packs, and 34 GB overall. Above 200 MB, users on mobile data see a size warning.

Step 6: Complete the store listing

Go to Grow users > Store presence > Store listings (some help pages say Main store listing) and fill in the details and graphics.

Choose a category and tags in the same area. Google's Metadata policy bars titles, icons and text that suggest store ranking, price or promotions, and emojis in the title, icon or developer name.

Step 7: Complete the app content declarations

Open the App content page (Monitor and improve > Policy and programs > App content; older help pages show it under Policy). Each declaration must be complete before you can release.

1. Privacy policy. Link a privacy policy on your store listing and inside the app, even if the app handles no personal data. Host it as a public web page (not a PDF) with a valid SSL certificate and no login or geoblocking. The Data safety form also requires it.

1. Ads. Declare whether the app shows ads, including through third-party SDKs; apps with ads get a label on the listing.

1. Sign-in details. If any part of the app needs a login, membership or location, give reviewers working access details (up to five sets). Google lists working test credentials among its pre-application checks.

1. Target audience and content. Declare the target age groups. If any group includes children, the app must follow the Families policy, and ads shown to children or users of unknown age must come from Families Self-Certified Ads SDKs.

1. Content rating. Click Start, enter an email address for correspondence with the International Age Rating Coalition (IARC), pick a category and answer the questionnaire. The answers produce ratings from authorities such as ESRB, PEGI, USK and ClassInd, and misrepresenting content can lead to removal or suspension.

1. Data safety. Declare what data the app and its SDKs collect and share, why, whether it is encrypted in transit and whether users can request deletion. Every app on a closed, open or production track needs the form; apps only on internal testing are exempt. Google reviews the answers and shows them on your listing, but you alone answer for their accuracy.

1. Sensitive permissions. High-risk permissions such as SMS or Call Log may need a Permissions Declaration Form and approval.

The Data safety answers must cover every third-party SDK: data an SDK collects counts as your app's collection even if your own code never touches it.

Step 8: Run internal and closed tests (the 12-tester, 14-day rule)

Play Console offers four tracks.

For personal accounts created after 13 November 2023, the Production and Pre-registration pages stay disabled until you meet the testing rule: when you apply, at least 12 testers must have been opted in to your closed test without a break for the previous 14 days. A tester who opts out and rejoins needs 14 fresh consecutive days.

1. Create a closed test and add testers by email list (up to 2,000 per list) or Google Group (no size limit), then share the opt-in link. A new test link can take several hours to work.

1. Ask testers to stay opted in for 14 days and use the whole app. Recruit more than 12 to absorb drop-outs.

1. Read feedback under Monitor and improve > Ratings and reviews > Testing feedback and ship fixes to the closed track; you summarise it when you apply.

1. Run a pre-launch report to catch crashes and warnings before review.

1. On the Dashboard, click Apply for production and complete three sections: about your closed test, about your app or game, and about your production readiness.

Google emails the account owner when the review ends, usually within seven days. With fewer than 12 opted-in testers or weak engagement, you may be told to keep testing.

Step 9: Roll out to production and pass review

Open Test and release > Production, click Create new release, upload the AAB or add a tested one from the library, name the release and add release notes (up to 500 characters per language), then preview and start the rollout. A first release sets up Play App Signing and has no rollout percentage; it publishes the app in your chosen countries. If the summary shows an errors section, fix those first; warnings do not block publishing.

Changes are not sent for review automatically. Open the Publishing overview page and click Send for review. With standard publishing, approved changes go live as soon as possible. Managed publishing lets you choose when approved changes go live, but only once the app is already available, so it cannot time a first launch. Google says some accounts get extended reviews of up to seven days, or longer in exceptional cases, and recommends at least a week between submitting and going live. For later updates, staged rollouts release to a percentage of users first.

Common upload errors and rejections

The fixes below come from the Play Console Help pages cited in the steps above.

India notes: payment, tax and service fees

• Paying the fee. The fee is in US dollars. At European Central Bank reference rates for 10 November 2026, a dollar bought about ₹93.93, so US$25 comes to roughly ₹2,350 (25 x 93.93 = 2,348.25) before any foreign-currency markup your bank adds. Prepaid cards are not accepted.

• Getting paid. To sell apps or digital goods, add a bank account to your payments profile from the Play Console Settings page. Google verifies it by test deposit or bank documents, which can take up to 5 days. Only the account owner can manage merchant payment accounts.

• GST. Google's tax page says developers located in India must work out whether they need a GSTIN and must pay any tax due on Google Play service fees. As a marketplace intermediary, Google also deducts withholding tax and GST TCS on paid apps and in-app purchases sold by Indian developers. Ask your chartered accountant how this applies.

• Service fees. Google says 97% of developers distribute on Play without paying a service fee. Fees depend on where the buyer is: sales to users in Australia, the EEA, Japan, the UK and the US already follow Google's new rate card. India falls in the rest-of-world group, scheduled for 30 September 2027. Until then, Play charges enrolled developers 15% on the first US$1 million of annual earnings and 30% above it, and 15% on auto-renewing subscriptions. If you offer an alternative billing system to users in India, Google reduces the fee on those transactions by 4%. Our breakdown of the 2026 Play fee split works through the new rate card.

For IT teams and businesses

• Own the account centrally. Create the organisation account with a shared, monitored address on your own domain. Google says organisation contact and developer emails should not be generic or personal, and it may remove apps if the developer email or phone stops working.

• Use roles, not shared passwords. Invite developers, QA and marketing as users with only the permissions they need; access to financial data is a separate permission. Only the account owner can manage merchant payment accounts, so keep that role with the company.

• Private enterprise apps. Permanently private apps restricted to one organisation and distributed internally are exempt from Play's target API rules. Apps you distribute to staff outside Play need registering for Android developer verification as it expands in 2027.

• Trader status. Settle your EEA and UK trader status with legal advice before 1 February 2027. From 1 March 2027, when Play moves to a marketplace model in those regions, a trader's contact details, D-U-N-S number and terms of service link are shown to users.

• Keep declarations consistent. Data safety answers, the privacy policy and in-app consent should tell the same story; Google can act on a gap between declarations and app behaviour.

• Plan the yearly cycle. Play raised the target API floor on 31 August in 2025 and 2026, so budget an upgrade, a closed-track regression test and a Data safety review every year.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our Android developers can prepare your app for Google Play, from Play App Signing and target API upgrades to store listing assets, Data safety declarations and closed testing. Talk to us at /contact-us/.

Last updated: 11 November 2026.

References

1. Get started with Play Console — Google Play Console Help

1. App testing requirements for new personal developer accounts — Google Play Console Help

1. Required information to create a Play Console developer account — Google Play Console Help

1. Target API level requirements for Google Play apps — Google Play Console Help

1. Prepare your app for the resizability and orientation changes in Android 17, 13 February 2026 — Android Developers Blog

1. Provide information for Google Play's Data safety section — Google Play Console Help

1. Trader status declaration — Google Play Console Help

1. Control when app changes are reviewed and published — Google Play Console Help

1. Device verification requirements for new developer accounts — Google Play Console Help

1. About Android App Bundles — Android Developers

1. Publish your app — Google Play Console Help

1. Choose a developer account type — Google Play Console Help

1. Create and set up your app — Google Play Console Help

1. Developer account registration payment methods and receipts — Google Play Console Help

1. Android developer verification — Android Developers

1. Register on Google Play Console, last updated 30 September 2026 — Android Developers

1. Register for limited distribution on Android devices, last updated 28 October 2026 — Android Developers

1. Configure the app module — Android Developers

1. Optimize your app's size and stay within Google Play app size limits — Google Play Console Help

1. Sign your app — Android Developers

1. Add preview assets to your store listing (help article 9866151) — Google Play Console Help

1. Metadata policy — Google Play Console Help

1. Prepare your app for review — Google Play Console Help

1. Manage target audience and app content settings — Google Play Console Help

1. Participate in the Families Self-Certified Ads SDK Program — Google Play Console Help

1. Content rating requirements for apps, games, and the ads served on both — Google Play Console Help

1. Set up an open, closed, or internal test — Google Play Console Help

1. Prepare and roll out a release — Google Play Console Help

1. Euro foreign exchange reference rates, 10 November 2026 — European Central Bank

1. Tax rates and value-added tax (VAT) — Google Play Console Help

1. Service fees — Google Play Console Help

1. Understanding Google Play's lower service fees — Google Play Console Help

1. Add developer account users and manage permissions — Google Play Console Help