Publish in Webflow, the app follows
New CMS items and Designer changes show the next time someone opens the app. You don’t make a new build.
For Webflow sites
Your app loads your published Webflow site, with its Interactions, CMS pages, member logins and checkout. Publish in Webflow and the app shows it on the next open.
Before you paste: Use your published custom domain, not the webflow.io staging address.
See how it worksComes with you
New CMS items and Designer changes show the next time someone opens the app. You don’t make a new build.
Point native bottom tabs at pages like Blog, Work, Library or Account, the ones people reopen most.
AI writes a short script that hides your Webflow navbar inside the app only. Browser visitors still see it.
Write a title, text, image and link, delivered through your own Firebase project. Sent to everyone who opted in.
We fill in your name and icon. AI sorts your links into a header, side menu and tabs, and writes the script that hides your site’s own header and pop-ups. You adjust the rest.
Scan a code and use your real site as an app, before you pay.
You may be asked to install our preview app first.
We build in the cloud, so you need no Mac or Xcode. iOS lands in TestFlight in your Apple account; Android downloads as an AAB or APK. You submit for review from your own accounts.
Webflow has no app export, so teams either rebuild screens from the CMS API or put the published site in a native shell.
A few marketing pages read once, or you need offline use, Bluetooth or app-only screens.
The app shows your site in a WebView, like a mobile browser. Check these in your preview.
They run as in a mobile browser; hover-only effects stay fragile.
Try it: Open the menu, a dropdown and a scroll effect.
Webflow Interactions, GSAP timelines and Lottie files run in the WebView as they do in a mobile browser. Problems come from design choices that were already fragile on phones: hover-only reveals, long page-load animations that delay the first tap, and fixed layers that sit over buttons. An interaction that stutters in mobile Safari will stutter in the app too, so fix it in the Designer.
Collection lists and item pages load as published, including on-page filters.
Try it: Filter a list, open an item, swipe back.
Collection lists, Collection pages and pagination are ordinary pages on your domain, so they load in the app as published. Filter and search scripts such as Finsweet Attributes run with the page. Check that going back from an item returns you to the same place in a long or filtered list, on iPhone with a swipe and on Android with the back button.
Email sign-in runs on your pages; Google sign-in and emailed links can fail in apps.
Try it: Try every sign-in method, then close and reopen.
Email and password sign-in runs on your own Memberstack or Outseta pages and normally works as it does in mobile Safari or Chrome. Google sign-in can be blocked inside in-app browsers, so keep an email option. A login link tapped in a mail app opens the phone’s browser and signs the member in there, so offer a typed one-time code or a password. Moved off Webflow User Accounts? Test your Memberstack or Outseta pages in the preview.
Stripe card checkout stays on your domain; PayPal, wallets and off-site links need a full run.
Try it: Pay with Stripe and PayPal in test mode.
Webflow’s cart and checkout pages live on your own domain, so Stripe card payments normally stay inside the app. Apple Pay and Google Pay buttons from Webflow’s web payments setting may not show inside the app, so make sure card checkout still works without them. PayPal, Stripe Payment Links and booking or course tools run on other domains. Follow each one to the end and check the customer lands back on your order confirmation.
Hide the Webflow navbar in the app, then check sticky bars and top padding.
Do this: Hide the navbar and check each page top.
Left alone, your Webflow navbar and hamburger menu would sit directly under the app’s native header. A SiteTo.App script can hide your site’s own header and pop-ups inside the app only, while the website keeps them for browser visitors. Check sticky announcement bars and anything positioned against the navbar after it is hidden, since Webflow layouts often offset the first section to make room for it.
Apple’s in-app purchase rules (3.1.1) can apply to digital content sold through your site.
Check: Read Guideline 3.1.1 before selling memberships.
If members pay for lessons, downloads or other digital content, Apple can require its in-app purchase system for those sales under Guideline 3.1.1, with exceptions that depend on the kind of app and the country. Physical goods and services used outside the app are treated differently. Read the guideline and decide how sign-up and upgrades appear in the iPhone app before you submit.
These are a starting point for your free preview, not a claim that every site setup or integration has been tested. Not for apps that need Bluetooth, AR, heavy offline use or background processing.
Planning the build?Setup walkthroughReadiness checklist
Website changes show up in the app without a rebuild. No subscription, and the price doesn’t change as your app gains users.
Paid to Apple and Google
Later rebuilds, such as a new icon, are included.
Yes, you can turn a Webflow site into an iOS and Android app with SiteTo.App without rebuilding it. The app loads your live Webflow site, adds your branding and menus, and costs $29 for Android, $79 for iOS or $99 for both, paid once per platform. Apple and Google developer accounts are separate.
No. Webflow designs, hosts and publishes websites and has no feature that produces an iOS or Android app. You don’t need to export your code either. SiteTo.App loads your published site in a native shell, so CMS, Ecommerce and member pages keep running on Webflow hosting.
It is if people come back: members who sign in, readers of a CMS publication, repeat buyers. A few marketing pages that visitors read once make a weak app, and Apple can reject it under Guideline 4.2. If that is your site, a home screen shortcut costs nothing.
People see the latest version of your website when they open or refresh the app, so ordinary content and page updates do not need a new app build. A new app icon, app name or launch screen needs a new build.
Apple decides, so nobody can guarantee it. Apple can reject apps that add nothing beyond a website (Guideline 4.2), so plan for real app features such as native navigation and push, and test your key journeys in the preview first.
Yes. Paste your URL and open the preview on your own phone. You don’t need an account or a card to preview, though you may be asked to install our preview app first. You only pay when you choose a build.
Paste your site URL and open the preview on your phone. Pay only when you build.
No account or card to preview.