Website Builders: What You Can Export and What Has an API
A website builder makes the first day easy. The question that matters comes later: if you want to leave, what can you take with you? This guide puts two questions side by side for five builders, using each one’s own help pages: what the platform lets you export, and whether it has a public API for reading your own data.
The order is alphabetical. It is not a ranking, and it is not a score. Where a public page did not answer the question, the guide says “could not verify” instead of guessing.
Carrd
Carrd lets you download a site only on the Pro Plus plan or higher. The download is a zip file with unminified HTML, CSS and JavaScript source code.
Two limits come with it. Forms do not work in the downloaded copy, and a downloaded site cannot be uploaded back to Carrd. As for a public API, we could not verify one from Carrd’s public pages, so this guide makes no claim either way.
Durable
For this builder, we could not verify either answer from its public pages. We found no clear statement of what an export contains, and none about a public API.
That is a gap in what we could check, not a finding that it has no export or no API. If either matters to you, ask its support team before you build, and ask for the answer in writing.
Squarespace
Squarespace exports to a single .xml file in WordPress format. It includes layout pages, one blog page with all its posts and up to 1000 comments per post, text blocks and image blocks.
It does not export other page types (albums, cover, index, info, calendar, portfolio and store pages), more than one blog page, product blocks, drafts, styles or custom CSS. On the API side, Squarespace has public Commerce APIs that read and write orders, products, inventory and transactions.
Webflow
Webflow exports your HTML, CSS, JavaScript and images, but only on a paid Workspace plan. The Site plans do not include it.
The export leaves out CMS content, user accounts, e-commerce, form handling, site search, password protection and localized content. CMS content, e-commerce and user accounts can be exported separately as CSV. Webflow also has a public REST API covering the CMS (create, edit and publish items), pages, domains and publishing, custom code and webhooks.
Wix
Wix’s help page says blog posts cannot yet be exported to another platform. It is listed as a feature request that Wix is collecting votes for. We did not check the other parts of a Wix site, so this guide says nothing about them.
Wix does have a public API, the Wix Data APIs. They let you access and manage the data in your site’s database, and the site’s code editor has to be turned on to use them.
Side by side
| Builder | Export | Public API |
|---|---|---|
| Carrd | Zip of HTML, CSS and JavaScript source; Pro Plus or higher; forms do not run; cannot be uploaded back | Could not verify |
| Durable | Could not verify | Could not verify |
| Squarespace | One .xml file in WordPress format: layout pages, one blog with posts and up to 1000 comments per post, text and image blocks | Yes: Commerce APIs |
| Webflow | HTML, CSS, JavaScript and images; paid Workspace plan only; CMS, e-commerce and accounts export separately as CSV | Yes: REST API |
| Wix | Blog posts cannot be exported yet; other parts not checked | Yes: Wix Data APIs, code editor must be on |
Before you choose
Before you choose a builder, find its help page on exporting a site and read two things: what the export contains, and which plan it needs. Then look for a public API page. Write down the date you checked, because help pages change.
Treat “could not verify” the same way: it is a question to put to the builder, not a yes. If you already run a site and are weighing a move, see when to switch tools. For how costs grow with a team, see the real cost of per-seat pricing.