Skip to main content
Bolt.new → Android

Turn Your Bolt.new App Into a Signed Android APK

Nothing to export. Bolt publishes your project for free at a bolt.host address — paste that address here and get a signed Android APK in about 60 seconds. No eas build, no Android Studio, no second codebase to keep in sync.

Written by the Free App Maker team at My Mind Studio · Last verified 26 August 2026

Yes — you can turn a Bolt.new app into an Android app without exporting your project or installing Android Studio. Publish it in Bolt to its free bolt.host address, paste that URL into Free App Maker, and a signed APK is ready in about 60 seconds. Building and previewing are free; downloading the signed APK is a one-time unlock, with the price shown before checkout.

Sources for the Bolt facts above: Bolt Support — Publish your project to a live website and Bolt Support — Expo for mobile apps, both checked 26 Aug 2026.

✓ Free to start, no account ✓ Signed APK in ~60 seconds ✓ Supabase backend keeps running server-side
bolt.new My Bolt App APK ✓
Builds in ~60 seconds
Signed APK — install anywhere
Free to start — no account needed
Android 5.0+ compatible
Zero coding required

An AI app builder that runs in the browser — and publishes to a free bolt.host address

Bolt.new is an AI development environment built on StackBlitz's WebContainers, described by StackBlitz as a browser-based runtime. You describe what you want, Bolt writes the code, and the preview runs in the same tab — no local toolchain involved.

When it is ready to share, Bolt's documentation says you can publish your project for free at a web address ending in bolt.host. New projects use Bolt hosting by default; you can publish to Netlify instead, and on a paid plan you can attach a custom domain you own. At publish time Bolt asks whether the site is visible to everyone on the web (public) or only to people you invite (private) — that choice matters here, because a private site has nothing for an app to load.

Bolt's Supabase integration documents three things your app gets: a hosted SQL database, authentication services, and edge functions — which Bolt notes are also used for talking to other services such as Stripe for payment handling. All of that runs over the internet, not on the device, which is exactly why a WebView wrapper leaves it intact. Free App Maker is a website to APK converter: it takes your published Bolt address and wraps it in a signed Android app.

$0
Bolt Free plan (Aug 2026)
$25/mo
Bolt Pro, the cheapest paid plan
60s
Avg APK build time

Bolt plan prices from Bolt pricing (Free $0 with a 300K daily / 1M monthly token limit; Pro $25 per month billed monthly; Teams $30 per month and member billed monthly), checked 26 Aug 2026 — Bolt can change these, so check the page before relying on it. A custom domain sits behind a paid plan, per Bolt Support — Publish your project, also checked 26 Aug 2026. The 60-second figure is our own average build time, measured on the Free App Maker build pipeline.

Bolt writes your React Native code. It does not hand you a signed Android build.

Bolt does have a mobile story: ask it for a mobile app and, in its own words, "it automatically uses Expo to make your app work on multiple platforms." What you get back is source code. Bolt's instructions are to download the code, open it in a code editor, and run eas build --platform android to produce something you can actually install or submit.

That is a real path, and for genuinely native UI it is the right one. It is also a second codebase, an Expo account, and a build pipeline. Expo's own pricing lists a Free tier at $0 with 15 Android and 15 iOS builds and one concurrency, and a Starter tier at $19 per month with $45 of build credit — reasonable, but it is another moving part next to the web app you already shipped.

Free App Maker aims at the other case: you already have a published Bolt app that works, and you want it on a home screen this afternoon. Paste the URL, get a signed APK, share the link. Being honest about the trade: this wraps your live site in an Android WebView, so the site has to stay online and publicly reachable, and native-only device APIs that a web page cannot reach — Bluetooth, NFC, background services — are not available to a WebView app either.

Sources: Bolt Support — Expo for mobile apps and Expo (EAS) pricing (Free $0 with 15 Android + 15 iOS builds; Starter $19/month), both checked 26 Aug 2026.

