How to Download Google Sites for Offline Viewing
Use Google Takeout for an owner archive or HTTrack for a browsable offline copy of a published Google Site, with limits and fixes explained.
Use Google Takeout/Google Drive export if you own the Google Site. It is Google’s preservation route and can include site content, settings and related files. If you only need to browse a published site without an internet connection, use HTTrack to mirror the visitor-accessible pages to your computer.
An owner export and a visitor mirror solve different problems. Takeout is better for backup and preservation; HTTrack is better for a locally browsable copy. For important sites, keep both.
Choose the right method
| Goal | Best method | What you get |
|---|---|---|
| Back up a Site you own or administer | Google Drive/Google Takeout | An export archive containing available Site data and settings |
| Read a published Site offline | HTTrack | A local mirror of pages and assets a visitor can fetch |
| Preserve ownership data and test browsing | Both | An official archive plus a visitor-style offline copy |
Method 1: Export a Google Site with Google Drive or Takeout
Google’s Sites help documentation describes exporting Google Sites data from Google Drive. Depending on the Site and account, the archive can include draft and published sites, full pages, embedded URLs, table of contents, image carousels, text and collapsible text, buttons, custom paths, navigation links, themes, fonts, colors, logos, favicon, navigation bars, announcements, file cabinets, attachments, lists, page templates and site-owner information. See Google Sites Help for the current account-specific workflow.
Step-by-step
- Confirm that the Site is in an account and Drive location you can export.
- Open Google’s export workflow and select the Google Drive/Sites data available to your account.
- Create the archive and wait for Google to make it available.
- Download the archive to your computer.
- Extract it into a new folder and inspect the included HTML and other files.
- Open the exported start page or HTML files in a browser. Check several pages, images and attachments.
- Keep a second copy on removable storage or another location if the archive is important.
What the export does not guarantee
- A downloaded archive does not guarantee that login-protected content works offline.
- Third-party embeds may still require their original service and an internet connection.
- Server-side behavior, forms, search, comments and other live interactions may not function locally.
- Work or school policies can make data unavailable for download; administrators may control organization exports.
- Google warns that files exceeding maximum export size limits can cause an export to fail.
Method 2: Mirror a published Site with HTTrack
HTTrack copies a website to your disk so you can read it offline. It recursively downloads HTML, images and other fetchable files, keeps a relative link structure, can resume an interrupted download and can update an existing mirror.
Graphical workflow
- Install HTTrack for your operating system from the official project site.
- Start a new project and choose a local destination folder.
- Enter the published Google Site URL, including
https://. - Keep the crawl within the Site’s domain unless you intentionally need linked domains.
- Start the mirror and let the crawl finish.
- Open HTTrack’s generated local start page in a browser.
- Switch your computer offline and test navigation, images, downloads and several nested pages.
Command-line example
On systems where the httrack command is available, this creates a project directory and limits crawling to the supplied domain:
httrack "https://sites.google.com/view/your-site/" -O1 "./google-site-mirror" "+https://sites.google.com/view/your-site/*"
Replace the URL with the published address of the Site. HTTrack’s command-line options differ by version, so run httrack --help when you need exclusions, proxy settings or update behavior.
Keep the mirror focused
- Start with the exact published Site hostname and path.
- Allow only the Site’s domain by default; linked Google Drive files, YouTube videos and external embeds may enlarge the crawl or remain online-only.
- Do not attempt to bypass authentication or access controls.
- Respect the Site owner’s rights and applicable terms. Archive material you are allowed to copy.
Why an offline copy can look incomplete
HTTrack mirrors what an unauthenticated visitor can fetch. A page can therefore open while parts of it remain unavailable offline.
| Symptom | Likely reason | Practical response |
|---|---|---|
| Images are missing | The image is lazy-loaded, hosted on another domain or blocked during the crawl | Open the page online first, allow the crawl to complete, and check external-host rules |
| A sign-in page appears | The content requires authentication | Use an owner export or save authorized files separately; do not bypass access controls |
| An embed is blank | The embedded service needs scripts or network access | Capture or download the source material separately if you have permission |
| Navigation returns to the internet | A link points to an absolute live URL or an uncopied domain | Include the permitted domain in the mirror, or accept that the link is online-only |
| Forms, search or comments fail | They depend on Google’s servers | Use the live Site for interaction; an offline mirror is mainly for reading |
How to verify the download
- Record the original published URL and download date.
- Open the local start page with your network disconnected.
- Test the home page, every top-level navigation item and at least one deep page.
- Check representative images, PDFs, attachments and collapsible sections.
- Search the extracted folder for unexpectedly small or missing files.
- Store the archive or mirror in two locations and label both with the date.
Or skip the browser setup
If you only need image snapshots of Google Site pages for documentation, review or a report, ScreenshotNeo provides a one-request screenshot API. It returns PNG, JPEG or WebP (and can create PDFs), but a screenshot is a visual snapshot rather than a replacement for an editable offline Site.
Before capture, ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets. Bot checks, blank pages, timeouts, failed loads and cache hits cost nothing, and the response identifies the page verdict and billing with X-Page-Verdict and X-Billed headers. Its MCP server also lets Claude, Cursor and other MCP clients call take_screenshot, get_page_info and capture_pdf.
See the ScreenshotNeo API documentation for all options, including full-page capture, CSS selectors, device presets, custom CSS and JavaScript, waits, request blocking, cookies, headers, geolocation, PDF settings, caching, signed links, asynchronous jobs, bulk capture and usage reporting.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://sites.google.com/view/your-site/ -o site.webp
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://sites.google.com/view/your-site/"},
timeout=90,
)
r.raise_for_status()
open("site.webp", "wb").write(r.content)
const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://sites.google.com/view/your-site/'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const file = await res.arrayBuffer();
await import('node:fs/promises').then(fs => fs.writeFile('site.webp', Buffer.from(file)));
There is a free allowance of 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots, and every feature is included on every plan. Create a free ScreenshotNeo account.
Troubleshooting
Google export is unavailable
Check that you are exporting the correct Drive account and that your organization permits downloads. Ask a Workspace administrator about export controls. If you only need visitor-readable pages, use HTTrack instead.
The export fails or never completes
Large files can exceed Google’s export limits. Reduce the scope where the export workflow allows it, remove unneeded material, or create separate archives. Keep the original Site intact while you verify each archive.
HTTrack stops partway through
Check disk space, network stability and the crawl scope. Resume the project rather than deleting it; HTTrack supports resuming and updating an existing mirror.
The local copy works online but not offline
Disconnect the network before testing. Any absolute URL, remote script, authentication step or third-party embed that still loads is an online dependency. Download permitted source files separately or accept the limitation.
Only a screenshot is needed
Use ScreenshotNeo for a clean visual capture. A screenshot cannot preserve navigation, source HTML or live interactions, so retain a Takeout archive or HTTrack mirror when those are required.
FAQ
Can I save an entire Google Site as HTML?
HTTrack can save the visitor-accessible rendition as local HTML and assets. Google Takeout is the better choice when you own the Site and need its data and settings preserved.
Can I re-import an HTTrack mirror into Google Sites?
HTTrack creates a browsable copy, not a Google Sites project intended for re-import. Keep the official owner export if editability or preservation of Site structure matters.
Will a private Google Site work in HTTrack?
Only content the crawler is authorized and configured to fetch can be mirrored. Authentication-protected pages and private embeds may not work offline.
Should I keep more than one backup?
Yes. Store the downloaded archive or mirror in at least two locations and record the export or crawl date.
Summary
- Use Google Drive/Takeout for an owner-controlled archive.
- Use HTTrack for a locally browsable copy of a published Site.
- Expect authentication, dynamic scripts and some embeds to remain online-only.
- Check export limits and account policy before relying on one archive.
- Keep a second copy, and use ScreenshotNeo when a clean visual snapshot is the actual requirement.


