The best way to turn a website into an app depends on whether you need an app store listing. If you only want an icon on the home screen, install the site as a web app from the browser for free. If you need Google Play, wrap a PWA in a Trusted Web Activity or package the site in a WebView app. For the App Store, plan on Capacitor or native work, because Apple rejects plain wrappers.
The four ways to turn a website into an app
There are four common routes, and they differ mainly in who renders the page and how much native code sits around it. Here they are from least to most work.
- Install it from the browser. Chrome Help says you can use web apps “to have a website work as an app”. On some sites you just select Install at the top right of the address bar.
- Make it a PWA and wrap it. A PWA adds a manifest and offline support to your site. web.dev says you can wrap it in a launcher and upload it to stores such as Google Play.
- Use a WebView wrapper. A small native app shows your pages inside an Android WebView. This is what most “website to app” converters produce.
- Rebuild with Capacitor or native code. Capacitor is “a cross-platform native runtime” that runs your web code inside native iOS and Android projects, with plugins for device features.
Which route fits you: a decision table
The right route comes from three questions: do you need a store listing, which stores, and do you own the site. The table puts the store rules and fees next to each option, which the vendor guides at the top of Google mostly leave out.
| Route | Store listing | Owns the site? | Skill needed | Main risk |
|---|---|---|---|---|
| Browser install | None | No | None | Users must find your site first |
| PWA in a Trusted Web Activity | Google Play | Yes, verified | Some web and CLI work | Site must meet PWA install rules |
| WebView wrapper | Google Play, or sideloaded APK | Needs permission | Low with a builder | Minimum functionality rejection |
| Capacitor or native | Google Play and App Store | Usually yes | Real development | Time and maintenance |
Fees apply only once you list. Google Play charges a US$25 one-time registration fee. The Apple Developer Program costs $99 a year. New personal Play accounts must also run a closed test “with a minimum of 12 testers who have been opted in continuously for at least 14 days” before going live.
Route 1: install the website as a web app
Installing a website as a web app is the fastest option and needs no store at all. Open the site in Chrome, look for Install in the address bar, and follow the prompts. The site then opens in its own window with an icon.
It suits internal tools, a team dashboard, or a booking page your regular customers already visit. Strangers won’t find it, because there’s no listing to search.
Route 2: a PWA in a Trusted Web Activity
A Trusted Web Activity (TWA) lets an Android app open your PWA full screen in the user’s browser. Chrome’s TWA overview says “the app and the site it opens are expected to come from the same developer.” You prove that by hosting a verification file on your domain.
The catch is the starting point. A TWA needs the same install requirements as Add to Home Screen, so your site must already be a working PWA. web.dev’s advice is to “Start small!” with a basic manifest file and a simple offline page. I covered the full process in publishing a PWA on Google Play.
Route 3: wrap the site in a WebView app
A WebView app is a native Android app whose main screen is a web page. Android’s WebView guide notes that a WebView doesn’t include browser features such as navigation controls or an address bar, so the app has to supply them.
This is the route most people mean when they ask how to turn a website into an app without coding. It works for sites you can’t turn into a PWA, and for self-contained HTML you want offline inside the APK. If you’re unsure between this and route 2, PWA vs WebView app compares them line by line.
WebToAPK Free is one builder for this route. It runs in your browser, needs no account, and produces a signed APK and an AAB without adding ads or a watermark. The limits: it makes Android apps only (Android 8.0 or newer), with no iOS output and no push notifications. The website to APK guide walks through a build.
Route 4: Capacitor or a native rebuild
Capacitor or a native rebuild is the route for an app that must do things the website can’t. Capacitor’s docs put it simply: “If it works in the browser, it probably works in a mobile app when using Capacitor.” You keep your web code and add native plugins for the camera, files or notifications.
The cost is that you now maintain native projects for each platform. You need Android Studio, and for iOS a Mac with Xcode. For a small business with one developer, that’s a real commitment.
Why app stores reject plain website apps
App stores reject website apps that add nothing beyond the website, and both stores say so in writing. Apple’s App Review Guidelines say under 4.2 that an app should include features, content and UI that elevate it beyond a repackaged website.
Apple adds two more traps:
- 4.2.2: apps shouldn’t mainly be marketing materials, web clippings or a collection of links.
- 4.2.6: apps made from a commercial template or app generation service are rejected unless the content provider submits them.
Google is less strict about wrappers but has its own lines. Its minimum functionality policy blocks “Apps that are static without app-specific functionalities”, and apps that “crash, force close, freeze, or otherwise function abnormally.” The spam policy bans apps that “provide a webview of a website without permission from the website owner or administrator.”
Say a restaurant wraps its menu page and submits it to both stores. Google may accept it if it loads cleanly. Apple will likely cite 4.2, because the reviewer sees exactly what Safari shows. The details are in why Google Play rejects WebView apps and turning a website into an iOS app.
Common mistakes when you make a website into an app
Most failed website apps fail for the same few reasons, and none of them are about code.
- Wrapping a site you don’t own. Google’s spam policy covers this directly, and no feature list fixes it.
- No test login for reviewers. If the app opens on a login form, give reviewers working test credentials.
- Assuming the whole app updates itself. In a WebView app, live site content updates on its own, but the name, icon and navigation change only with a new build.
- Offline. A live website needs a connection. Only bundled HTML works with no signal.
- The testing period. Twelve testers for fourteen days adds two weeks to a new personal Play account.
My take on the best route
My take: start with the cheapest route that meets your real goal. If you don’t need a listing, the browser install is enough. If you need Android and own the site, a TWA keeps everything in Chrome; if the site can’t be a PWA, a WebView wrapper is the practical choice. Only pay for Capacitor or native work when you need the App Store or device features.
The wrapper approach has one hard limit: it can’t make a weak mobile site good. A site that’s slow or awkward on a phone makes an app that’s slow or awkward. Fix the mobile site first, then package it. The cost of publishing on Google Play is low enough that this order costs you little.
FAQ
Can I turn a website into an app for free?
Yes. Installing the site as a web app from Chrome costs nothing, and free WebView builders can make an Android APK. Store listings cost extra: Google Play charges a US$25 one-time fee and Apple charges $99 a year.
Will Apple accept a website wrapped in an app?
Only if the app offers more than the website. Guideline 4.2 asks for features, content and UI that elevate the app beyond a repackaged website, and 4.2.6 rejects template-generated apps not submitted by the content owner.
Do I need to own the website to make an app of it?
For Google Play, yes in practice. Google’s spam policy bans apps that provide a webview of a website without permission from the website owner or administrator. A Trusted Web Activity also expects the app and site to come from the same developer.
Is a PWA the same as an app?
Not quite. web.dev says Progressive Web Apps are still websites, with enhanced features and capabilities. People can install one from the browser, and you can wrap it to list it in an app store.
Sources
- Use web apps (Google Chrome Help)
- Progressive Web Apps: first steps (web.dev)
- Trusted Web Activity overview (Chrome for Developers)
- Build web apps in WebView (Android Developers)
- Capacitor documentation
- App Review Guidelines (Apple Developer)
- Functionality, Content, and User Experience (Play Console Help)
- Spam policy (Play Console Help)
- Registration fee and account setup (Play Console Help)
- App testing requirements for new personal developer accounts (Play Console Help)
- Apple Developer Program