Convert Your Bolt App to Android in 3 Steps

No Android Studio. No Gradle. No Java. Just paste your URL and your APK is ready in about a minute.

Publish your Bolt project and copy the URL

In Bolt, open the Publish menu in the top-right corner and publish the project. Bolt's documentation describes the result as a free web address ending in bolt.host — so https://your-app.bolt.host, or a netlify.app address if you publish to Netlify, or your own domain on a paid plan. When Bolt asks, choose public rather than private: a private site is visible only to people you invite, and the app would have nothing to load.

Configure your Android app

Paste your URL into Free App Maker at freeappmaker.org. Enter a name for your Android app (this appears under the home screen icon) and your email address. Optionally upload a square 1024×1024 PNG icon — if you skip it, we generate a clean default icon automatically from your app name.

Download and install your APK

Free App Maker wraps your published Bolt URL into a WebView APK and signs it — your build is ready on the build screen in about 60 seconds. Building and previewing your app is free; downloading the signed APK is covered by a one-time unlock, and its exact price is always shown before you pay. Open the APK on any Android device, tap Install, and your Bolt app runs as a standalone app with its own home screen icon.

Source for the Bolt publishing steps and the bolt.host address in step 1: Bolt Support — Publish your project to a live website, checked 26 Aug 2026.

Ready to convert your Bolt.new app right now?

Start Free — Takes About 60 Seconds →

Who Converts Bolt.new Apps to Android?

From solo founders to enterprise teams, converting a Bolt app to Android opens distribution channels the web alone can't reach.

Startup Founders & Indie Hackers

You built your MVP in Bolt.new in a weekend. Converting it to an Android APK lets you distribute it to beta users directly — no Play Store listing required yet. Share the APK link in your Discord, Reddit post, or Product Hunt launch and get real feedback from real Android users immediately.

Agencies & Freelancers

Your client asked for an Android app on top of the web version you built in Bolt. Wrapping the published Bolt URL gives you something installable to demo in minutes rather than weeks — and because it loads the live site, the app reflects whatever you republished that morning. When the client is ready for a Play listing, that is a separate step: new Play submissions take an Android App Bundle, and you can get the AAB, the signing key, the graphics and the form answers through our Play Store Pack.

Students & Hackathon Teams

When a judging panel asks for an installable Android build alongside the web demo, wrapping your published Bolt project takes about a minute and gives the team something a judge can put on their own phone. Bolt's Expo route would give you a more native app, but it means exporting the code and running an EAS build — usually not what you want at 2am on the last night.

Internal Tools & Field Teams

Internal dashboards, field-worker tools, and stock-check screens built in Bolt.new can be handed out as an APK rather than a bookmark — including through a Mobile Device Management system if your organisation runs one. No Play listing is involved. The catch to plan for: the app loads your live Bolt URL, so it needs connectivity and a site that stays published.

What Works — and What to Test First

Free App Maker uses a full Android WebView, so most modern web features behave much the way they do in Chrome. Here's a practical breakdown for Bolt.new projects.

✅ Generally works

  • React, Vue, and Svelte frontends built in Bolt — they are ordinary web pages by the time they reach the phone
  • Supabase email-and-password logins and magic links
  • Supabase Postgres queries and Realtime subscriptions over wss://
  • Supabase edge functions, and the REST or GraphQL APIs your app calls
  • Tailwind CSS, shadcn/ui, and CSS animations
  • File uploads and downloads
  • Responsive layouts built for mobile viewports
  • Anything you republish in Bolt — the app loads the live URL, so no rebuild is needed

