Paste your published Squarespace URL, pick the pages, and download a ZIP of HTML, CSS and JavaScript to test, edit or self-host.
//about/blog/*/pricing/contactCopy the address of your published site, not its editor. The page must open without a login.
The scan follows links up to three levels deep. Select the pages you need from the results, within your plan’s limit.
yoursite.squarespace.comYour 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.
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.
Supported navigation and page interactions are included. Blocks that use Squarespace services may need a replacement.
squarespace-export.zipUnzip the download and open the files through a local web server or temporary hosting. Check layouts, links, forms and animations on desktop and mobile.
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 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 need | Squarespace 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
These reads explain the XML limitation, compare export options, and walk through what to validate before switching hosts.
Export once with Site Pass, or choose Pro for regular updates and client projects.
One site to move. One payment. No subscription.
Features included:
Scan your site and review the pages before checkout.
A failed export restores your pass so you can retry.
Keep exporting as your sites evolve.
Features included:
Annual billing and Agency options. See all plans
Everything you need to know about the export process.
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.
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.
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.
Paste your published URL and review the pages. No payment is needed to scan.