Exporting a Wix Studio Two site to code: what works and what doesn't yet

Wix Studio Two can export your site as a standard React project, and import your changes back. As of November 2026 the feature is in Beta, and Wix says it may change and have bugs. It's useful if you want to edit a site with a coding agent, or host the frontend yourself. It also has real limits, the biggest being that sites with item pages or pages with repeaters can't be exported yet.

Why would you export a Wix site to code?

Wix suggests three reasons. You might want to build in Wix but host on your own infrastructure. You might want to bring in work made elsewhere, such as a Figma design or pages built with Claude. Or you might want to edit the site in an outside AI tool or code editor and import it back. Studio Two sites are built as React code, so most platforms that handle React can read and host what you export.

How do you export a Studio Two site?

In the editor, open the Studio Two menu at the top left, then Site, then Export/Import, then Export Site Code. You get three options: open an AI agent on your computer with the prompt already filled in, copy the prompt for another agent, or run the commands yourself in a terminal.

To do it by hand you need:

1. Node.js 24.18 or later.
2. The Wix CLI, installed and logged in to your Wix account.
3. The export commands, added with wix flows add origami. Running the same command later updates them.
4. Then run wix origami export-site, pick the site from the list and choose a folder.

There's also wix origami create-site, which makes a blank Studio Two site and exports it in one step. It doesn't publish the new site.

What's in the exported folder?

The export is a new Git repository, set up as a Yarn workspace with two parts:

• packages/site-app holds the pages, header and footer, menus and theme.
• packages/site-code holds your custom code, such as React components and data sources, if the site has any.

Wix also ships files for coding agents: AGENTS.md and CLAUDE.md with instructions, an editing skill, a component catalogue, and a contract file for each component listing the props and CSS properties it accepts. We think that's the clever part. An agent can only change what each component allows, which keeps imports from failing on something the editor can't handle.

If the site doesn't already have one, the export also creates an OAuth app called "export site", which the exported code uses to call Wix APIs.

To preview, run yarn install, then yarn dev, and open localhost:3000. The preview reloads as files change, and each page file becomes a route.

How does importing work?

Run yarn lint first. It checks your changes against the import's rules, by default only on pages changed since the last passing check. Add --full to check every page. A pass means the import will probably work, but the import itself is the final test.

Then run npx wix origami import-site from the export's root folder. The CLI offers to upload any images that aren't in Wix Media yet. Images you don't upload won't show.

What does an import replace?

Read this before you run one:

• The whole site. Your exported version replaces it. Edits made in Studio Two since the export are overwritten, and pages added in the editor meanwhile are deleted.
• Page IDs. Every page except the homepage is deleted and re-created with a new ID. Wix says the URLs stay the same. Popups get new IDs too.
• Sections, menus and theme. All replaced. The site's code is replaced by your code package if you have one, and left alone if you don't.
• Not apps or CMS collections. Wix says import doesn't touch installed apps, collections or other site data.
• Not publishing. Import only saves the changes in the editor. You review and publish yourself.

An export is a snapshot and doesn't stay in sync with the editor. After each import, export again before you make more changes. If you export into the same folder, your local files are replaced. Wix's developer docs say the CLI asks first and commits your local changes to Git, but the Help Center still recommends a backup or a new folder, and so do we.

What doesn't work yet?

As of November 2026, Wix lists these as not supported:

• Sites with dynamic pages can't be exported at all. In Studio Two that means item pages and pages with a repeater.
• Popups (lightboxes) are exported but don't show on the running site.
• Pages with widgets from installed apps, other than React components, fail in preview and build.
• Visitors can't log in as members.
• Code that waits for cookie consent, such as analytics or marketing tags, doesn't load.

The first one rules out a lot of business sites. If your site has a CMS-driven list, portfolio or catalogue, export isn't an option yet.

Can you host an exported site yourself?

Partly. Building the export gives you a Node server that serves every page and the 404 page, and it runs on any host that supports Node. But the site still loads fonts, media and business features from Wix. Wix describes it as a frontend you host for a site that Wix still runs. So it isn't a way to leave Wix.

If you want a fully custom frontend on top of Wix's business tools, that's what Wix Headless is for, and Wix's own frontend docs point there too. See our Wix Headless service, or talk to our Wix development team about an export and edit workflow. For everything else about the new editor, see our Wix Studio 2 service.

Questions people ask

Is Studio Two export the same as Wix Headless?

No. Export gives you a Studio Two site as React code you can edit and import back, or host as a frontend. Wix Headless is for building your own frontend from scratch on Wix's business APIs.

Does importing publish my site?

No. Import only saves the changes in the editor. You check them and publish when you're ready.

Will importing change my URLs?

Wix says URLs stay the same, even though most pages are re-created with new IDs. After an import, check anything that relies on page IDs, such as custom code.

Can I export a Wix Editor or Studio Editor site?

Export and import are documented for Studio Two sites only.