⚠️ Test before sharing widely

  • Sign in with Google. Google's developer blog states that OAuth 2.0 authorization requests from embedded webviews are blocked, and points developers to the system browser or an Android Custom Tab instead. Plan for the hand-off, test it on a real device, and consider keeping an email login as well
  • Stripe checkout and other payment redirects — these leave your page and come back; place a test payment on a real device before you share the app
  • WebSocket endpoints on plain ws:// — Android disables cleartext support by default from Android 9 (API level 28), so serve sockets over wss://
  • A Bolt project published as private — it is visible only to people you invite, so the app has nothing to load; publish it public first
  • Camera, microphone and location — the app shows the standard Android permission prompt the first time your site asks for them; your site must be served over https for the browser engine to allow it. Test on a real device
  • Deep links out to other apps (maps, dialer) — test on a real device
  • PWA install prompts — do not rely on them appearing inside the app
  • Heavy Canvas or WebGL scenes — test on mid-range devices for performance

Sources for the three cited rows above: Google Developers Blog — security changes to Google's OAuth 2.0 endpoint in embedded webviews, Android Developers — Network security configuration, and Bolt Support — Publish your project to a live website, all checked 26 Aug 2026.

Not sure if your Bolt app is compatible? Run it through our free WebView Compatibility Checker before you build. And this flow isn't Bolt-only — any live page can be wrapped, as our URL to APK guide shows.

Free App Maker vs. Your Alternatives

Free App Maker is a free website to APK converter: paste your live Bolt.new URL on the homepage and a signed APK comes back in about a minute.

These are the four routes Bolt builders actually weigh up when they want an Android app. Prices below come from each vendor's own pricing page and were checked on 26 August 2026.

What you're comparing Free App Maker ✓ Bolt + Expo EAS Build Capacitor (self-build) Median.co
What you start from Your published bolt.host URL Bolt's exported React Native code Your app's built web assets Your live URL
Cost (as of 26 Aug 2026) Free to build — one-time unlock to download, price shown before checkout EAS Free $0 (15 Android builds); Starter $19/mo $0 — MIT-licensed, plus your own time Free tier watermarked; Starter $229 one-time licence fee, then $179/yr
Second codebase to maintain None ✗ Yes — React Native alongside your web app A native shell wrapping your build None
Android Studio / SDK on your machine ✓ Not needed Not needed — EAS Build is a hosted service ✗ Required — Android Studio + Android SDK Not needed
Republish in Bolt — does the app change? ✓ Yes, next time it loads that page ✗ No — re-export and rebuild ✗ No — rebuild the shell ✓ Yes — it loads your live URL too
Native device APIs (Bluetooth, NFC, background work) ✗ No — web capabilities only ✓ Yes — genuinely native Via Capacitor plugins Via their plugin library
Signed build handed to you ✓ Signed APK Yes, once EAS credentials are set up — but Android builds default to an AAB, which Expo notes can't be installed straight onto a device; an APK needs its own eas.json profile You sign it yourself ✓ Yes
Path to a Google Play listing AAB included in the Play Store Pack, with graphics and form answers EAS builds an AAB by default Build an AAB yourself Their own publishing workflow

Competitor pricing checked 26 August 2026 against each vendor's own pricing page: Expo (EAS) — Free $0 with 15 Android and 15 iOS builds and 1 concurrency, Starter $19/month with $45 of build credit, with EAS Build documented as a hosted service that defaults to an AAB on Android; Median.co — Free $0 with a "Powered by Median.co" watermark, Starter a $229 one-time licence activation fee then $179/yr from month 12 (median.co blocks automated fetching, so this row was read in a real browser on 26 Aug 2026); Capacitor — MIT-licensed and free, with Android Studio and the Android SDK required locally. Prices change — check each vendor before relying on a figure here. New Google Play listings require an Android App Bundle rather than an APK, per Android Developers.

6 Reasons Bolt Builders Choose Free App Maker

Beyond the speed, there are real technical and strategic advantages to converting your Bolt.new app with us.

Republish in Bolt — no new APK needed

Because the APK loads your live Bolt URL at runtime, a screen you change and republish shows up the next time the app loads that page — subject to any caching in front of it. No store review, no new build, no forced update prompt for users. On the Expo route the same change means re-exporting the code and running another EAS build.

