Frequently asked questions

HTML to App is an HTML 2 APK builder. It packages an HTML file, a ZIP of a web project or an HTML5 game into a signed Android app — an APK to install directly, or an AAB for Google Play — and adds native features such as a splash screen, bottom tabs and push notifications. You do not write any Android code.

Install the free HTML & ZIP to APK Builder app, choose your HTML file or ZIP, set the app name, icon, colour and package name, and start the build. The project is compiled and signed in the cloud in a few minutes, and you install the APK with one tap.

Yes. Free builds are complete signed APKs with no watermark and no expiry, for content up to 5 MB. Pro ($5 a month, through Google Play) adds AAB output for Play, your own signing key, splash screen, onboarding, bottom tabs, push notifications, branded loaders, 18 MB of content and no wait between builds.

Yes. Export the game for the web — Phaser, PixiJS, Three.js, Construct, GDevelop and similar — zip the export with index.html at the root, and build it. Canvas, WebGL, Web Audio and WebAssembly all run in Android's Chromium WebView at the same speed as in Chrome.

Yes, for HTML and ZIP builds: every file is bundled inside the APK and served from the phone. Only things your code fetches from other servers — APIs, CDN libraries, embedded videos — need a connection.

Yes. Build an AAB with Pro, signed with your own key, and upload it in the Play Console. You will need a $25 Google developer account, a privacy policy and the Data safety form, and new personal accounts must run a 14-day closed test with 12 testers first.

Yes. Build the app for production with relative paths (base: './' in Vite), switch the router to hash mode, and zip the build folder. The framework code runs unchanged.

5 MB of zipped content on the free plan and 18 MB on Pro. The finished APK is about 5 MB larger, the size of the app runtime.

No. The builder is an Android app and the build runs in the cloud, so you can go from an HTML file to an installed app entirely on your phone.

Use the URL route: the free Website to App app turns a live address into an app that loads your site and updates the moment you publish. HTML and ZIP builds are for content you want inside the app.

Camera, microphone and location work once you switch on the permission in the builder. File inputs open the system picker on Pro builds. Web Push, Web Share, Bluetooth, downloads and PDF viewing are not available inside a WebView.

HTML to App's free plan gives a signed APK with no watermark and adds native splash, onboarding, tabs and push on Pro; html2app.dev offers larger paid upload limits and a JavaScript bridge with plugins such as AdMob. See the full, dated comparison on the compare page.

Apps run on Android 7.0 (Nougat) and later — over 97% of active Android devices — using the Android System WebView, which Google Play keeps up to date.

No. HTML to App builds Android apps only. An iOS build needs Apple's toolchain and a developer account; for iPhone users, a PWA from the same HTML is the practical route.

Yes. Rebuild with the same package name, a higher version code and the same signing key (Pro), and upload the new AAB to Google Play.

Your project is sent to the build service to compile the app and kept with your account so you can rebuild. See the privacy policy for retention details.

Not through a native SDK — HTML to App has no plugin system. Web ad tags may not serve inside apps; check your ad network's rules. If native ads are essential, consider Capacitor.

Almost always absolute paths, history-mode routing, a CDN script, or file-name case. The blank-screen guide walks through each with a quick check.