PWA to APK: Convert Your Web App in Minutes

Yes — you can convert a PWA to APK in a few minutes, without installing Android Studio, without generating a keystore by hand, and without writing a single line of Java or Kotlin. The modern path is a Trusted Web Activity (TWA): Google's own method for shipping a Progressive Web App as an Android app on Google Play.

APK vs AAB — clarify the target first

An APK and an AAB are not interchangeable. Decide which one you need before you build (you get both from PWAtoApp anyway).

How a Trusted Web Activity build works

A TWA opens your verified domain inside the user's own Chrome engine, full screen, with no address bar. There is no duplicated native codebase and no WebView hack — which is why the resulting app is often under 1 MB instead of the several megabytes a wrapper ships.

What your PWA needs

• HTTPS — mandatory. Plain HTTP URLs are rejected by the TWA runtime.
• Web manifest with name, start_url, display: "standalone", theme_color and an icon of at least 512×512.
• Service worker — strongly recommended. It controls offline behaviour and satisfies Google Play's minimum functionality policy.
• Digital Asset Links — the /.well-known/assetlinks.json file that proves you own the domain and removes the URL bar.

PWA to APK, step by step

• 1. Paste your PWA URL. We read your manifest, icons and service worker automatically.
• 2. Set your app identity. App name (30 characters max on Play), package name such as com.yourcompany.app — which can never be changed after first publish — and version code 1.
• 3. Upload a 512×512 icon. Square PNG, no rounded corners; Android applies the mask itself.
• 4. Launch the build. Manifest parsing, keystore generation, compilation and signing all run server-side.
• 5. Download your files. Signed APK for sideloading and alternative stores, signed AAB for Google Play, plus the signing certificate.

Common errors and how to fix them

"App rejected — minimum functionality (policy 4.3)"

Usually a raw WebView wrapper with no service worker and no real PWA behaviour. A validated TWA build with a manifest and service worker passes by design.

"Digital Asset Links verification failed"

The assetlinks.json file is missing, or the SHA-256 fingerprint inside it does not match the certificate the app was signed with. Re-host the exact file we generate for your build.

"Keystore not found on update"

Google Play requires the same signing identity for every update. Always rebuild from the same project so the original keystore is reused — a new keystore means a rejected update.