Signed APK — install and share directly

Each APK we generate is digitally signed, so Android will install it once the device allows installs from your source. Android still shows its standard unknown-source prompt for any app that didn't come from Play. Share it as a direct download link, in your Discord, or with beta testers — no store listing required.

From published URL to signed APK in about 60 seconds

Setting up a native toolchain is a detour before you ever see a first build — Capacitor's own docs require Android Studio and an Android SDK installation on your machine before you can compile anything. Free App Maker's build pipeline runs server-side and delivers your APK in about 60 seconds, so testing a new app name or icon takes minutes.

Your launcher icon at every Android density

Android's own guidance puts launcher icons in a mipmap directory per density bucket — 48×48 at mdpi, then 72, 96, 144 and 192 px as the density rises. Free App Maker generates those from a single 1024×1024 PNG. No Figma, no Photoshop, no manual export. We generate a default icon if you don't have one.

Unbranded once unlocked, yours to distribute

The unlock that lets you download the signed APK also removes the small Free App Maker splash screen, so what you hand out carries your name rather than ours. Worth knowing when you compare: Median.co's own pricing page shows a "Powered by Median.co" watermark on its free tier, removed by the $229 Starter licence.

Works on Android 5.0 and above

Our APKs run on Android 5.0 (Lollipop) and above. The engine that renders your Bolt app is the Android System WebView, which the Chromium project describes as an updatable system component since Lollipop rather than something frozen into the OS image — so on devices that still receive those updates, modern web features are generally there.

Sources for the cited cards above: Android Developers — Support different pixel densities (launcher icon sizes per density bucket), Chromium — WebView providers (WebView as an updatable system component), Capacitor — Environment setup, and Median.co pricing, all checked 26 Aug 2026.

Frequently Asked Questions

Everything you need to know about converting a Bolt.new app to an Android APK.

Does Free App Maker work with Bolt.new apps?
Yes — with any Bolt project that is published and publicly reachable. Bolt's own documentation says you can publish a project for free at a web address ending in bolt.host, and you can also publish to Netlify or attach a custom domain on a paid plan. Paste whichever address is live and Free App Maker wraps it in an Android WebView app. One thing to check first: when you publish, Bolt asks whether the site should be visible to everyone on the web (public) or only to your team and people you invite (private). A private site has nothing for the app to load.

Source: Bolt Support — Publish your project to a live website, checked 26 Aug 2026.

My Bolt project is published as Private — will the Android app work?
No. Bolt lets you choose at publish time whether your site is visible to everyone on the web or only to your team and people you invite. The APK loads your live URL over the internet with no special credentials, so a private site will not render inside it. Switch the project to public before you build, or point the app at a public custom domain instead.

Source: Bolt Support — Publish your project to a live website, checked 26 Aug 2026.

Can I point the app at my own domain instead of the bolt.host address?
Yes, if your Bolt plan allows it. Bolt's documentation says that on a paid plan you can attach a custom domain you own, or buy a domain through Bolt; otherwise your project stays on the free bolt.host address. Free App Maker treats either the same way, because it only needs an address that is publicly reachable. One practical note: the URL is baked into the APK when it is built, so if you move to your own domain later, rebuild the app with the new address and share the new APK.

Source: Bolt Support — Publish your project to a live website, checked 26 Aug 2026. Bolt's pricing page listed Pro at $25 per month billed monthly on the same date; plans change, so check before relying on it.

Should I publish to Bolt hosting or to Netlify?
Either works, because Free App Maker only needs a public address. Bolt's documentation says all new projects created in Bolt are published using Bolt hosting by default, though you can choose to publish new projects to Netlify instead, and that when you first publish your app, Bolt automatically creates a random netlify.app URL name for you. Pick whichever address you plan to keep live and paste that one — if you switch hosts later, rebuild the APK with the new URL.

