How to export a Studio Two site to React code and import it back
Updated: 6 hours ago
Export the site from the Studio Two menu in the editor or with the Wix CLI command wix origami export-site. Edit the React project locally, run the lint, then import it back with the import command. The import replaces the site with the exported version and does not publish it.
Status: Export and import are in beta according to the Help Center and in alpha according to the developer docs. Both say the feature may change.
Before you start
Node.js 24.18 or later.
The Wix CLI, installed and logged in to your Wix account.
The site export commands added to the Wix CLI with the origami flow.
A Studio Two site you can edit, or a new one created through the CLI.
Optional: a coding agent such as Claude Code or Cursor, or your own IDE.
Step by step
Finish editor changes first. An export is a one-time snapshot. Make any changes you need in the Studio Two editor before you export, because later editor changes are lost on import.
Export from the editor. Open the Studio Two dropdown at the top left, hover over Site, then Export/Import, and click Export Site Code. Choose Export to for a listed AI agent, Copy Prompt for an external agent, or copy the prompts into your terminal to work manually.
Or export with the CLI. Run wix origami export-site and follow the prompts to pick the site and a target folder. For scripts, pass the site and folder as flags: wix origami export-site --site <site-id> -d <folder>. The folder becomes a new git repository.
Install and preview. Install the exported site's packages, then start the preview. Open http://localhost:3000 in your browser. The preview reloads when you change files.
Edit the site. Open the project root in a coding agent, which reads the included instructions and editing skill. Describe the change in plain language. You can also edit the files by hand. Keep to the allowed props and CSS properties of each component, and put behavior in the code package.
Run the lint. In the project root, run yarn lint. It checks pages changed since the last passing run. Use yarn lint --full to check every page. Fix all errors and run it again until it passes. Warnings do not fail the run.
Run the import. In the editor, go to Studio Two, Site, Export/Import, then Import Site Code. Copy the command from the Import tab and run it in the exported site's root folder. The CLI must be logged in.
Upload missing images. If the import lists images that are not in Wix Media yet, enter y to upload them to the Media Manager. Images that are not in Wix Media do not display on the imported site.
Review and publish. Check the import output for the number of pages added and deleted. Open the site in the Studio Two editor and review it. Publish from the editor when you are satisfied.
Re-export before the next round. Export again in the project root before you make more changes. That way you work from the site's current version.
Good to know
Import deletes pages that are not in the exported site and overwrites Studio Two changes made since the export. Every page except the home page is deleted and added again, so it gets a new ID. URLs stay the same.
Re-exporting into the same folder replaces local changes. The CLI asks first and commits your local changes to git. You can also back up your work or export to a new folder.
Import does not change installed apps, CMS collections or other site data, and it does not publish. If the export has no code package, the site's code stays as it is.
Not supported yet: sites with dynamic pages cannot be exported. Member login does not work. Custom code that waits for visitor consent does not load. Lightboxes do not appear on the running site. Pages with widgets from installed apps, other than ERCs, fail in preview and build.
The Help Center states that site components and elements are currently not exported, and that style and layout come as css files and structure as jsx files. The developer docs describe a code package for ERCs and Data Sources. Check what your export contains.
Wix's feature list describes the export as a standard React project that you can work on with any AI tool or IDE before importing it back. The feature is still marked Beta.
parnii note
Try the full export, edit, lint and import round trip on a copy of the site first, since import overwrites pages and the feature is still in alpha or beta. Freeze editor work while the code is out, so nothing is lost on import.
FAQ
Can I host an exported Studio Two site outside Wix?
Yes. Building the site produces a Node server, which runs on any platform that supports Node. The site still loads fonts and media from Wix and calls Wix APIs for business features.
Does the exported code stay in sync with the editor?
No. The export is a snapshot from the moment you run it. To get later editor changes, export again, and back up or commit your local changes first.
Does importing code publish my site?
No. The import only saves the changes in the Studio Two editor. Review the result there and publish yourself when you are ready.
Sources
https://support.wix.com/en/article/studio-two-editor-exporting-and-importing-site-code-files
https://dev.wix.com/docs/studio-two/code-your-site/export-your-site/export-your-site-to-code
https://dev.wix.com/docs/studio-two/code-your-site/export-your-site/edit-an-exported-site
https://dev.wix.com/docs/studio-two/code-your-site/export-your-site/import-changes-to-your-site
Part of our Wix Studio Two series (Studio 2). Last checked: 06 November 2026.















