🔄 Google Sites → Android

Turn Your Google Site Into an Android App

Google Sites has no app export and no plugins to add one — but the moment you click Publish and enter a web address, your site is an ordinary public page. Paste that address into Free App Maker and get a signed Android APK in about 60 seconds. No account, no coding, no Android Studio.

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

Yes — a published Google Site can become an Android app. Google Sites publishes to a public web address, and Free App Maker wraps that address in a signed Android WebView APK in about 60 seconds, embedded Forms, Maps and YouTube included. Building and previewing are free; downloading the signed APK is a one-time unlock, with the price shown before checkout.

Source for the Google Sites publish step: Google Sites Help — Publish & share your site, checked 26 Aug 2026.

Convert My Google Site — Free → Check Compatibility

✓ Free to start, no account ✓ Signed APK in ~60 seconds ✓ Custom domains work too

Signed APK in ~60 seconds

Published /view/ URLs convert directly

Free to start, no account

Forms, Maps & YouTube embeds keep working

No coding, no Android Studio

What is Google Sites?

Google's drag-and-drop site builder — and the Publish step that matters here

Google Sites is Google's own website builder, available with a Google Account. You assemble pages from drag-and-drop sections and insert Google content directly. Google's documentation lists what you can add: Docs, Slides, Sheets, Forms and Charts, plus YouTube, Calendar and Map — and beyond those, embedded web addresses, Apps Script, and HTML, CSS or JavaScript code.

The publish step is the detail that matters for conversion. Google's guide is short: at the top, click Publish; enter the web address for your site; click Publish; then visit your site's web address to make sure it's published correctly. That published address — sites.google.com/view/your-site on a personal account, sites.google.com/domain/sitename on a Workspace account, or a custom domain — is an ordinary public web page. The address you are looking at while editing is not that address, so publish first and copy the one Google gives you.

Free App Maker is a website to APK converter: it takes that published address and wraps it in a signed Android app. Your site stays exactly where it is, edited exactly as before; the app is a dedicated, installable window onto it.

Custom domains per site (max)

48h

Domain changes to propagate

~60s

Our average build time

Sources: Google Sites Help — Add Google files, videos, website content, & more, Publish & share your site, Google Workspace Learning Center — Publish your site and Use a custom domain for your site (five domains per site; up to 48 hours to propagate), all checked 26 Aug 2026. The ~60s figure is our own average build time, measured on the Free App Maker build pipeline.

Why not just "Add to Home screen"?

A Google Site isn't an installable web app — so the shortcut stays a shortcut

The obvious free alternative is Chrome's Add to Home screen. For a page that ships a web app manifest, Chrome can install it as a standalone app. Chrome's documented install criteria require exactly that: the page must be served over HTTPS and provide a web app manifest with short_name or name, icons including a 192px and a 512px icon, a start_url, and a display value of fullscreen, standalone, minimal-ui or window-controls-overlay.

Google Sites does not publish one. Loading a live published Google Site on 26 August 2026 and inspecting the document returned no <link rel="manifest"> and no registered service worker — so Chrome has nothing to install, and what you get is a browser shortcut rather than a standalone app. A signed APK is a different object: it installs as a real Android app, gets its own launcher icon, opens without browser chrome, and is a file you can hand to someone.

Sources: web.dev — Installability criteria, checked 26 Aug 2026. The manifest check was run by us against a live published Google Site (sites.google.com/view/…) on 26 Aug 2026; Google could add a manifest at any time, so re-check before relying on it.

The maintenance story stays simple either way. You keep editing in Google Sites as you always have. When you publish, the app shows the new version the next time it loads that page — no APK rebuild, no re-distribution.

Simple 3-Step Process

Convert Your Google Site to Android in 3 Steps

No Android Studio. No Gradle. No code. Just your published Google Sites URL — and your APK is ready in about a minute.

Publish your site & copy the published address

In Google Sites, click Publish at the top and enter the web address for your site, then visit that address to check it published correctly — Google's own three-line instruction. Copy it: https://sites.google.com/view/your-site, or your custom domain. Then check the site is publicly viewable: under Share, next to Published site, the drop-down should read Public, not Restricted. Quick test: open the URL in a private/incognito window. If it loads without a sign-in prompt, it will convert cleanly.

Configure your Android app

Head to freeappmaker.org and paste your published URL. Enter the name you want to appear under the app icon on Android home screens, add your email address, and optionally upload a 1024×1024 PNG icon. We'll auto-generate the required Android icon sizes from that single image.

Download your signed APK

Our build system wraps your published site in 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, priced by country, and its exact price is always shown before you pay. Install the APK on an Android phone or tablet by opening it and tapping Install, or share the file with the people who use your site.