Source: Bolt Support — Netlify integration, checked 26 Aug 2026.

Bolt can already build mobile apps with Expo — why use this instead?
They solve different problems. Bolt's Expo integration writes React Native code for you, and Bolt's documentation then tells you to download that code, open it in a code editor, and run eas build --platform android to produce something installable. That means an Expo account, an EAS build pipeline, and a second codebase to maintain alongside your web app. Free App Maker takes the web app you already published and wraps it — no export, no second codebase, no native toolchain. If you want true native UI and native device APIs, the Expo path is the right one; if you want your existing Bolt app on a home screen today, this is faster.

Source: Bolt Support — Expo for mobile apps, checked 26 Aug 2026.

Will my Bolt app's Supabase backend keep working in the Android APK?
In most cases, yes. Bolt's Supabase integration gives your project a hosted SQL database, authentication services, and edge functions — all of which run over the internet rather than on the phone. The APK loads the same live URL your browser does, so those calls behave much as they do in mobile Chrome. Email and password logins are the straightforward case; third-party sign-in buttons are the ones to test, for the reason described in the Google sign-in answer below.

Source: Bolt Support — Supabase integration, checked 26 Aug 2026.

Does the Android app update when I republish in Bolt.new?
Yes. The APK loads your live Bolt URL at runtime, so a screen you change and republish in Bolt shows up the next time the app loads that page — subject to any caching or CDN in front of it. No new build and no new APK are required, and your users are not prompted to update.
Does Google sign-in work inside the Android WebView?
Not inside the WebView itself. Google's developer blog is explicit that OAuth 2.0 authorization requests made from embedded webviews are blocked, and Google's recommended approach on Android is to hand the sign-in off to the system browser or an Android Custom Tab instead. Email and password logins and magic links are not affected. If your Bolt app relies on a Sign in with Google button, test that flow on a real device before you share the app, and consider offering an email login alongside it.

Source: Google Developers Blog — security changes to Google's OAuth 2.0 authorization endpoint in embedded webviews, checked 26 Aug 2026.

My Bolt app uses WebSockets for real-time features. Will they work?
Secure WebSocket connections over wss:// are the ones to rely on. Android's own security documentation states that starting with Android 9 (API level 28), cleartext support is disabled by default — so an unencrypted ws:// endpoint is the case that fails. Hosted services such as Supabase Realtime already use wss://. If you run your own socket server, make sure it is served over TLS, and test a live session on a real device.

Source: Android Developers — Network security configuration, checked 26 Aug 2026.

What is the minimum Android version the APK supports?
APKs built by Free App Maker run on Android 5.0 (API level 21) and above. The rendering engine that runs your Bolt app is the Android System WebView, which the Chromium project describes as an updatable system component since Android Lollipop rather than something frozen into the OS image — so on devices that still receive those updates, modern web features are generally available. Older or unmaintained devices are worth testing if your audience uses them.

Source: Chromium — WebView providers, checked 26 Aug 2026.

Can I upload the APK to Google Play Store?
The APK you receive is built for direct installation and testing — install it on any Android device or share the download link with your users. Google Play is a separate path: Google's developer documentation states that from August 2021, new apps are required to publish with the Android App Bundle on Google Play, so an APK is not the format a new listing takes. If a Play listing is your goal, the files you need to publish your app on Google Play comes in one payment — the AAB, your signing key, a hosted privacy policy, the graphics and the form answers.

Source: Android Developers — About Android App Bundles, checked 26 Aug 2026.

Is this completely free? Any hidden costs?
It is free to start — no account, no credit card, no subscription. You paste a URL, enter your email, and your app is built free. Downloading the signed APK is covered by a one-time unlock — priced by country and always shown before checkout — which also removes the small Free App Maker splash screen from every app you build.

Your Bolt.new App Deserves to Be on Android

About 60 seconds. No export, no coding. Free to start.

Convert My Bolt App — Free to Start →