WEBSITE TO APK
Website to APK — turn any URL into an Android app
Updated November 10, 2026
- Free test
- No account needed
- Result in 10s
- Your code stays yours
How a URL becomes an Android app
Your site is not rewritten and not copied. The build produces a small native Android app that opens your URL full screen, under your name and your icon, with no browser bar. Because your code stays on your server, anything you deploy to the site shows up in the installed app the next time it opens: no new release, no store review, no asking users to update. What the app adds is what a website cannot have on its own — a place in the app drawer, a launch screen, a listing on Google Play, and, if you set them up, a native header with a tab bar or side menu.
From URL to APK in four steps
1. Check your web address
Paste it into the checker above. Any HTTPS site works; the checker tells you in about ten seconds whether it is a PWA and what is missing — icon, name, HTTPS.
2. Name your app
Set the app name, the package name (permanent — for example com.yourdomain.app), the icon and the colors. They are read from your site where possible.
3. Build
A cloud build produces the signed APK and, on a paid build, the AAB, usually in one to five minutes. The signing key is generated with your first paid build and kept for every update; the free test build uses a temporary key.
4. Install or publish
Install the APK on your phone to try it. A paid build delivers the signed files each store asks for, starting with the AAB for Google Play.
APK or AAB: which file do you actually need?
People look for a website to APK converter and expect one file. Android actually uses two formats that do different jobs — and a third thing, the signing key, that decides whether you can ever update the app.
| File | What Android does with it | What SaasToStore gives you |
|---|---|---|
| .apk | Installs directly on a phone: send it to testers, sideload it, try it before release. Google Play no longer accepts it for new apps. | A signed APK in every build — the free test build is an APK too. |
| .aab | The Android App Bundle, uploaded to Google Play, which then builds an optimized APK for each device. Required for new Play apps since August 2021. | A signed AAB in every paid build, ready for Google Play. |
| Signing key | Every update must be signed with the same key as the first release, or the store refuses it. | One key per project, created at your first paid build, kept encrypted and backed up, its password emailed to you once. |
Two ways to wrap a website — and which one your site gets
There is no single "website to APK" technique. If your site is a PWA, the lightest option is a Trusted Web Activity, the approach Google recommends. Otherwise, the app is a native shell around Android's system web view. SaasToStore recommends one from what the checker finds, and you choose in the build selector.
| Trusted Web Activity | Native WebView shell | |
|---|---|---|
| Recommended when | Your site has a web app manifest (a service worker is recommended for offline use, not required) | Any HTTPS site — no manifest or service worker needed |
| What runs your site | Chrome, already on the phone, full screen | Android's system web view, inside our native shell |
| Browser bar | Hidden once your site serves the small assetlinks.json file we generate | Never shown |
| Native navigation | Your site's own | Optional native header, tab bar or side menu |
| Google sign-in | Works as in Chrome | Works after a one-time setup — Google blocks sign-in inside web views |
| Android TV | Not available | Available, with remote-control navigation |
Want the PWA route in detail? PWA to APK covers the manifest, the service worker and the checklist.
What Google Play checks before your app goes live
Google Play is less strict than Apple's review, but it does reject apps. These are the checks that matter for a wrapped website — the first two are handled by the build, the others depend on you.
- Target API level: our builds target Android 16 (API level 36), the level Google Play requires for new apps and updates since 31 August 2026
- Signed AAB: required for every new app, signed with the same key for every update
- The site must be yours: Google refuses apps that only display a website the developer does not own or administer
- The app must work: no crash, no blank screen, no page that only says “open this in your browser”
- A privacy policy URL and the Data safety form, filled in for what your site actually collects
- Digital goods sold inside the app go through Google Play Billing in most countries
The same URL, on every platform
Android is rarely the only place your users are. The same web address also builds a signed iPhone app for the App Store, Windows, macOS and Linux installers, and an Android TV app. SHIP covers one app on all of them for €39, once: the first build plus three updates per platform, for 12 months. See what Apple accepts from a website and Website to EXE for the other two big ones.
What you get
- A signed APK to install on any Android phone
- A signed AAB, the file Google Play asks for (paid builds)
- Your own signing key, created at your first paid build, kept encrypted and reused for every update
- Your icon, your app name, your colors and launch screen
- The Trusted Web Activity or WebView build, recommended from your site — you choose
- Optional native header, tab bar or side menu (WebView build)
- Targets Android 16 (API level 36)
- Free test APK with our logo; your published app is SHIP, €39 one-time
When an APK is the wrong answer
Your app has to work with no connection
The app loads your live site. For a genuinely offline product, give the site a service worker with an offline cache first — the app then inherits it. Packaging alone does not make a web app work offline.
You need deep device access
Background services, Bluetooth pairing or heavy 3D are outside what a web view reaches comfortably. That is a native app, not a wrapped site.
Your site is not usable on a phone yet
The app shows your site as it is. If it is not responsive, fix that first: no app shell hides a desktop-only layout from Google Play's reviewers.
Works with every website builder
Any HTTPS URL also works — no website builder required.
The kind of site matters less than how it behaves on a phone: a SaaS dashboard, an online store, a booking site or a blog all convert to an Android app, as long as the pages fit a small screen and every button can be reached with a thumb.
Related pages
Website to APK — frequently asked questions
Can I really turn a URL into an APK?+
Yes. Paste any HTTPS web address and SaasToStore builds a signed Android app from it: an APK you can install on a phone and, on paid builds, the AAB that Google Play requires. You install nothing — no Android Studio, no Gradle, no Java — the build runs in the cloud.
Does my website need to be a PWA?+
No. The lighter Trusted Web Activity build starts from your web app manifest; a service worker is recommended for offline use, not required. The native WebView shell works with any HTTPS site and needs neither. SaasToStore recommends one, and you choose in the build selector. On a paid build, both produce a signed APK and AAB.
Is converting a website to APK free?+
You can test it for free: the free plan gives one Android APK with the SaasToStore logo, to install on your own phone and see the result. The version you publish — your logo and name, a signed AAB for Google Play, plus iOS, desktop and Android TV — is SHIP, €39 one-time. The free test APK uses its own test key, so uninstall it before installing your store version.
Do I need a Google Play developer account?+
Only to publish on Google Play: it costs 25 USD once, on Google's side. You can build and install the APK without one. Personal developer accounts created after November 2023 must also run a closed test with 12 testers for 14 days before their first production release; organization accounts are exempt. The Samsung Galaxy Store and Amazon Appstore developer accounts are free.
What happens to my signing key?+
Each project gets its own key, generated at the first paid build. We keep it encrypted, include an encrypted backup with every build, and send its password by email once, with that first paid build — never on screen. Every update is signed with the same key, which is what Google Play requires to accept it.
My app is already on Google Play, made with another tool. Can I switch?+
Yes. On paid plans, your project has a 'My app is already on Google Play' section: it gives you the certificate to register as your new upload key in the Play Console, and lets you set the version code to continue from. Your users keep updating the same app.
How long does the build take?+
A few minutes. The free check of your URL takes about ten seconds, and the Android build itself usually finishes in one to five minutes.
How do I update the app after it is published?+
For content and features you do not: deploy to your website and the app shows the change the next time it opens, because it loads your live URL. You rebuild only when the app itself changes — its name, icon or native settings — or when Google raises the required target API level, once a year.
Does sign-in with Google work in the app?+
In the Trusted Web Activity build it works as it does in Chrome. In the WebView build, Google blocks sign-in inside web views (error disallowed_useragent), so the app opens it in the system browser and brings the user back signed in, after a one-time setup shown in your project.
Will my app pass Google Play review?+
Google judges each app, and nobody can promise approval. What we control is the build: a signed AAB, the current target API level, and no permissions your site does not use. What Google looks at beyond that — that the site is yours, that the app works, your privacy policy and data safety answers — is listed in the section above.
Turn your URL into an Android app
Paste your web address and get a signed APK — and, with a paid build, the AAB Google Play requires.
Build my Android app