To convert HTML to an APK, upload the HTML file to an HTML 2 APK builder, set the app name, icon and package name, and start a cloud build. The file is bundled inside the APK and served from the phone, so the app works offline. With HTML to App the signed APK is free, with no watermark.
- Calculators, converters and single-page tools
- Small HTML5 games in one file
- Landing pages, menus, price lists, event pages
- Prototypes you want on a real phone today
What counts as "an HTML file"
A single .html or .htm file becomes the app's index.html. Everything the page needs should be inside the file: <style> blocks, <script> blocks, images as data URIs or SVG. If your page links to style.css, app.js or an images/ folder, you do not have one file, you have a site — zip the folder instead, which works the same way and keeps the links.
Links to a CDN (https://cdn.jsdelivr.net/...) work while the phone is online but break in airplane mode. Paste your page into the CDN dependency scanner to list them, then download each file and bundle it.
Converting HTML to APK, step by step
- Check the page on a phone first. Open it in Chrome on Android or in your desktop browser's device mode. Add
<meta name="viewport" content="width=device-width, initial-scale=1">if text renders tiny — the viewport meta builder writes the right tag. - Install the builder. HTML to App builds run in the free HTML & ZIP to APK Builder Android app. Sign in once with Google.
- Pick "HTML file" and choose your page. It is previewed in a phone frame, served exactly as the finished app will serve it.
- Name it and brand it. App name, a square icon (512×512 PNG is ideal), a theme colour for the status bar, a package name such as
com.yourname.tipcalcand a version. - Build and install. The cloud build compiles and signs the APK in a few minutes. Tap the download, allow "install unknown apps" once, and it is on your home screen.
What happens to your file inside the APK
The file is copied byte for byte into the APK's assets. When the app launches, Android's WebView — the same Chromium engine as Chrome — loads it from https://appassets.androidplatform.net/web/, a local https address Android reserves for exactly this. Nothing goes over the network. Because the page has a real https origin rather than file://, the things that usually break in naive HTML-to-APK wrappers keep working: localStorage, IndexedDB, fetch() of bundled JSON, ES modules and WebAssembly.
Data your page stores in localStorage survives app restarts and updates, which makes a one-file app perfectly usable for notes, scores, settings and to-do lists.
Limits worth knowing before you build
- Size: 5 MB on the free plan, 18 MB on Pro. A one-file app almost never comes close.
- Downloads and PDFs: the WebView has no download manager and cannot display PDFs. Show content as HTML instead.
- Web Push and Web Share: not available inside a WebView. Native push notifications are a Pro feature instead.
- Google Play: needs an AAB, not an APK — a Pro build. The APK is for direct installs, testing and sharing.
HTML to APK — questions
Can I convert HTML to APK without coding?
Yes. You upload the HTML file, fill in a name and an icon, and the builder generates, compiles and signs the Android project for you. You never open Android Studio or write Java or Kotlin.
Does the HTML APK work offline?
Yes. The HTML file is packed inside the APK and served from the phone itself, so it opens with no connection. Only resources your page loads from other servers — CDN scripts, web fonts, APIs — need the internet.
Is the APK signed?
Every build is signed, because Android will not install an unsigned APK. Free builds use a shared release key; Pro lets you sign with your own key, which you need to keep updating an app on Google Play.
Can I convert HTML to APK on my phone?
Yes — the builder is an Android app, so the whole conversion happens on the phone: pick the file from Downloads or Drive, build, install.