Can I Export My Website From My Website Builder?
It depends on which of four separate things you mean by "export." A website builder can let you export your blog posts while refusing to export your page layouts, or let you export your product catalog while keeping your design locked to its own servers. "Can I export my site?" is really four questions: can I get the source code, can I get my structured content, can I get my data (orders, forms, customers), and can I take my domain with me? Below is what each builder's own documentation says about each one, checked September 2026. Where a vendor documents nothing, the cell says "Not documented" rather than guessing.
What are the four kinds of export?
- Source code / HTML export — a file you could put on any static host and have the site work.
- Structured content export — posts, pages, or products in a reusable format (XML, CSV, JSON), not the design.
- Data archive — orders, form submissions, customers, or members, separate from page content.
- Domain portability — whether you can point the domain elsewhere or move its registration out.
What can each builder export?
| Builder | Source code / HTML | Structured content | Data archive | Domain portability |
|---|---|---|---|---|
| Squarespace | Not available. No HTML/CSS export; custom CSS is excluded even from content export (Squarespace) | One blog page (posts + up to 1,000 comments each), layout pages, text/image blocks export to an XML file for WordPress. Store, cover, album, index, portfolio and calendar pages are excluded, and you can't import the file into another Squarespace site (Squarespace) | Commerce orders export to CSV (Squarespace); image files are not bundled with the site export, and Squarespace recommends downloading them manually (Squarespace) | Domains registered through Squarespace can transfer to another registrar; the transfer doesn't cancel your site subscription and can take up to 15 days (Squarespace) |
| Wix (Editor/Studio) | Not available. Wix says the site "must run on Wix's servers"; there's no HTML/CSS export button (Wix) | CMS ("Content Manager") collections export to CSV, one collection at a time, with the option to export just the field structure (Wix) | Contacts, orders and invoices export from their own dashboards; uploaded media downloads individually from the Media Manager, not in bulk (Wix) | A domain bought through Wix can transfer to another registrar once unlocked; a 60-day ICANN lock can apply after registration or a contact change (Wix) |
| Webflow | Workspace (paid) plans only: HTML, CSS, JS and media-library assets export as a zip you can host anywhere, no attribution required. CMS, ecommerce, user accounts, code components, and localized content are excluded (Webflow) | CMS Collections, Ecommerce Collections and User Accounts export to CSV, one Collection at a time; image and file fields export as links to the old project (Webflow) | Existing form submissions are not in the code export and are exported separately (Webflow); our Webflow code export guide covers the rest | A domain registered elsewhere connects by DNS records and can be repointed at your registrar |
| WordPress.com | No site-code export. SSH/SFTP file access comes with the Business and Commerce plans, not Personal or Premium (WordPress.com) | Posts, pages, comments, categories and tags export as an XML/WXR file; media is linked, not included as files, and theme, customizations and plugins are excluded (WordPress.com) | Media library downloads separately as a .tar archive organized by year and month (WordPress.com) | Domains transfer out via an authorization code with roughly a 5-day wait; confirming the outgoing transfer can speed it up (WordPress.com) |
| Self-hosted WordPress | Full access. You (or your host) control every theme, plugin and core file directly | Built-in Tools → Export produces the same WXR/XML format as WordPress.com (WordPress.org) | Full database access via your host's backup tools or a plugin; nothing is withheld by the software itself | Registered wherever you chose; portability depends only on that registrar, not on WordPress |
| Shopify | Theme files download as a zip from Online Store → Themes → Download theme file, but the files are Liquid templates that need Shopify's rendering engine — they won't run as static HTML elsewhere (Shopify) | Products export to CSV, with images excluded from the file and sorting in a spreadsheet risking broken variant/image links (Shopify) | Order/customer exports are available for backup or tax requests via the Data Exporter app; discount codes and issued gift cards can't be transferred this way (Shopify) | Shopify-managed domains transfer out after an automatic unlock and an authorization code; up to 7 days, and the domain re-locks if the transfer isn't finished within 30 (Shopify) |
| Framer | Not available. Framer says published sites depend on its backend services for performance and optimization, so they "cannot be exported as standalone HTML files for self-hosting" (Framer) | Not documented as a native feature | Not documented | Domains you own connect by DNS (A/CNAME records you add at your registrar); nothing about Framer prevents repointing them later (Framer) |
| Square Online (Weebly) | Not available. Weebly sites in 67 countries are unpublished on September 27, 2026, with account access until December 26, 2026; see our Weebly shutdown guide | See our dedicated Weebly blog export guide for what the blog export includes | Order history exports to CSV, Excel, Numbers or QuickBooks (Weebly) | Domains transfer out after unlocking and retrieving an EPP/authorization code; a 60-day lock can apply after registration (Weebly) |
| GoDaddy Websites + Marketing | Not documented. GoDaddy publishes no HTML/CSS export path for this builder | Not documented beyond commerce data below | Store products, customers and orders export to CSV (GoDaddy) | As a domain registrar, GoDaddy documents a standard transfer-away flow with an authorization code; 5–7 days, with 60-day locks after registration or bundled discounts (GoDaddy) |
| Carrd | Yes, on Pro Plus or higher: unminified HTML, CSS and JS download as a zip. Elements that need Carrd's platform, most notably forms, won't function in the download, and the download can't be re-uploaded to Carrd (Carrd) | Not applicable — Carrd sites are single-page, with no CMS to export | Not documented; form submissions typically forward to email or a connected service rather than storing in Carrd | You register the domain elsewhere and point DNS at Carrd; disconnecting is just removing those records at your own registrar (Carrd) |
| Google Sites | Not a hostable export. Google Takeout exports site content (pages, embeds, navigation, themes) in Google's own archive format, not deployable HTML (Google) | Included in the same Takeout export; Google documents no separate structured-content-only format | Not documented for Sites itself; Google Forms responses live in Forms/Sheets, not in the site | A custom domain registered elsewhere connects by DNS and can be repointed at your registrar |
| Hostinger Website Builder | Agentic ("Horizons") mode only: full project code downloads as a zip. Manual mode has no code export (Hostinger) | Manual mode exports pages, text and images to WordPress; style/layout, store, integrations, forms, submissions and SEO settings are explicitly excluded (Hostinger) | Not documented beyond the WordPress content export above | As a registrar, Hostinger follows the standard ICANN transfer-out process; check your account's domain settings for the authorization code |
| Ghost | Self-hosted Ghost: full source control, it's open source. Ghost(Pro): theme files download and upload as a zip (Ghost) | Posts, pages, tags, settings and staff users export as a single JSON file (Ghost) | Members export to CSV with fields including email, name, subscription status and Stripe customer ID (Ghost) | Ghost isn't a registrar; a custom domain connects by CNAME and repoints the same way at your own registrar |
| Lovable | Yes: Download codebase (paid plans, in Project settings → Git), or a two-way GitHub sync to a repository Lovable makes private by default (Lovable) | Not documented at the platform level — structured content usually lives in a connected backend (for example Supabase) that you already control | Not documented at the platform level, for the same reason | Custom domains connect via automatic (Entri) or manual DNS setup on paid plans; you can point Lovable-bought domains at your own nameservers instead (Lovable) |
| Bolt | Yes: Export → Download bundles the generated project as a zip (Bolt) | Not applicable — Bolt generates application code, not CMS content | Not applicable, for the same reason | Bolt now has built-in hosting and custom-domain management (earlier projects deployed through Netlify) (Bolt); a domain you own can be repointed at your registrar |
| v0 | Yes: Project menu → Settings → GitHub → Connect creates a private repository and pushes the project's code to it (v0) | Not applicable — v0 generates application code, not CMS content | Not applicable, for the same reason | Custom domains are added from Project menu → Settings → Domains and configured in the Vercel dashboard (v0) |
A pattern shows up once the columns are separated: closed hosted builders (Wix, Squarespace, Framer, GoDaddy, Square Online) protect the design layer and release only data and content. Code-based tools (self-hosted WordPress, Ghost, Lovable, Bolt, v0) release the code freely, because the code is the product. Webflow, Shopify, and Hostinger sit in between — real code or theme exports, tied to a runtime or plan tier.
What should I do before I cancel?
- Export every column separately. Don't assume a "content export" also grabs your orders, your form submissions, or your images. Check each one against the matrix above.
- Download your images yourself. Neither Squarespace's site export nor Wix's content exports bundle your image files, so budget real time for this if your site has hundreds of images.
- Get your domain's authorization code before you cancel hosting, not after. Several of these flows require an active account to request the code.
- Test the export before you need it. Open the XML/CSV/JSON file and confirm it has what you expect. A WXR file with links to media you never downloaded is not a backup.
- Screenshot what won't export. Custom CSS, page layouts, and closed-editor design choices in Squarespace, Wix, and Framer have no export path — a screenshot or a set of exported HTML pages from "View Source" is the only record you'll keep.
- Cancel in the right order. Keep the site live until every export is verified, then cancel hosting, then handle the domain separately if you're keeping it.
What if I'm leaving for good?
If your builder is one of the five with a dedicated Figment migration guide, start there instead of rebuilding this research: migrate from Squarespace, migrate from Webflow, migrate from WordPress, move from Wix to an AI website builder, and Weebly shutting down: save your site all cover the rebuild steps in detail.
None of this replaces checking your own account. Plans, regions and product tiers change what a given account can export, and a vendor can update a feature after this was checked in September 2026. Confirm the export in your own dashboard before you rely on it, and keep a second, independent copy of anything the platform calls irreplaceable.
