Turn Any Link Into an Android App

Not every project is a full business website. Sometimes what you have is a single link — a booking page, a dashboard, a course, a form, a Notion page somebody shared with you, an internal tool — and what you want is that one thing, as an installable Android app, without wrapping an entire site around it.

Last verified 26 August 2026 · written and maintained by My Mind Studio.

What Converting a Link to an APK Actually Means

It is worth being precise, because the phrase means two very different things to two different groups of people, and only one of them is what this page does.

What it means here. An APK is an Android app package. When you convert a link to an APK, a small Android app is built whose entire job is to open one URL inside a component called a WebView — Android's built-in browser engine, embedded in your app rather than in Chrome. The app carries your name and your icon. When someone taps it, the WebView loads your link full-screen, without a browser address bar. Android keeps that engine current on its own: WebView updates arrive through the Google Play Store, separately from the Android version on the phone, so the rendering engine inside your app does not freeze at the version that shipped with the handset.

Source: Android Developers — WebView Beta program, checked 26 Aug 2026. Android ships WebView as a separately updatable component distributed through Google Play, with a Beta track available roughly four weeks ahead of stable.

What it does not mean. Two things, and both come up constantly in this search:

• It is not downloading or repackaging somebody else's app. A lot of people arrive at "link to APK" hoping to paste a Play Store listing URL and receive that app's installer. That is not what happens, and it is not something we do — the result of pasting a store listing URL would simply be a WebView app that shows the listing page. If you want an existing app, install it from the store it is published in.
• It cannot bundle a site that needs a login you do not control. A WebView is a browser without the browser furniture, so it starts logged out, the way a fresh incognito window does. If the page you want only renders content after an authenticated session, your app will show the sign-in screen, not the content. Where the site's own login form works inside a plain browser it will usually work inside the WebView too — but a login you cannot test is a login you should preview before you commit.

Which Links Work, Which Need Testing, and Which Cannot

This is the part most "URL to APK" pages skip. The honest answer has three tiers.

Links that convert cleanly

• A public page on a domain you own — a landing page, a documentation site, a knowledge base, a portfolio.
• A published Notion site. Notion's own help states that when you publish a page, anyone on the web can view it, and that the published site updates automatically as you edit the underlying page — which is precisely the behaviour a WebView wrapper wants.
• A no-code app's public URL — the deployed link from a builder, rather than the editor or preview URL. Editor URLs are behind that platform's own login and will not survive the trip into an app.
• A booking or scheduling page that is designed to be opened by strangers, since it is already built to work without an account.
• A public form or survey — these render and submit inside a WebView the same way they do in a mobile browser.

Source: Notion Help — Public pages and web publishing, checked 26 Aug 2026 (“Anyone on the web can view it”; the site updates as the page changes).

Links that need testing before you build

• Google Drive and Google Docs share links. These can work, with a caveat worth understanding. Google's sharing settings distinguish “Restricted”, where only people with access can open the file, from “Anyone with the link”, which Google describes as usable without signing in to a Google Account. A file set to “Anyone with the link” is the version that has a chance inside a WebView. A restricted file will ask for a Google sign-in — and that sign-in is the problem described in the next tier.
• Single-page apps. Framework-driven sites that rewrite the URL as you navigate generally render fine, but their history handling and the Android back button deserve a look on a real device before you ship the app to anyone.
• Pages that lean on hardware — camera, microphone, geolocation, file pickers. These are permission-gated inside a WebView and behave differently from a desktop browser tab.
• Pages that open payment or identity flows in a new window. A pop-up that a browser would open as a tab has nowhere obvious to go inside a single-page app shell.

Source: Google Drive Help — Share files from Google Drive, checked 26 Aug 2026 (“Anyone with the link” vs “Restricted” general access).

Rather than guess at any of this, run the link through our free WebView compatibility checker first, then build and preview the app before you unlock a download.

Links that cannot work

• localhost, 127.0.0.1, and private-network addresses such as 192.168.x.x or 10.x.x.x. This one is worth stating plainly: the phone is a different machine on a different network, so those addresses resolve to the phone itself or to nothing at all. A dev server on your laptop is not reachable from a stranger's handset. Put the page on a public host — or, for a quick test, a tunnelling service that gives it a public HTTPS address — and convert that URL instead.
• Plain http:// links, in most cases. Android's network security documentation states that from Android 9 (API level 28), cleartext support is disabled by default. An app has to opt in to unencrypted traffic. If your link is HTTP-only, the sturdier fix is an HTTPS certificate on the host, which most hosting platforms now issue free.
• Anything gated behind a Google account sign-in inside the app. Google's OAuth 2.0 policies state that a developer must not direct a Google OAuth 2.0 authorization request to an embedded user-agent under the developer's control — embedded webviews included. So a page whose only door is a “Sign in with Google” button is a page that will not get past its own front door inside a WebView wrapper. This is a Google policy decision, not a limitation we can engineer around, and any converter claiming otherwise is worth a second look.
• Intranet pages and VPN-only tools — same reason as localhost. If the phone cannot reach the address on its own connection, no wrapper changes that.

Sources: Android Developers — Network security configuration (“Starting with Android 9 (API level 28), cleartext support is disabled by default”) and Google Identity — OAuth 2.0 Policies, both checked 26 Aug 2026.

How to Convert a Link to an APK, Step by Step

