Book an inspectionInspection
Squarespace
HTMLAstroVite
Squarespace page + styles → source project

Bring your Squarespace design
into your next codebase.

Capture public page markup and available styles, images and fonts. Start your rebuild with the front end that a content-only XML export does not carry.

Free · no account · nothing changes on your live site

Use a published, publicly accessible page on your site. Password-protected pages and the Squarespace editor are not accessible.

What comes with you

Your Squarespace front end

  • Public page structure

    Server-provided HTML, text and layout markup as editable source files.

  • Available CSS and assets

    Linked stylesheets, fonts, images and CSS background resources that can be downloaded.

  • A design migration reference

    A runnable project plus a list of detected scripts, forms and embedded services to inspect.

Plan the rest of the move

Replacements to build

  • Editable Squarespace blocks

    Captured markup does not recover the Fluid Engine editor or its block configuration.

  • Forms and store behavior

    Review submissions, cart/checkout, scheduling and other services your site uses. These need their own replacements.

  • Content outside the sample

    Use a separate content export for your archive. This captures only the linked public pages within your selected cap.

Squarespace documentation on export exclusions
Built for the move

Your Squarespace move,
one step at a time.

  1. Pick a page with your core styling.

    Capture a landing page that includes your typography, navigation and important layout sections.

  2. Review the local design files.

    Open the project in your editor and compare the captured page and available CSS with the live site.

  3. Move content and services separately.

    Use the source files as your rebuild reference. Plan forms, commerce and content migration before changing hosting.

Questions,
answered.

Can't find what you need? You'll get an answer from an engineer within a day.

Talk to us
How is this different from Squarespace XML export?

Squarespace XML transfers selected content. This tool captures the public front-end markup and available design assets to help you rebuild the presentation in a code project.

Will the result include every animation and block?

Only what is available in fetched HTML and downloaded assets. JavaScript-rendered sections and platform-backed interactions can still require manual work.

Will I get the original PHP code, CMS database or a React rewrite?

You get the public front-end HTML, downloaded assets and a runnable project structure. PHP source, database content, user accounts and CMS workflows cannot be recovered from a public URL. Astro and Vite outputs retain editable HTML; they are not generated component rewrites.

Can the exported project work without the original hosting?

Downloaded assets and copied pages can be served locally. CSS imports, fonts and background images are followed and localized when available. Missing assets remain remote, while forms, embedded services and runtime scripts may still depend on the old host. The report identifies detected dependencies so you can rebuild them.

How much can I export free?

Choose one, three or five linked public pages. Each project is capped at 100 asset attempts, 5 MB per asset, 2 MB per page and 25 MB total fetched data. Query-based pages are kept distinct. Pages and assets beyond the caps are listed in the report. No account or card required; request limits apply.

Explore website to code export →