HTML to APK converter Turn your HTML into an Android app.

What you can convert

HTML to AAB works with the files you already have. No framework, no build tools, no Android project.

• A single .html file: a landing page, a calculator, a small game or a tool.
• A .zip of a whole site: your HTML pages together with their CSS, JavaScript and images.
• A live website: if your HTML is already online, use the domain instead. See Website to APK.
• A React production build: zip the dist or build folder. See React to APK.

HTML to APK in six steps

1. 1

   Install HTML to AAB

   Get the app from Google Play and start a new project.

2. 2

   Upload your HTML

   On the Source step choose Upload an HTML file and pick your .html file or the .zip of your site.

3. 3

   Make it yours

   Set the app name and icon, pick a splash animation and choose colors, gradients and a logo style.

4. 4

   Fill in the technical setup

   Package name (for example com.yourname.appname), version name, version number, Min SDK and Target SDK. Each field explains what Google Play expects.

5. 5

   Choose permissions

   Internet and network state are required. Add anything else only if your HTML really needs it.

6. 6

   Monetize and build

   Optionally add AdMob banners or a lifetime purchase, then build your Android App Bundle.

APK or AAB: which one do you need?

Most people search for “HTML to APK” because APK is the Android file everyone knows. But if you want to be on Google Play, the file you upload is an AAB (Android App Bundle): since August 2021, new apps on Google Play must be published as app bundles.

You upload the AAB once and Google Play builds optimized APKs for every device: smaller downloads for your users, no extra work for you. That is why HTML to AAB builds an AAB. Read the full comparison in APK vs AAB.

Make your HTML feel like a native app

• Add a responsive viewport: <meta name="viewport" content="width=device-width, initial-scale=1">.
• Use relative paths (./css/style.css, images/logo.png) so assets resolve wherever the files are loaded from.
• Design for touch: tap targets of at least 48 × 48 dp and no hover-only menus.
• Keep the first screen light. The splash screen covers loading, but a fast first paint still feels better.

Frequently asked questions