Discover public pages from site links and the sitemap.
Example: https://your-site.squarespace.com
Commerce, scheduling, forms, member areas, and dynamic collections need separate integrations. Next.js export is in development.
What a Squarespace HTML export includes
FNJ captures the public Squarespace pages that visitors can open, with reachable styles and images. You get a static snapshot for editing or self-hosting, not access to Squarespace's template editor or site database.
How to convert a Squarespace site to HTML
- 01 / Paste a public URL
Use a published Squarespace page you own or are allowed to convert. A private project link cannot be captured.
- 02 / Choose the scope
Capture one page, or discover linked public pages and pages exposed in the site's sitemap. Review the capture report for omissions.
- 03 / Preview and export
Check the HTML preview, then edit, download or deploy the captured files according to your FNJ access.
What FNJ captures
FNJ saves public page markup and accessible styles, images and other assets. You can capture one page or let it discover linked public pages. Uncopied assets and external scripts may still load from the original service.
Before you publish
Compare the preview with your published site, including galleries and mobile layouts. Check whether image blocks, menus and embeds still load from Squarespace. Move scheduling, forms, store and member flows separately before changing the domain.
Squarespace migration checks
A static export captures public pages, not the builder account or its hosted workflows. Check these before directing visitors to the new host:
- Open galleries and image blocks on phone and desktop.
- Check event, scheduling, member and store links for remaining Squarespace dependencies.
- Complete a test booking or purchase with your replacement service before changing the domain.
Keep your pages findable after the move
Keep important URLs and page titles where possible. If a path changes, redirect its old URL to the matching new page. Review canonical URLs and your sitemap on the final domain, then check indexing and crawl errors in Search Console. The export cannot guarantee that a search ranking will stay the same.
Follow the edit and deployment guide →Squarespace to HTML: export and hosting FAQ
- Will Squarespace commerce move with the HTML?
- No. Store pages may appear visually, but products, cart, payments and orders remain in the original service unless you rebuild them.
- Are member-only pages captured?
- FNJ fetches only publicly accessible pages. It cannot sign in to copy restricted content or membership rules.
- Do future Squarespace blog posts appear in my HTML export?
- No. The export is a snapshot of captured public pages. Publish new content in your chosen code or CMS workflow; later changes in Squarespace do not automatically update it.
- Can I edit the Squarespace HTML and CSS after downloading?
- Yes. The captured HTML, CSS and accessible assets are editable files. Work in your code editor or use supported FNJ MCP tools with a connected agent. The export is a snapshot; changes made later in Squarespace do not automatically sync.
- Can I host the Squarespace HTML export on Cloudflare?
- You can deploy the static files to your own Cloudflare account or another compatible static host. Preview every page and reconnect hosted forms, payments and other services first. A GitHub repository can hold the source files; pushing code is separate from configuring its hosting.
- Is the Squarespace converter free or does it need an account?
- Converting requires a signed-in FNJ account and the access shown in current FNJ pricing. You can read this guide without signing in. Check the pricing page for current purchase terms; no builder subscription or private account access is used to fetch public pages.
Need the next step? Connect your agent through MCP, copy a site editing prompt, or check current FNJ pricing.
Where to take your Squarespace HTML
Host your Squarespace HTML export on Cloudflare
Deploy Squarespace HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Squarespace HTML code to GitHub
Put your Squarespace HTML export in your own GitHub repository. Choose the right files, review the fnj-export branch and plan updates and hosting.
Follow the workflow →Make your Squarespace export work for you
Practical guides for editing the captured HTML, reconnecting services and checking the result before launch.
Edit with MCP →
Connect an agent to FNJ MCP, inspect the correct route, change content and review the draft before publishing.
Reconnect forms →
Audit form actions, connect your own submission service and verify delivery, validation and error feedback after moving hosts.
CMS & content →
Separate captured article pages from the original CMS, inventory content and choose a tested publishing workflow for future updates.
URLs & SEO →
Map old and new routes, check canonical tags and metadata, test redirects and review indexability on the final domain.
Mobile layout →
Compare narrow and wide previews, fix overflow and navigation, and verify touch, keyboard and reduced-motion behavior.
Images & fonts →
Find failed asset requests, correct relative paths, inspect external dependencies and preserve typography on the new host.
Export troubleshooting →
Separate URL access errors, capture limits, missing content and deployment problems using a small reproducible conversion.
Explore related converters