Free website-to-app converters export something. Whether Google Play will accept it is a different question. Disclosure up front: I work with ZoopCoder, an Indian shop that builds and submits these apps for a fixed fee, so I have a commercial interest in this answer — but the two rules below are Google's own, not ours, and are worth knowing before you spend a rupee anywhere.
Rule 1: Play has not accepted a plain APK for a new app since August 2021
Google Play requires new apps to be submitted as a signed Android App Bundle (.aab), not a raw APK. This has been true since August 2021, so it isn't new — but a lot of free "website to app" converter tools still hand you a bare .apk file, because building an AAB means the tool has to manage a proper signing keystore for you, which is more than a wrapper script usually does.
If your converter's output is a .apk and not a .aab, you cannot upload it as a new app. Full stop.
Rule 2: every app must target API level 36 (Android 16) — enforced from 31 August 2026
Since 31 August 2026, Google requires new apps and app updates to target API level 36 (Android 16) to be submitted to Play at all. A converter built even a year ago, targeting an older API level, produces a bundle Play will now reject outright — not "flag for review," reject at upload.
There was a one-off extension available (to 1 November 2026) for developers who filed for more time through Play Console, but it does not renew, and a brand-new project has no reason to ask for it — it should just target 36 from the start.
What this means practically
If you already have a website and want it on Google Play, the wrapper approach (website content shown inside a native Android shell, with an icon, splash screen, offline handling, and native link handling for things like WhatsApp/phone/maps links) is still the fastest, cheapest route to an app — usually far cheaper than a full native rebuild. But the deliverable has to actually be:
- a signed .aab, not an .apk
- targeting API 36, not whatever the tool defaulted to a year ago
- built with an upload keystore you're handed, not one locked inside someone else's tool, because you need it for every future update
None of that is exotic to build correctly — it's just two checkboxes a lot of free tools skip because their business model is "generate once," not "keep apps updatable and compliant."
For reference, I do this at fixed prices: wrapping an existing website into a Play-ready Android app (signed AAB, API 36, keystore handed over) is ₹4,999, and the separate Play Console submission — store listing, content rating, Data safety form, and actually sending it for review — is ₹1,999 on top of Google's own one-time US$25 developer fee. Details: https://zoopcoder.com/services/website-to-android-app.php and https://zoopcoder.com/services/play-store-app-publishing.php
Either way — DIY, a free tool, or paying someone — check the AAB format and the API level before you assume the app is ready. Those two checks catch almost every "why was my upload rejected" surprise before it happens.
Top comments (0)