To publish an HTML app on Google Play in 2026 you need a $25 developer account, the app as a signed Android App Bundle (AAB) targeting a recent Android API level, a privacy policy URL, a completed Data safety form, a content rating and — for personal accounts created after November 2023 — a closed test with at least 12 testers for 14 continuous days. The app must also do more than display a website, under Play's minimum-functionality policy.
Technical requirements
- AAB format. New apps must be uploaded as Android App Bundles. HTML to AAB.
- Target API level. Play raises the minimum
targetSdkVersionevery year (API 35 became mandatory for new apps and updates in August 2025). Builds from HTML to App target a current API level, so this is handled for you — just rebuild apps you published long ago. - A stable package name.
com.yourbrand.appname. It can never change after the first upload. - Your own signing key for updates, and a version code that increases with every release.
Account requirements
- One-time $25 registration and identity verification.
- Closed testing for new personal accounts: at least 12 testers opted in for at least 14 continuous days before you can apply for production access. Organisation accounts are exempt.
- A real contact email, and a physical address shown on the listing if the app has in-app purchases or the account is an organisation.
Policy: minimum functionality
Play rejects apps that are "a website in a frame" with nothing app-like. HTML apps pass easily when they are apps: a tool, a game, offline content, a utility. For website-based apps, native features close the gap — push notifications, bottom-tab navigation, an onboarding flow, an offline screen. Avoid: a single page that just links out, content copied from sites you do not own, and repeating the same template app under many listings.
Store listing and declarations
| Item | Requirement |
|---|---|
| App icon | 512×512 PNG, 32-bit, ≤1 MB |
| Feature graphic | 1024×500 JPG or 24-bit PNG |
| Screenshots | 2–8 phone screenshots, 320–3840 px per side |
| Title / short description | 30 / 80 characters |
| Privacy policy | A public URL, required for every app |
| Data safety form | What data the app — including your website, SDKs and APIs — collects and shares |
| Content rating | IARC questionnaire |
| Target audience | Age groups; under-13 triggers the Families policy |
Data safety for an HTML app
The form is about what the app collects, which includes what your HTML collects. If your pages send analytics, contact forms, account data or location to a server, declare it. A purely offline HTML app with no network calls can truthfully declare that it collects no data. Push notifications via OneSignal mean a device identifier is collected for messaging.
Rejections HTML apps actually get
- Minimum functionality / webview spam — add real app features or bundle useful content.
- Broken functionality — reviewer found a blank screen or dead link. Test offline and on a cheap phone.
- Impersonation / IP — using a brand name or content you do not own.
- Missing privacy policy or inaccurate Data safety.
- Login required, no test account — give reviewers credentials in App access.
Questions people ask
Does Google Play accept WebView apps?
Yes. Many apps use WebViews. Play rejects only apps whose sole purpose is to display a website without added functionality, under its minimum-functionality and webview-spam policies.
Can I upload the APK to Play?
Not for a new app; Play requires an AAB. Use the APK for testing and direct distribution.
What is the 12-tester rule?
Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 opted-in testers for 14 continuous days before applying for production access.
How long does Play review take?
Typically a few days for a first submission, sometimes longer for new accounts. Updates are usually faster.