Can you download your Wix website? What actually comes out
There is no HTML export from Wix — the site has to run on Wix's servers. But your media, your CMS collections, your contacts and your domain are all portable. Here is exactly what leaves, what does not, and the order to do it in.
If you have searched for how to download your Wix website, you have probably already found the answer and hoped it was wrong. It is not. But "no export" is not the same as "nothing comes out", and the difference is a few hours of work rather than a lost site.
Everything below is from Wix's own help centre, checked in September 2026.
Why there is no download button
Wix's position is stated plainly in their docs: the site is built with Wix's technology, and it has to be hosted and operated on Wix's servers to work. Their words for the limitation are that a SaaS architecture does not support external hosting, because it relies on Wix's own services to run.
The same page is equally plain about ownership: the content you build on Wix belongs to you. Both things are true at once. You own the words and the pictures; the thing that turns them into a website is not yours to take.
What you can actually get out
Your media. The Media Manager will download your uploaded files, one at a time or in bulk. Do this first — it is the part that is genuinely yours and genuinely portable, and it is the slowest to recreate.
Your CMS collections. A Wix CMS collection can be exported to CSV. If your site is a directory, a menu, a product list or anything else built on a collection, that structured data comes with you.
Your contacts. They live in the CRM side of the account rather than the site, and they matter more than the pages.
Your domain. A domain bought through Wix can be transferred out, and a domain held elsewhere was never Wix's. This is the single most important asset on the list: it is what your links, your listings and your search results point at.
What does not come out
The pages and the design. No HTML, no CSS. What you can take is what you can see.
The blog. This one surprises people. Wix can import posts from WordPress, and it can import from another Wix site. Exporting posts to another platform is, at the time of writing, an open feature request in Wix's own help centre — listed as collecting votes, which is Wix's way of saying not yet.
So if you have written seriously on a Wix blog, budget real time for it. Copy the text out by hand, or pull it from your live pages, and keep the URLs — you will want them later.
The order that wastes the least time
- Download the media. Everything else is faster if the pictures are already on your machine.
- Export every CMS collection to CSV.
- Copy the writing out, page by page, with its URL next to it. A spreadsheet is fine.
- Export contacts.
- Rebuild the site somewhere that will give you the files this time.
- Then, and only then, move the domain. The old site keeps working until you point it away, so there is no reason to be offline in the middle.
- Redirect the old URLs to the new ones before anyone notices they moved. That is its own job and there is a short guide to it here.
A site you can download, because it was always yours. Static HTML and CSS on your own hosting. Nothing to export, because nothing was held. DragGo vs Wix.
The useful thing to take from this
A rebuild sounds worse than it is. Most small sites are five to ten pages, and the part that took longest the first time — working out what the site should say — is already done. You are not starting from a blank page. You are re-typesetting a finished one.
The question to ask of the next builder, before you commit a second time: when I leave you, what do I leave with? Some of them answer it well.
DragGo's answer is that there is nothing to export, because the files were always yours — the editor writes plain HTML and CSS you can host anywhere, and the download is the site.