1. Check the link opens on a phone. Open it in your phone's browser while connected to mobile data, not your home Wi-Fi. If it loads there, it can load inside an app; if it does not, fix that first.
2. Paste the link into the builder. Free App Maker is a website to APK converter that runs in the browser — no Android Studio, no SDK, no developer account.
3. Name the app and add an icon. The name is what sits under the icon on the home screen. A square PNG works best for the icon; our free icon generator produces the sizes Android expects.
4. Preview it, then download the signed APK. Building and previewing are free. Downloading the signed APK is a one-time unlock, priced by country, with the price shown before checkout.

One build, not a subscription. There is no monthly bill here, and no account to cancel. The unlock is per build, and its price is on screen before you are asked to pay anything.

What Happens to the Link After Conversion

This is the part that surprises people, and it is the strongest argument for the WebView approach: the app shows the live page. You are not baking a snapshot into the APK. You are shipping a window onto a URL.

The practical consequence is that editing the page updates the app, with no rebuild, no new APK, and nothing for your users to reinstall. Fix a typo on the booking page at nine in the morning and anyone who opens the app at nine-oh-one sees the fix. Add a section to the Notion site and it appears. Change the whole design and the app changes with it.

The trade-off is the mirror image of that benefit, and it is fair to state it: if the page goes down, the app shows what a browser would show. If you move the content to a different URL, the app still points at the old one, and that does need a new build. So the URL you convert is worth choosing as a stable address rather than a temporary preview link.

Installing the APK on an Android Phone

Installing an APK that did not come from an app store takes two extra taps compared with a Play Store install, and it is better to know about both in advance than to meet them mid-demo in front of a client.

1. The “install unknown apps” permission. Android used to have a single device-wide “Allow unknown sources” switch. Since Android 8.0 it is per-app: Android's own documentation records that the “Allow unknown sources” system setting was removed and that the “Install unknown apps” permission now manages installs from unknown sources. In practice, whichever app is handing over the file — usually Chrome or the Files app — is the one that asks. Tapping through the prompt grants it to that app, and the phone remembers.

Source: Android Developers — Android 8.0 behaviour changes, checked 26 Aug 2026 (“The Allow unknown sources system setting has been removed; in its place, the Install unknown apps permission manages unknown app installs from unknown sources”).

2. The Play Protect caution screen. Be ready for this one, because it is the moment people email us about. Google Play Protect scans apps regardless of where they came from, and Google's support documentation states that it checks the device for potentially harmful apps from other sources, that it may ask you to send unknown apps to Google, and that it may prevent installation of an app that is unverified and uses sensitive device permissions commonly targeted by scammers. For a WebView app built from your own link, what you will typically see is a caution screen noting that the developer is not recognised — because the signing certificate belongs to a new developer rather than an established one. There is usually a “More details” or “Install anyway” path underneath it.

We are not going to pretend that screen is not there or that a converter can make it disappear. It is a function of the app being distributed outside a store, and it is the same screen a hand-built Android Studio APK produces on its first install. What removes it in the long run is distributing through a store, which is the next section.

Source: Google Play Help — Use Google Play Protect to help keep apps safe, checked 26 Aug 2026.

APK vs AAB, and What Google Play Requires

An APK installs directly on a phone. An AAB — an Android App Bundle — is a publishing format: you upload it to Google Play, and Google generates the per-device APKs from it. They are not interchangeable, and the difference decides how you can distribute what you just built.

Google's own App Bundle documentation states that from August 2021, new apps are required to publish with the Android App Bundle on Google Play. So the signed APK from a link conversion is the right file for installing on a phone, for sending to a client, for a QR code on a poster, for an internal rollout, or for stores that accept APKs — and it is not the file Google Play accepts for a new submission. We would rather say that here than have you discover it at the upload screen.

Source: Android Developers — About Android App Bundles, checked 26 Aug 2026 (“From August 2021, new apps are required to publish with the Android App Bundle on Google Play”).

The full comparison — what each format contains, why Google made the change, and what it means for download size — is in APK vs AAB explained. If your goal is a listing on Google Play rather than a link you hand out yourself, the Play Store Pack covers the AAB and the surrounding submission requirements.

Notes by Where the Link Came From

“Convert a link to an APK” is the same operation regardless of what generated the link, but the practical gotchas differ by platform — mainly around which URL is the public one. These guides go deeper on each:

• Google Sites to Android — for a published Google Sites URL, including the difference between the draft and published addresses.
• Bolt.new to Android — deployed project URLs from Bolt, rather than the in-editor preview.
• Lovable to Android — publishing first, then converting the live link.
• Framer to Android — Framer sites and the custom-domain question.

If your link is a whole business website rather than a single page, the main conversion guide covers that end to end.

Why Turn a Single Link Into an App

A link saved as a bookmark gets forgotten. The same link as an icon on the home screen gets opened. For a tool your team uses daily, a client-facing booking page, or a course your students return to, that difference in friction is often the whole reason to do this. An icon is also something you can hand over — “install this” is a shorter conversation than “bookmark this URL and remember where you put it”.

Frequently Asked Questions

In Short

If what you have is one link rather than a full website, this is exactly the case it covers. Paste the URL, check the preview on a real phone, and you get a signed, installable APK — a live window onto your page, sitting on the home screen with your name and icon on it.