WEBFLOW → PLAY STORE
Publish your Webflow site to the Google Play Store
- Free test
- No account needed
- Result in 10s
- Your code stays yours
Updated November 10, 2026
Webflow publishes a site — Google Play wants a bundle
Webflow gives you world-class hosting, a CMS and pixel-perfect responsive design, published to webflow.io or your domain. But the Play Store doesn't take a URL — it needs a signed Android App Bundle, a keystore and a store listing. And since Webflow sites ship no web manifest, a TWA-only tool won't build them. SaasToStore bridges that with a Capacitor native build, so any published Webflow URL becomes a real Android app.
Two Android builds for a Webflow site
Most website-to-Android converters only produce a Trusted Web Activity (TWA): a very small app that opens your site in Chrome's engine. A TWA needs a web manifest on the site, plus an assetlinks.json file on the domain to hide the address bar; a service worker helps offline but isn't required. Webflow gives you no manifest out of the box, so a Webflow URL fails the PWA check of a TWA-only tool. It's the most common reason a Webflow site never reaches Google Play. SaasToStore has two Android builds, and one of them doesn't need a PWA at all.
Android Build (Native) — the one for Webflow
- Your live Webflow site inside a native Android shell
- Any Webflow URL on HTTPS: CMS, Commerce, heavy Interactions
- Nothing to add to your Webflow project: no manifest, no service worker
- Takes native tabs and menus, and plugins such as push notifications and biometric unlock
Android Build (Web) — TWA
- A very small app that opens your site in Chrome
- Only once you add a web manifest through custom code
- Hiding the address bar takes an assetlinks.json file served by your site
- No native navigation and no plugins
With a paid build, both give you a signed .aab for Google Play and an .apk, and the same signed app also goes to the Amazon Appstore and the Samsung Galaxy Store. The free test build is an .apk with the SaasToStore logo: it shows your Webflow site as an app on your own phone, it isn't a file to publish.
From Webflow to the Play Store, step by step
- 01 ·
Publish in the Webflow Designer
Click Publish. Use your webflow.io staging URL or, ideally, your custom domain on a paid Site Plan for the cleanest app identity.
- 02 ·
Paste it into SaasToStore
We read your favicon, title and Open Graph data; you can override the icon and name. You choose the build: we recommend the Capacitor build, which needs no manifest and no service worker.
- 03 ·
We build & sign the .aab
A signed bundle with an encrypted RSA-2048 keystore, kept for your future updates.
- 04 ·
Get the files for the stores
A paid build delivers the signed files each store asks for: the .aab for Google Play. Each store sets its own review time.
Doing it yourself vs with SaasToStore
A typical Webflow launch
A creator runs a paid membership and course site on Webflow with Memberstack for auth and the Webflow CMS for lessons. Members want a home-screen app for daily access. They publish, paste their domain into SaasToStore, and get a signed app for Google Play the same day — then add push notifications with SHIP to bring members back. New lessons published in Webflow show up instantly in the app.
What carries over into your Webflow Android app
The app renders your live site, so what you built in Webflow works as it does in mobile Chrome:
- Every page, layout and responsive breakpoint
- Webflow Interactions, scroll-triggered animations and Lottie
- CMS collections: blog posts, products, dynamic pages
- Webflow Forms and their integrations (Zapier, Make…)
- Webflow Commerce pages and checkout
- Custom fonts and custom code embeds
Pages on your domain and its subdomains stay inside the app. A link to another domain, such as a payment page, a booking calendar or a sign-in provider, opens in the phone's browser, unless you add that domain to Extra domains in your project before the build.
Webflow tips before you build
- Publish before you build. The app opens your live site, so publish your latest changes in Webflow first. After launch, everything you publish appears in the app without a new build.
- Use your production domain. Your custom domain is the address the app opens from then on. Moving from webflow.io to your own domain later means a new build.
- Add native features without touching Webflow. With the Native build, you can add a native tab bar, header or side menu, push notifications, biometric unlock and deep links. They live in the app, not in your Webflow project, and reach your users with the next build.
What you get for your Webflow site
- Signed Android App Bundle (.aab) + APK for Google Play
- Capacitor build — works without a Webflow service worker
- Your CMS, forms, interactions and custom code keep working live
- Encrypted keystore kept for seamless updates
- Optional AI-generated Play Store icon, screenshots and description
- Same URL also builds Windows, macOS and Linux desktop apps
- One-time pricing: €39 for every platform — no monthly lock-in
On another tool too? See Lovable, Bubble, Framer and any website → APK.
Frequently asked questions
Where do I get the URL to paste from Webflow?+
Hit Publish in the Webflow Designer. Your site goes live at yoursite.webflow.io, or your custom domain if you're on a paid Site Plan. Paste that public HTTPS URL into SaasToStore.
Does a Webflow site need a manifest or service worker?+
Webflow sites don't ship a manifest or service worker by default. No problem — you choose the build, and the Capacitor build we recommend for Webflow wraps any Webflow URL into a native Android app without either. A TWA would need a web manifest; a service worker only helps offline. For a custom icon and name, we read your site's favicon and Open Graph data, or you set them in SaasToStore.
Will my Webflow CMS, forms and interactions keep working?+
Yes. The app loads your live Webflow site, so your CMS content, forms, interactions and any custom code embeds behave exactly as on the web. Publish in Webflow and the app reflects it.
Is the result a real native app or a webview?+
It installs and runs like a native app — its own icon, full screen, no browser bar — and passes Google Play review. Your Webflow breakpoints render normally inside the shell.
Do I need Android Studio or any code?+
No. SaasToStore builds and signs the Android App Bundle in the cloud. You only need a Google Play Console account to upload the signed .aab.
My Webflow site is mostly content — is a Play Store app worth it?+
An installable app gives you a home-screen icon, full-screen reading and push notifications (included in SHIP) — strong for memberships, courses, communities and content brands built on Webflow.
Can I update the app after publishing?+
Yes. Re-publish in Webflow and the live content updates instantly in the installed app. You only rebuild for a new icon or name — and we reuse your keystore so updates stay accepted.
Can my Webflow site also become a desktop app?+
Yes. The same URL also builds Windows (.msi), macOS (.dmg) and Linux (.AppImage) installers — your Webflow site as a desktop app.
Can I publish my Webflow site to the App Store as well as Google Play?+
Yes. The same Webflow URL also produces a signed .ipa for the App Store — iOS is included in SHIP together with Android and desktop, so you are not buying a second product. You submit it under your own Apple Developer account (99 USD/year); we build and sign, you own the listing.
Will Apple approve a Webflow site published this way?+
Apple reviews wrapped web apps more strictly than Google does. App Store Review Guideline 4.2 asks for an app that does more than reopen a website, so your Webflow site needs real app value — an account, saved state, notifications, something a bookmark cannot do. Apps that are genuine products pass; a marketing page wrapped in a shell does not. Google Play applies a comparable rule but enforces it more loosely, which is why an app can clear Play and still be rejected by Apple.
Ready to ship?
Paste your URL. We handle the build. You publish to the store.
Publish now