1. Home
  2. Guides
  3. Convert a website URL to APK

Guide

How to convert a website URL to APK

If your site is already online, the app does not need a copy of it. A URL app opens your live site inside a native shell, so every change you publish appears in the app straight away.

Updated 2026-10-183 min readBy the APK Maker team
Short answerOpen Website to App, paste your website's address, set the name, icon and splash screen, and build. The APK opens your live site in a WebView, so content stays in sync automatically. It needs an internet connection and shows an offline screen without one.

How a URL app works

The APK contains a native Android shell and your address. When someone opens the app it loads your site in a WebView — Android's built-in browser engine — without the browser's address bar and tabs. Logins, carts and forms work the same as on the mobile web, and cookies persist between launches.

Make your site app-ready

  • HTTPS — Android blocks plain HTTP pages by default.
  • Responsive layout — the app shows your mobile site.
  • Fast first load — the first screen is what reviewers and users judge.
  • No "download our app" banners — hide them when the visitor is already in the app.

Convert it

  1. Install Website to App from Google Play.
  2. Paste your full address, for example https://shop.example.com.
  3. Set the app name, icon, theme colour and splash screen.
  4. Choose a package name and build.
  5. Install the APK and test the pages people use most.

Make it feel like an app, not a bookmark

A wrapper that only shows a website gives users little reason to install it — and Google Play's policies discourage apps whose only purpose is to display a website. Add things a browser tab cannot do:

  • Push notifications for orders, posts or reminders (Pro).
  • A bottom tab bar to your key sections (Pro).
  • An offline screen instead of a browser error.
  • App Links, so links to your domain open in the app — generate the file with the assetlinks.json generator.

Works with any platform

WordPress, WooCommerce, Shopify, Wix, Squarespace, Webflow, Blogger, Ghost, custom web apps — if it opens in Chrome on a phone, it can be an app.

Test these before you share the app

  • "Sign in with Google". Google blocks its sign-in page inside embedded WebViews (error disallowed_useragent). Offer email login, or make sure your builder opens Google sign-in in a browser tab.
  • File and photo uploads on forms — profile pictures, documents.
  • Payments — redirects to payment pages and back to your site.
  • Special links — tel:, mailto:, WhatsApp and maps links should open the right app.
  • The back button — it should go back a page, and only close the app on the home screen.
  • Pages on other domains — decide whether they open inside the app or in the browser.

Make the first launch fast

A URL app is only as fast as your website on a phone. Check your mobile score in PageSpeed Insights, lazy-load images below the fold, defer third-party scripts, and cache static assets with long Cache-Control headers — the WebView keeps its cache between launches, so the second open is much faster than the first.

When to build from files instead

If your site is static (a portfolio, menu, brochure or game) and you want it to work offline, export it and use the ZIP to APK route. You lose instant updates but gain offline use and instant loading.

Make your APK now — free

No Android Studio, no code, no watermark. Pick what you are starting from:

Frequently asked questions

Does a website-to-APK app update automatically?

Yes. The app loads your live site, so content changes appear immediately. You only rebuild to change the app's name, icon or settings.

Will logins and shopping carts work?

Yes. The WebView keeps cookies and local storage between launches, so sessions and carts work like the mobile web.

Can Google Play reject a website app?

It can if the app only mirrors a website. Adding push notifications, native navigation and an offline experience makes approval much more likely.