Paste your published sites.google.com/view URL, verify your email, and get a signed Android APK in about 60 seconds. Free to start, no account, no coding, no Android Studio.
Google Sites is the free website builder built into your Google account. You assemble pages from drag-and-drop sections, insert Docs, Sheets, Slides, Forms, Maps, Calendar, and YouTube embeds, and collaborate on the site the same way you would on a Google Doc. There is no hosting to set up and nothing to install — when you click Publish, the site goes live at an address like sites.google.com/view/your-site, or on a custom domain you connect.
That publish step is the detail that matters for conversion. A Google Site has two URLs: the editor address (sites.google.com/d/…), which requires a Google sign-in, and the published address (sites.google.com/view/…), which anyone can open once the site is published. The published address is an ordinary public web page — which means Free App Maker can wrap it into a signed Android APK exactly like any other website.
Google Sites is popular with teachers, clubs, small businesses, and event organisers precisely because it is free and frictionless. Converting the published site to an Android app keeps that spirit: paste the URL, verify your email, and the APK arrives in about 60 seconds.
Sharing a sites.google.com/view link works, but it asks something of your audience: open a browser, find the link again, remember where it was posted. For the people who actually use a Google Site — students, parents, club members, customers — that friction adds up. An Android app removes it: they tap an icon on the home screen and the site opens full-screen, without an address bar.
Because the APK renders the same published page, everything on the site comes along: your embedded Google Form still collects responses, your Maps embed still shows directions, your YouTube videos still play. You are not rebuilding anything — you are giving the site you already maintain a second front door.
And the maintenance story stays simple. You keep editing in Google Sites the way you always have. When you click Publish, the app shows the new version the next time it is opened — no APK rebuild, no re-distribution. For a class site that changes weekly or a club site with a rotating events page, that is the difference between an app that stays current and one that goes stale.
No Android Studio. No Gradle. No code. Just your published Google Sites URL — and your APK is ready in about a minute.
In Google Sites, click Publish at the top right and confirm the web address. Copy the published URL — it looks like https://sites.google.com/view/your-site, or your custom domain if you connected one. Do not use the editor URL (sites.google.com/d/…) — that address requires a Google sign-in, so the app would open a login screen. Quick check: open your URL in a private/incognito window. If it loads without asking you to sign in, it will convert cleanly.
Head to freeappmaker.ai 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.
Confirm the verification email we send you. Our build system wraps your published site in a WebView APK, signs it, and sends you a download link — the whole process takes about 60 seconds. Install the APK on an Android phone or tablet by opening the link and tapping Install, or share the file with the people who use your site.
Ready to put your Google Site on Android home screens?
Convert Free — Takes About 60 Seconds →Google Sites powers class pages, club sites, and small-business pages — exactly the sites whose audiences benefit most from a home screen icon.
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.
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.
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.
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.
Free App Maker wraps your published Google Sites URL in an Android WebView. The app renders the same page a browser does — here's what to expect.
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.
Several paths exist to get a Google Site onto Android devices. Here's how they compare honestly.
| Approach | Free App Maker ✓ | Hire Android Dev | DIY Android Studio | PWA (Add to Home) |
|---|---|---|---|---|
| Time to first install | ~60 seconds | Weeks | Days of setup | Minutes, varies by browser |
| Cost to start | $0 | Developer's fee | Your time | Free |
| Home screen icon | ✓ Custom icon | ✓ Custom icon | ✓ Custom icon | Browser-dependent |
| No browser address bar | ✓ Yes | ✓ Yes | ✓ Yes | Sometimes visible |
| Coding required | None | Full native dev | Java / Kotlin | None |
| Signed APK file to share | ✓ Yes | ✓ Yes | Sign manually | ✗ No APK |
| Updates when you republish the site | ✓ Automatic | Depends on the build | Depends on the build | ✓ Automatic |
The practical advantages that make this the shortest path from a published Google Site to an Android device.
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.
Because the app renders the same published page, embedded content keeps working: Google Forms collect responses, Maps show directions, Docs and Slides render in their viewers, and YouTube videos play — all inside the app, with no extra configuration.
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.
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.
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.
Google Sites layouts are responsive by design, so they adapt cleanly to phone and tablet screens inside the Android WebView. The WebView's rendering engine is updated by Google through Play Services, so your site benefits from current browser rendering without a new APK build.
Everything you need to know about converting a Google Site to an Android APK.
Paste the /view/ URL, verify your email, get a signed APK in about 60 seconds. Free to start.
Convert My Google Site — Free →