Source for the Google Sites publish and sharing steps described in step 1: Google Sites Help — Publish & share your site, checked 26 Aug 2026.

Ready to put your Google Site on Android home screens?

Convert Free — Takes About 60 Seconds →

Use Cases

Who Converts Google Sites to Android?

Google Sites powers class pages, club sites, and small-business pages — exactly the sites whose audiences benefit most from a home screen icon.

Teachers & Class Sites

Your class site holds the homework calendar, resources, and announcement banner — and students lose the link every term. As an Android app, the class site sits on the student's (or parent's) home screen. Embedded Forms for quizzes and permission slips keep working inside the app, and every time you hit Publish, the app shows the update.

Small Businesses

Many small businesses run their whole web presence on Google Sites: opening hours, services, a Maps embed for directions, a Form for enquiries. Converting the published site to an APK gives regular customers an app icon instead of a bookmark — with the same Maps directions and enquiry form inside, and no separate app to maintain.

Clubs, Communities & Nonprofits

A club or community site on Google Sites changes constantly — events, rosters, meeting notes. An Android APK you share in the group chat puts the site one tap away for members. Because the app loads the live published site, the person who maintains the site keeps working in Google Sites and never touches the app again.

Events, Weddings & Portfolios

Event pages and portfolios built in Google Sites are made to be shared. Hand guests an installable app with the schedule, venue map, and RSVP form, or give your portfolio a more polished delivery than a pasted link. When the event details change, republish in Google Sites — the app follows.

Compatibility Guide

What Works — and the One Thing That Trips People

Free App Maker wraps your published Google Sites URL in an Android WebView. The app renders the same page a browser does — so most of what follows is Google Sites behaviour, not app behaviour.

✅ Works out of the box

Published sites at sites.google.com/view/… addresses, and Workspace sites at sites.google.com/domain/sitename
Custom domains connected to Google Sites — up to five per site, connected by the site owner
The content types Google documents as insertable: Docs, Slides, Sheets, Forms and Charts
YouTube, Calendar and Map embeds — the other insert types in the same Google guide
Embedded web addresses, Apps Script, and custom HTML, CSS or JavaScript blocks
Multi-page sites with navigation menus and sub-pages
Collapsible text, image carousels, and buttons
Announcement banners and site search
Anchor links, if you left Show anchor links on under Settings → Viewer tools
Sites you asked Google to keep out of search results — that setting is a crawler request, not an access control

Sources: Add Google files, videos, website content, & more, Use a custom domain for your site and Publish & share your site (Google Sites Help), all checked 26 Aug 2026.

⚠️ Check before you convert

The site must actually be published. Until you click Publish and enter a web address there is no public page to wrap — and the address you see while editing is not the one to paste.
Published visibility must be Public. Under Share, next to Published site, Google lets you select Restricted or Public; a Restricted site is shared only with the people and groups you add as Published Viewers, and it will ask for a Google sign-in inside the app exactly as it does in a browser.
Draft edits stay invisible until you publish again. Google's publish review shows the draft on the left and the current published version on the right, with annotations marking unpublished changes — the app shows the published side.
Restricted embeds don't become public inside the app. Google is explicit: if a file is stored on a shared drive or has restricted sharing permissions, only people with access will be able to see the file — so share the Doc, Sheet or Form itself, not just the site.
On a custom domain, three things change. Google Groups embeds do not render properly; features needing a Google Account sign-in can fail, because a custom-domain-mapped site is no longer hosted on sites.google.com and cookies for *.google.com are not sent; and additional third-party fonts fall back to web-safe alternatives.
Give a new custom domain time. Google says changes to your domain may take up to 48 hours to become visible on the Internet — build the app after the domain resolves, not before.
Drive file links open Google's file viewer — walk that flow on a real device before sharing widely.

Sources: Publish & share your site, Review the latest changes to your site before publishing, Add Google files, videos, website content, & more and Use a custom domain for your site (Google Sites Help), all checked 26 Aug 2026. Google can change these behaviours — check the current pages before relying on them.

The fast test: open your URL in a private/incognito window. If it loads without a sign-in prompt, it will convert cleanly. You can also run it through our free WebView Compatibility Checker. This flow isn't Google Sites-only — any live page can be wrapped, as our URL to APK guide shows.

How It Compares

Free App Maker vs. Your Alternatives

Free App Maker works as a free website to APK converter for any published Google Site — paste the URL on the homepage.

A Google Site owner who wants an Android app realistically picks between four things: a hosted web-to-app service, an Android Studio template they build themselves, Chrome's Add to Home screen, or us. Prices below come from each vendor's own pricing page and were checked on 26 August 2026.

