Can a Webflow site be published on Google Play?

Yes. Webflow sites are served over HTTPS with a valid web manifest when PWA settings are enabled. SaasToStore wraps your Webflow URL in a signed Android App Bundle (.aab) using a Trusted Web Activity — the method Google recommends for PWAs.

Do I need to enable PWA mode in Webflow first?

Not necessarily. If your Webflow project does not have a service worker, SaasToStore's Capacitor mode wraps it natively without any service worker requirement. For TWA mode (lighter, Google-recommended), enable the PWA feature in Webflow's Project Settings.

Should I use my Webflow subdomain or a custom domain?

A custom domain is strongly recommended. Google Play requires a Digital Asset Link (assetlinks.json) hosted on the same domain, and custom domains signal professionalism in your Play Store listing. Both *.webflow.io and custom domains work technically.

How long does the Google Play review take for a Webflow app?

Initial review for new apps typically takes 1 to 3 business days. Updates are processed within 24 hours. SaasToStore builds are engineered for first-try approval — TWA template, valid manifest, signed AAB, minimal permissions.

How much does it cost to publish a Webflow app on Google Play?

Google charges a one-time 25 € developer account fee. SaasToStore starts free (one build with SaasToStore branding). The SOLO plan at 9 € adds your custom logo. LAUNCH from 15 € covers Android + Desktop + 7 stores.

Will my Webflow CMS content update automatically in the app?

Yes. Your Android app loads your live Webflow URL on every launch. CMS changes, new blog posts, product updates — all reach users instantly without any rebuild or Play Store review.

How to Publish a Webflow App to Google Play (2026 Guide)

Why Webflow sites are strong Play Store candidates

Every Webflow site ships over HTTPS by default. When PWA mode is active, Webflow automatically generates a manifest.json and registers a service worker — the two prerequisites that unlock Trusted Web Activity (TWA) builds. Even without PWA mode, SaasToStore's Capacitor pipeline wraps any HTTPS URL into a fully compliant .aab without requiring a service worker.

Webflow's semantic HTML and performance-optimized output also means fewer issues with Google's policy 4.3 (minimum functionality check), which rejects apps that feel like blank shells or simple website redirects. A well-built Webflow site passes this check reliably.

Quick check: Open your Webflow site, press F12 → Application → Service Workers. If you see an active registration, your site is TWA-eligible. If not, enable PWA in Webflow settings or use Capacitor mode — both paths produce a store-ready .aab.

Custom domain vs. Webflow subdomain

Both yoursite.webflow.io and your custom domain work as source URLs for the Android build. However, a custom domain is strongly recommended for two reasons: it allows you to host the Digital Asset Link file (assetlinks.json) that TWA mode requires, and it makes your Play Store listing look more credible to reviewers and users alike.

If you're using a Webflow subdomain, SaasToStore's Capacitor mode handles the build without the Digital Asset Link requirement.

Before you start — what you need

Your Webflow site's public HTTPS URL (custom domain or *.webflow.io)
A Google Play developer account (25 € one-time, 24–48h verification)
An icon at 512×512 px (PNG) — or generate one with SaasToStore's AI icon tool
A privacy policy URL (SaasToStore can auto-generate one for your app)
At least 2 phone screenshots of your running Webflow site
A 1024×500 feature graphic (no device mockups, no store badges)

Step 1 — Enable PWA in Webflow (recommended)

In your Webflow dashboard, go to Project Settings → PWA. Enable the PWA toggle, upload a 192×192 and 512×512 icon, set a theme color matching your brand, and configure the display mode to standalone. Save and republish your site.

This step is optional if you'll use Capacitor mode, but it takes under 5 minutes and unlocks the lighter, faster TWA build path. It also improves your site's discoverability via Chrome's "Add to Home Screen" prompt.

Step 2 — Check your PWA score

Run a free PWA scan on your Webflow URL before choosing a build type. The scan checks HTTPS, manifest validity, service worker presence, and icon dimensions.

Score ≥ 70 — TWA build (recommended)

Your Webflow site runs inside Chrome's engine — fast, secure, full PWA capabilities. Google's official method for publishing PWAs. Content updates go live instantly without a rebuild.

Score < 70 or no service worker — Capacitor build

Full native WebView wrapper. No service worker required. Works with any Webflow plan, including subdomain-hosted sites. Passes Play Store review reliably.

→ Run the free PWA check on your Webflow URL

Step 3 — Set up your Google Play developer account

Navigate to play.google.com/console, sign in with a Google account, and pay the one-time 25 € registration fee. Google verifies your identity within 24 to 48 hours. You cannot upload your first .aab until verification completes — start this in parallel with your build, not after.

Important: Create the app in the Play Console before uploading your .aab. The package ID (e.g., com.yourcompany.yourapp) must match exactly between SaasToStore and the Play Console listing. It cannot be changed after the first upload.

Step 4 — Build your signed Android App Bundle

SaasToStore replaces what would otherwise require Android Studio, Gradle, and hours of configuration. The pipeline generates a 2048-bit RSA keystore, compiles your Webflow URL into a signed .aab, and emails you the artifact along with an encrypted keystore backup.

Paste your Webflow URL

Sign in to SaasToStore, create a new project, and paste your Webflow site's public URL. SaasToStore auto-detects your manifest and PWA score.

Configure app identity

Set your app name (visible on the Play Store), package ID (com.yourcompany.yourapp), and version. Package ID cannot be changed after your first publish.

Upload your icon

Upload a 512×512 PNG. SaasToStore resizes it to all required Android densities automatically. Or use the AI icon generator to create one from a text prompt.

Launch the build

Click "Launch Build". The pipeline runs in under 5 minutes: manifest parsing → asset generation → AAB compilation → keystore signing → email delivery.

You'll receive an email with: the signed .aab (for Play Store), the .apk (for sideload testing), and your encrypted keystore. Store the keystore — you'll need it for every future update.

Step 5 — Configure your Play Store listing

A complete listing is required before Google accepts your .aab. The Play Console blocks submission until these sections are filled:

Store listing — Short description (80 chars), full description (4,000 chars), screenshots (min. 2 phone), feature graphic (1024×500)
App category — Required for discoverability. Choose the category that best matches your Webflow site's purpose
Content rating — Complete the IARC questionnaire (≈ 5 minutes). Incorrect answers trigger rejection
Data safety form — Declare what data your Webflow site collects. Include a privacy policy URL

Listing tip: Screenshots matter more than descriptions for conversion. Use your Webflow site's best-looking pages. Feature graphic should be a clean banner — no device mockups, no store badges per Google's policy.

After launch — live updates and multi-store

Every content update you publish in Webflow — new CMS items, design changes, new pages — reaches your app users instantly without any rebuild. Your Android app loads the live version of your Webflow URL on every launch.

Structural changes (new icon, updated app name, new permissions) require a new .aab build using the same SaasToStore project to preserve your keystore. Increment the version code by 1, rebuild, upload.

With the LAUNCH plan, the same pipeline produces a Windows .msi, macOS .dmg, and Linux .AppImage from the same Webflow URL — plus Amazon Appstore and Samsung Galaxy Store slots.

→ See pricing for multi-store distribution

How to Publish a Webflow App to Google Play