Getting started
What do I need to convert a ZIP file to an APK?
A ZIP of your web project with index.html at its root, a square logo, and a few minutes. No Android Studio, no SDK, no coding. The full walkthrough is in how to convert a ZIP file to an APK; the single-file and URL routes work the same way.
Does index.html have to be at the root of the ZIP?
Yes. It must be at the top level, not inside a folder. Compress the folder's contents, not the folder. The ZIP checker spots the wrapper-folder mistake instantly and the Folder to ZIP tool avoids it.
Do I need to know how to code?
No. You need a website that already works; everything Android-specific is handled for you. If you want to understand what is being generated, the guides explain each piece.
How long does a build take?
Usually a few minutes. Your settings and content are sent to the build service, which compiles a real Android project and returns a signed file. You can leave the page — the build carries on, and the result is waiting when you come back.
Can I convert a WordPress, Shopify or Wix site?
Yes, by pointing the app at the live URL rather than bundling files. Those platforms generate their pages server-side, so there is no folder of HTML to export. The app then loads your site the way a browser would, and needs a connection to do it.
How the app behaves
Will my app work offline?
Only if you bundle your content into the app rather than loading a live URL. A bundled app serves its pages from the device and works in airplane mode. A URL-based app needs a connection for every screen.
Why does my app show a blank white screen?
Nearly always one of three things: index.html was not at the root of the ZIP; the pages use absolute paths starting with /; or a script is loaded with type="module", which browsers block on bundled file:// pages. The ZIP checker finds all three, and the blank-screen guide covers the rarer causes.
Can my app use the camera, microphone or location?
Yes. Enable the permission when you build, and the standard web APIs work inside the app. Background location and Bluetooth are the notable exceptions — those need a native app.
Does the back button work?
Yes — it navigates your page history and only exits the app at the first page, which is what Android users expect.
Google Play
Can I publish a converted website on Google Play?
Yes, provided the app does more than a browser bookmark would. Play's minimum functionality policy rejects apps that are only a URL in a wrapper. Bundled offline content, push notifications, native tabs and a proper splash screen all count as real functionality. See from ZIP to Google Play.
Why will Play not accept my APK?
New apps must be uploaded as an App Bundle (AAB), not an APK — a requirement since August 2021. AAB output is part of Pro. The difference between the formats is explained in the Google Play guide.
Can I convert a website I do not own?
No. You must own the content or have permission to distribute it. Wrapping someone else's site is a copyright violation, it is rejected by Google Play, and it is grounds for us to remove your account. See our DMCA policy.
Files, size and signing
How big can my ZIP be?
Free accounts can upload up to 5 MB of web content; Pro raises that to 18 MB. Those are limits on your source files, not on the finished app. Most sites are far under them once images are sensibly sized — the size estimator shows exactly where your bytes are going.
How big is the finished app?
The Android runtime is roughly 2.6 MB before your content. Text compresses to about a quarter of its size inside the package, so a large HTML site often adds only a few hundred kilobytes. Bundled images and video dominate everything else.
What is a signing key, and do I need one?
Android refuses to install an unsigned app, so every build is signed. For a free build we sign it for you. If you publish on Play and will ship updates, you need your own key — every update must be signed with the same key as the original — which is a Pro feature. Keep a backup of it: an app whose key is lost cannot be updated.
Can I update my app later?
Yes. Rebuild with a higher version code and the new file installs over the old one, keeping user data — as long as it is signed with the same key. See the updating guide.
Account, billing and privacy
Why do I need an account to build?
Builds consume real compute and are tied to an identity so we can apply limits fairly, keep your projects between sessions, and let you download an artifact later. The tools need no account, because they never touch our servers.
What happens to the files I upload?
Content you submit for a build is transmitted to the build service, used to produce your app, and retained with your project so you can rebuild or download it again. You can delete a project, which removes its build. Files you drop on the tools are never uploaded at all — they are processed in your browser. Details in the privacy policy.
How much does it cost?
Building APKs is free. Pro — AAB output, your own signing key, splash, onboarding, tabs and push — is a subscription sold through Google Play in our Android app. See pricing.
Can I get a refund?
Google Play handles subscription refunds, including the self-service window straight after purchase. Our refund policy explains what to do and when we can help.