Approach	Free App Maker ✓	AppsGeyser	Median.co	WebViewGold	Chrome “Add to Home screen”
Price (checked 26 Aug 2026)	Free to build — one-time unlock to download, price shown before checkout	From $58/mo (Starter); no free plan listed	Free tier with watermark; Starter $229 one-time, then $179/yr	$109 one-time (sale price to 31 Aug 2026; $154 listed)	Free
Unbranded app	✓ After the one-time unlock	Custom Branding / No Ads listed from the $98/mo plan	✗ On the free tier — a “Powered by Median.co” watermark is displayed in the app	✓ 100% white-label	n/a
What you actually get	A signed APK on the build screen in about 60 seconds	An app built in their no-code builder	Native iOS and Android apps built in their App Studio	An Android Studio template you build and sign yourself	A browser shortcut — no file to share
Coding / tooling required	None	None — described as a no-code app builder	None — their pricing page says without Xcode or Android Studio	✗ Android Studio	None
Installs as a standalone Android app	✓ Yes	✓ Yes	✓ Yes	✓ Yes	✗ Not for a Google Site — no web app manifest, so Chrome has nothing to install
Recurring cost after year one	None — the unlock is one-time	Subscription continues	$179/yr from month 12 on Starter	None — one-time licence	None

Competitor pricing checked 26 August 2026 against each vendor's own pricing page: AppsGeyser (Starter $58/mo, Individual $98/mo, Master $238/mo — no free plan listed), Median.co (Free $0 with a “Powered by Median.co” watermark; Starter $229 one-time licence activation fee plus $179/yr from month 12 — this page returns HTTP 403 to automated fetches, so it was read in a real browser) and WebViewGold ($109 one-time, a sale price listed against $154 and stated to run to 31 August 2026). The Chrome column reflects web.dev's installability criteria and our own 26 Aug 2026 check that a published Google Site serves no web app manifest. Vendors change prices and plan contents — check each site for the current position.

Why Free App Maker

6 Reasons Google Sites Owners Choose Free App Maker

The practical advantages that make this the shortest path from a published Google Site to an Android device.

Publish in Google Sites, update the app

The APK loads your live published URL. Edit the site, click Publish, and the app shows the new version the next time it is opened — no new APK build, no re-sharing files, no update prompts for the people using it. Your workflow in Google Sites doesn't change at all.

Your embeds come along

Because the app renders the same published page, the content types Google documents as insertable — Docs, Slides, Sheets, Forms, Charts, YouTube, Calendar and Map — render inside the app as they do in mobile Chrome, with no extra configuration. The one thing to sort out first is sharing: Google notes that a file on a shared drive or with restricted permissions stays visible only to people with access.

Signed APK in about 60 seconds

From published URL to signed APK in your inbox in about a minute. No local build environment, no SDK downloads, no waiting on a build queue. Paste the URL, verify your email, and the download link arrives.

No new tools to learn

You chose Google Sites because it needs no code and no hosting. Converting it keeps that promise: there is no SDK, no manifest file, and no store console to configure. If you can publish a Google Site, you already know how to make the Android app.

Share the APK your way

The APK is a file you can distribute however suits your audience: attach it in the class group chat, link it from the site itself, hand it out on Drive, or load it onto shared devices. If you later move the site to a custom domain, rebuild with the new URL in about a minute.

Renders the way Google built it

A published Google Site we loaded on 26 August 2026 ships a width=device-width viewport tag, so its layout adapts to phone and tablet screens inside the WebView the same way it does in mobile Chrome. And the rendering engine itself is updated through the Google Play Store — not by us shipping you a new APK. Chromium's WebView documentation notes that WebView and Chrome for Android always release together on all OS levels, and that from Android 10 onwards Chrome can no longer be used as the WebView implementation, though on earlier versions it could.

Sources: Google Sites Help — Add Google files, videos, website content, & more (the insertable embed types, and the note that restricted files stay restricted) and Chromium — WebView pre-release channels (WebView and Chrome release together; Chrome is not a WebView implementation from Android 10 on), both checked 26 Aug 2026. The viewport observation is our own check of a live published Google Site on the same date.

FAQ

Frequently Asked Questions

Everything you need to know about converting a Google Site to an Android APK.

Can I turn a Google Site into an Android app?

Yes. Once a Google Site is published it is an ordinary public web page — and a public URL is exactly what Free App Maker wraps. Google's own Publish & share your site guide describes the flow: click Publish at the top, enter the web address for your site, then visit that address to make sure it published correctly. Paste that address into Free App Maker and a signed Android APK is ready in about 60 seconds. Building and previewing are free; downloading the signed APK is a one-time unlock, priced by country, with the price shown before checkout.

Source: Google Sites Help — Publish & share your site, checked 26 Aug 2026.

Why does my app open a Google sign-in screen?

