Skip to content
From published URL to portable files

Squarespace Website Exporter

Paste your published Squarespace URL, pick the pages, and download a ZIP of HTML, CSS and JavaScript to test, edit or self-host.

01How it works

Paste your Squarespace URL and choose pages.

Choose what to include

  1. Paste the public Squarespace link

    Copy the address of your published site, not its editor. The page must open without a login.

  2. Choose the pages to export

    The scan follows links up to three levels deep. Select the pages you need from the results, within your plan’s limit.

02How it works

Download your Squarespace site as HTML files.

Inside your ZIP download

Page content and design

Your published Squarespace pages and styles. The ZIP contains the live site’s output, not an editable Squarespace template. Review page titles and search settings before publishing.

Images and fonts

Choose downloaded assets to include available images and fonts. Free exports keep them linked to the original site. Videos and embeds may still need an internet connection.

Menus and animations

Supported navigation and page interactions are included. Blocks that use Squarespace services may need a replacement.

03How it works

Test your exported site then publish it.

Choose your hosting

  1. Test the exported site

    Unzip the download and open the files through a local web server or temporary hosting. Check layouts, links, forms and animations on desktop and mobile.

  2. Publish on your chosen host

    Upload the tested files to Vercel, Netlify, Cloudflare Pages or GitHub Pages. Check the live site before changing your domain. Hosting costs and provider terms apply.

Before you move your domain. The ZIP does not include Commerce, Member Areas, Scheduling or form processing. Connect replacement services for those features.

Squarespace’s built-in export vs NoCodeExport

Squarespace’s built-in export writes one .xml file in WordPress format. Its help center lists what that file carries. NoCodeExport captures a static view of public pages, without moving Squarespace’s backend.

What you needSquarespace built-in export
Recommended path
NoCodeExport
File you download
One .xml file, and only in WordPress format: you click the WordPress icon even when WordPress is not the destination.A ZIP of the rendered HTML, CSS and JavaScript. On Pro the images, fonts and files the pages reach are downloaded into it; the free plan links them from Squarespace’s servers.
Page types
Layout pages, gallery pages and one blog page. Album, cover, index, info, calendar, portfolio and store pages, and dropdowns, do not export.Selected public pages reachable from your URL, within plan limits. Private pages and backend functionality are excluded.
Blocks and media
Text and image blocks. Audio, video and product blocks do not export; embed-type blocks come out as text with minimal structure.Rendered text, images and supported blocks. Video and audio may stay linked to their source; commerce, memberships and forms need separate services.
Design and styling
Not included: style settings, custom CSS, drafts, and content in page-specific headers, footers and sidebars.Captures available styles and assets. Compare desktop/mobile layouts and test navigation before switching hosts.
Blog
One blog page only, with its posts and up to 1,000 comments per post. A second blog is left out.Blog pages and posts linked from the site, as published, within the same page limit.
What it needs from you
An active, published site set to Public; trial sites cannot export.A public URL. No Squarespace login, and a single page is free to test.

Facts in the built-in export column follow Squarespace’s help article “Exporting your site”, checked 7 September 2026: support.squarespace.com

Squarespace guides for full-site export planning

These reads explain the XML limitation, compare export options, and walk through what to validate before switching hosts.

One site or ongoing exports?

Export once with Site Pass, or choose Pro for regular updates and client projects.

Free

Try the exporter on one page, with assets linked to the original site.

$0

Features included:

  • 10 Exports / Month
  • 1 successful export per domain, ever
  • Single Page Only
  • Small "Exported with NoCodeExport" footer link
  • Watermark Removal
  • Framer, Webflow, Wix & More
  • Single-page SEO audit
  • 7-day Export Retention
  • Community Support

Pro

Most Popular

For complete sites: downloaded assets, GitHub and Netlify deploys, the export API and included hosting.

$10/mo

Features included:

  • Everything in Free
  • No attribution footer
  • Up to 100 Pages / Export
  • Full Site SEO Audit
  • Offline-ready asset export
  • GitHub & Netlify Deploy
  • Hosting on ncehost for up to 15 sites
  • API access and scheduled re-exports
  • 50 Exports / Month
  • Export History (30 days)
  • Priority Processing

Agency

For freelancers and agencies handling multiple client sites.

$50/mo

Features included:

  • Everything in Pro
  • Unlimited Exports / Month
  • Unlimited Pages
  • Client Delivery Pages
  • Webhook Notifications
  • Hosting on ncehost for up to 60 sites
  • Unlimited Export Retention
  • Priority Email Support

Prices: Free $0 · Pro $10/month · Agency $50/month · Site Pass from $15, paid once for one site.

Frequently Asked Questions

Everything you need to know about the export process.

Yes. NoCodeExport works from the public site and captures rendered pages, styles, scripts and reachable assets as a static front-end snapshot. It does not create an editable Squarespace template or export account-backed services.

The exporter aims to retain the rendered typography, spacing, responsive styles, navigation and reachable assets. Test each important page and breakpoint because complex blocks, embeds and external files can vary.

The export gives you portable rendered front-end files. Whether you can leave Squarespace completely depends on your use of Commerce, Member Areas, Scheduling, forms, email, domains and other hosted services.

Full-site export follows reachable same-site links up to three levels deep and within the selected plan's page limit. Unlinked, private and login-protected routes are not discovered automatically.

No. The exporter reads your site from its public URL, so you never share your Squarespace password. Private, password-protected and draft pages are left out.

You can test a public page on the free plan. Full-site scope, local assets, SEO options and deployment features depend on the current plan limits shown in the exporter and pricing page.

It's a WordPress-format .xml file with layout pages, text and image blocks, galleries and one blog, but no style settings, custom CSS or store pages; the comparison table above lists the rest. To keep the design, export the published URL here instead.

Can You Export a Squarespace Site? The Short Answer

Only partly, and not as a website. Squarespace's own export creates an .xml file meant for importing into WordPress (Squarespace Help Center, checked 29 September 2026). It carries layout pages, one blog with its posts, and text and image blocks; album, index, portfolio and store pages, page headers and footers, style settings and custom CSS do not export.

So Squarespace's export is a content transfer, not a copy of your design. To keep the site as it looks, export the published pages instead: this exporter renders each page in a browser and saves its HTML, CSS, JavaScript and assets, ready for any static host. Commerce, Member Areas, Scheduling and form processing run on Squarespace's servers and still need a replacement.

Why Export From Squarespace

A Squarespace site can combine public pages with hosted services such as Commerce, Member Areas, Scheduling and form processing. A static export is most suitable when the public content and design are stable.

NoCodeExport captures the rendered site from a public URL. It can reduce manual front-end copying, but migration still requires QA, service replacements, redirects and domain planning.

What Is Preserved in Exported Code

NoCodeExport captures your typography, spacing, and structural layout so your new static site stays visually close to the original Squarespace version. Responsive breakpoints and media queries are preserved.

Some exports reference remote assets. The local-assets option downloads reachable images and fonts, but large media, embeds and inaccessible third-party files may remain remote.

Deploying Your Exported Site

Once you download the HTML bundle, deploy it to Netlify, GitHub Pages, Vercel, Cloudflare Pages or another compatible provider under its current terms.

Measure the deployed result rather than assuming a speed gain. Review Core Web Vitals, metadata, canonicals, redirects, forms and asset paths before launch. Learn how other approaches compare by copying HTML code from a website.

Ready to export your Squarespace site?

Paste your published URL and review the pages. No payment is needed to scan.

Check my site