Export a Wix site to HTML: Wix has answered that one itself.
Your client has asked for their site files. Before you reply, read what Wix’s own help centre says you can take with you and what stays behind — dated, linked, and short enough to forward.
There is no site export. The help centre says so in a sentence.
Wix’s help centre has an article on exporting or embedding your site elsewhere. It does not describe an export. It explains why there is none: the site is built with Wix’s technology and “needs to be hosted and operated on Wix’s servers”. The alternatives it offers are a domain you connect to Wix and a domain you transfer to Wix. Both point inward.
What you can take is data, a piece at a time: collections and form submissions as CSV, uploaded media from the Media Manager, and the blog not at all.
- HTML and CSS of your pages
- No export. Runs only on Wix’s serversFAIL
- Images and files
- Uploaded media, by hand, from the Media Manager
- Form submissions
- CSV, from the submissions tablePASS
- CMS collections
- CSV per collection, every fieldPASS
- Blog posts
- “Not possible”, per the help centreFAIL
- The editor and templates
- Wix’s technology. Stays with WixFAIL
- Your domain
- Transfer away, or point its DNS elsewherePASS
Read from Wix’s help centre on 3 September 2026. The links are at the foot of the page.
What you actually send the client. Say it out loud first.
The email is polite. They would like the website files. On Wix the honest reply is a login: the pages exist only as a Wix site, and the route the help centre offers is to transfer a copy of the site to their Wix account — a second Wix site, with the original still sitting in yours.
So you send a spreadsheet of form submissions, a spreadsheet per collection, a folder of images you downloaded a few at a time, and the blog as a list of links, because it does not export. Then you explain that the design, the pages and the editor were never files. Most clients take this well. None of them forget it. Ask the same question on the other two and the answer changes shape: Squarespace sends an .xml file built for a WordPress importer, and Webflow sends a ZIP with the CMS content missing.
The question to ask before the next build is the one the client will ask after it: if this ends, what do I hand over? The Ownership test puts it plainly — not just “can you leave”, but can someone change the deal while you stay. A site that cannot leave fails the letter before anyone touches the deal.
What the fee bought that you can hand over: a login.
Rebuild it as a folder of files. Then there is nothing to export.
The owned stack is a folder of static files on hosting with a free tier, behind a strict content-security policy, making zero third-party requests at runtime. It has no export button because it needs none: the folder is the site. Copy it and you have a second one. Hand it over and the client has the whole thing, editor included, because the editor is a text editor.
Keep the domain. Wix’s article on pointing a Wix domain at an external site says to edit the DNS records in your Wix account, and notes that the name servers of a Wix domain cannot be changed. The transfer-away article gives you an authorisation code and up to seven days, subject to the sixty-day locks after a purchase or a contact change. Either way, the address printed on the client’s van stays the same.
Move the content in the order Wix lets it out. Collections and submissions arrive as CSV, and a static build reads CSV without complaint. Media comes out of the Media Manager, a selection at a time. The blog comes out the slow way, copied by hand, which is worth telling the client before you start rather than after.
Then run the release gate before anything ships. A banned phrase, a dead link, a claim nobody can source: the build fails and nothing goes out. The CODES test tells you where to build; the gate keeps what you built worth handing over.
A folder of files has nothing to export. That is the whole escape.
Every claim above, dated and linked.
Sources
- A Wix site “needs to be hosted and operated on Wix’s servers”; there is no export to another hostsupport.wix.comAccessed 3 September 2026
- Media Manager downloads: single files or a selection; not Board folders in bulk; not free stock mediasupport.wix.comAccessed 3 September 2026
- CMS collections export to CSV, all items and fieldssupport.wix.comAccessed 3 September 2026
- Wix Forms submissions export to CSV; dates and times in UTCsupport.wix.comAccessed 3 September 2026
- Blog posts: “it is not possible to export blog posts to other platforms”support.wix.comAccessed 3 September 2026
- Transferring a Wix domain away: the lock, the authorisation code, up to seven days; the Wix site is disconnectedsupport.wix.comAccessed 3 September 2026
- Pointing a Wix domain at an external site by editing its DNS records; the name servers cannot be changedsupport.wix.comAccessed 3 September 2026
- Transferring a copy of a site to another Wix account; the original stays in your accountsupport.wix.comAccessed 3 September 2026
Read the sharpest chapter first. It costs an email.
We’ll send the build-gate chapter in full: the checks, the code, and the reasoning. Read it. If it doesn’t change how you think about shipping client sites, you’ve lost ten minutes and kept a working release gate.
That did not send. Check the address and try again.