Almost always because the address being wrapped is not a publicly published one. Google Sites keeps published visibility under Share: next to Published site you select Restricted or Public, and a Restricted site is shared only with the specific people and groups you add as Published Viewers. A WebView is subject to the same access controls as a browser, so a Restricted site asks for a Google sign-in inside the app too. The other cause is pasting the address you see while editing rather than the published web address you entered at the Publish step. The test takes ten seconds: open your URL in a private or incognito window, and if it loads without a sign-in prompt it will convert cleanly.

Source: Google Sites Help — Publish & share your site, checked 26 Aug 2026.

Do embedded Google Forms, Maps, Docs, and YouTube videos keep working?

In most cases, yes — the app renders the same published page, so what renders in mobile Chrome should render in the app. Google Sites documents the insertable types: Docs, Slides, Sheets, Forms and Charts, plus YouTube, Calendar and Map, along with embedded web addresses, Apps Script, and HTML, CSS or JavaScript code. One caveat comes straight from Google's documentation: if a file is stored on a shared drive or has restricted sharing permissions, only people with access will be able to see the file. Check the embeds that matter on a real device before you share the app.

Source: Google Sites Help — Add Google files, videos, website content, & more, checked 26 Aug 2026.

Does the Android app update when I edit my Google Site?

Yes — after you publish again. Google Sites holds your edits in the draft until then: its publish review splits the screen with the draft on the left and the current published version on the right, and annotations on the left show unpublished changes to your site. That review is turned on by default. The APK loads your live published address, so the app shows the last published version, and publishing an update is the same click you already use. No APK rebuild is needed.

Source: Google Sites Help — Review the latest changes to your site before publishing, checked 26 Aug 2026.

My site uses a custom domain — which address should I build the app on?

Build on the address your visitors actually use. Google documents that you can connect up to five custom domains to one site and that only the owner of a site can connect it to a domain, and it warns that a custom domain mapped site is no longer hosted on sites.google.com. So if you move to a custom domain after building, rebuild the app on the new domain rather than assuming the old address keeps serving. Google also notes that it may take up to 48 hours for changes to your domain to become visible on the Internet, so wait for the domain to resolve before you build.

Source: Google Sites Help — Use a custom domain for your site, checked 26 Aug 2026.

Does anything on my Google Site behave differently on a custom domain?

Three things, according to Google's own custom domain documentation. Google Groups embedded in Google Sites that have been published to a custom domain will not render properly. Features that rely on a Google Account sign-in can fail, because a custom domain mapped site is no longer hosted on sites.google.com and cookies for *.google.com are not sent. And additional third-party fonts do not work with custom URLs, falling back to web-safe alternatives. All three affect the browser and the app the same way — the app is not adding the limitation.

Source: Google Sites Help — Use a custom domain for your site, checked 26 Aug 2026.

I asked search engines not to index my site. Does the app still work?

Yes. Google Sites offers a setting under Publish settings called Request public search engines to not display my site, and Google is explicit that this is a request and doesn't guarantee that your site won't show up in public search engines. It is only available when the site is set to Public on the web. Either way it is a signal to search crawlers, not an access control, so the page still loads normally — in a browser and inside the app.

Source: Google Sites Help — Publish & share your site, checked 26 Aug 2026.

What if my site is restricted to specific people or my Workspace organisation?

Then the app asks for the same Google sign-in the browser does, because a WebView inherits the site's access controls. Google's guidance is that published visibility is set under Share, next to Published site, by selecting Restricted or Public — and it notes that if you use Sites for work or school, you may find other options. An internal-only app can still be useful for a team who all have accounts, but test it on a real device with a colleague's account before you rely on it.

Source: Google Sites Help — Publish & share your site, checked 26 Aug 2026.

What happens if I unpublish the site or the domain lapses?

The app has nothing to load. It is an honest wrapper around your live published page: it needs an internet connection, and it needs that address to stay reachable and publicly viewable. If you unpublish the site, switch published visibility to Restricted, or let a connected custom domain lapse, the app shows an error rather than your content — it keeps no offline copy of the site.

Can I publish my Google Sites app to Google Play?

The APK you receive is built for direct installation and sharing — install it on any Android device or send the download link to the people who use your site. A new Play listing 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 a Play submission needs an AAB rather than an APK — the Play Store Pack gives you one, along with the graphics, privacy policy and form answers. Google Play's functionality policy is also worth planning around: it says Google does not allow apps that only have limited functionality and content, and expects a basic degree of adequate utility as mobile apps. You can get the Play Store files, made for you in one payment.

Sources: Android Developers — About Android App Bundles and Play Console Help — Functionality, Content, and User Experience, both checked 26 Aug 2026.

Is this free? Any hidden costs?

Building and previewing your app is free — no account, no credit card, no subscription. 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.

Also Converting From