For my first week with Wix Studio Two, I have mostly been doing import work: somewhere around 40 to 50-plus hours moving my templates in with the new import and export tool. I have barely played in the editor itself yet, so this review is shaped by that work.
I have waited a long time for this editor, and I am excited about it. I also want to be honest. I have not moved a single template all the way over yet. Part of that is volume, with 76 templates to move plus new ones. Part of it is that the import tool is in beta, and early beta has rough edges.
What Studio Two is
Studio Two is Wix's new editor for professional web creators. Wix calls it "the deepest visual editor, open to any agentic workflow." It pairs a full visual editor and Aria, Wix's AI assistant, with a Code tab that runs Visual Studio Code in the browser.
Studio Two is rolling out now, and Wix has a live announcement scheduled for tomorrow, November 10, at 12pm EST. Sign up for the Studio Two event here. It already sits next to Harmony and Headless in the Wix Studio workspace. Before launch, I shared what I expected in Studio Two (Wix Studio 2): What to Expect Nov 10.

What I already like
- It is open. Export a site, work on it with Claude Code, Codex, Cursor or any agent you like, then bring it back. For a Wix editor, that is a big shift.
- Real code when you need it. The Code tab means custom features no longer mean leaving Wix.
- Custom components work. Aria built a working one for one of my sites.
- Everything in one place. Studio Two, Harmony and Headless sit side by side, so agencies can pick the right tool per client.
Aria itself has been a mixed experience so far. It built that component, and other requests took a few tries. I want to see everything it can do, and I will test it properly once my templates are in.
How the import and export tool works
The tool is in beta. In the editor it lives under Site, then Export/Import, and the export window offers to send your site straight to Claude Code, Codex or Cursor, or to copy a prompt for any agent.

- Export the site, or run wix origami export-site. You get the whole site as a React project in a folder.
- Edit it with an AI agent. After each change, yarn lint checks whether the import will accept it.
- Import it back with npx wix origami import-site.
- Review and publish in the editor. Import never publishes on its own.
Use the AI tool you like
You can work on the export with whatever AI tool you prefer. I use Claude Code on Claude's Max plan, and the import work took a lot of it: somehow I hit 78% of my weekly usage on the first day of the week. I think part of that was on Claude's side, and part was how I worked at first. I later built a more efficient system, moving from Claude Opus 5.5 to Sonnet 5.5, with smaller Haiku 5.5 agents handling the routine steps.
I also tested a local model, Qwen 3.8 27B, running on my M4 MacBook Pro with 48 GB of memory. It did a good initial build of a site, then fell apart when adding the other pages. I will keep fine-tuning it, because a capable local model would make this kind of work much cheaper.

What import does
Know what import does first. It replaces your pages, header, footer, menus and theme, deletes any page not in the export, and overwrites editor changes made since you exported. Apps and CMS data are not touched, and sites with dynamic pages cannot be exported.
I had already rebuilt my Wix Studio templates as Wix Headless sites, so I brought those designs in. That turned out to be lucky: I found no official tool that moves a Wix Studio site into Studio Two, so without the headless project this would have been even harder.
What tripped me up
None of this is unusual for an early beta. Wix is clearly working hard on Studio Two, and I expect most of it to get easier quickly. I will update this post as these get fixed.
Add the tablet breakpoint first
An import cannot add a breakpoint. Without a Tablet breakpoint, the phone layout stretched across tablet widths and broke, even though the local preview looked fine. Now every site gets its Tablet breakpoint in the editor before the first import, and we check every page at five widths.

I was really hoping to see every breakpoint at once, side by side. Switching between them one at a time makes checking dozens of pages slow.
I also move my templates to Framer, where every breakpoint comes in with the build. That is why breakpoints from import is my top wish for Studio Two.
The preview is not the editor
The local preview is a good first check, not the final word. Our worst surprises only showed up on the Wix side, including one site that published blank because of a single style rule. Removing it fixed it.
Publish a test early, and check that the live page actually shows your content. A successful publish is not the same as a working page.
Errors and limits
A passing lint does not always mean a passing import. Some refusals just said "Transaction was not approved," and the only fix was splitting the build in half until one half failed. We also found limits by running into them: an import that has to delete more than 10 pages is refused, apps can add pages that push you over it, very large pages time out, and the export refused a folder path with a space in it.
Hand work after import
Imported headers and menus came through differently from the source, and one header would not go transparent after import, which I have reported to Wix. Some animations did not carry over, so we used the closest native ones. Data is its own job too: we reseed CMS collections, install apps ourselves, and connect dynamic pages by hand. My real estate app, Showings to Closing, installs fine, but its widget is placed in the editor.
Custom components and content mode
When I brought Hart Homes over, its home search bar came through as a plain stack of elements. So I asked Aria to build a custom component with the same function, and it now shows up in the editor as its own Home Search element. I have not finished it yet, but it is a promising start.

I also wish content mode got more love. It lets clients and template buyers update text, images and buttons without touching the design, and I wrote a full guide on it: How to edit your Wix Studio template in content mode. AI and content mode make a lot of sense together. Editing in content mode works well in Studio Two, but right now you can only open it from inside the editor, not from the dashboard. I am sure that comes back quickly.

What I miss from Wix Studio
Every new editor takes time to catch up with the last one, and Studio Two is just now rolling out. These are a few Wix Studio features I rely on that I have not found in it yet:
- Repeaters with their own items. I used them constantly to keep designs consistent. In Studio Two repeaters have to be connected to data, which also caused import errors before I found out why.
- Expressions with data. I used them on my real estate sites to show prices with a dollar sign and commas.
- Custom member pages. That is how I built the first version of my own web app, allioo.com.
I expect these to arrive as Studio Two grows, and I will update this post when they do. I will go deeper on each in a follow-up post.
Why not MCP?
Wix already has an MCP server, a standard way for AI agents to work directly with a platform. Its docs say agents can search Wix's documentation, write code, make API calls and do things like create and publish sites, and Wix's announcement says MCP lets agents "manage nearly every aspect of a website and its business." What I did not find is a way to edit a page's design through it. In Framer, our agent built pages directly through Framer's MCP, every breakpoint included, with no export or import step.
Wouldn't MCP be faster and more seamless for design? I am sure Wix has their reasons, since a code export works with any agent and can be reviewed before it goes live. I was just wondering, and I would love to see both. More on this in a follow-up post.
Will this be Wix's last Studio editor?
The same question matters for agencies. Many already moved client sites from Editor X to Wix Studio, and now there is Studio Two. Wix says existing Wix Studio sites remain supported, which is good to hear, and every new editor still means some rebuilding and retraining. Framer and Webflow ship big updates inside the same editor.
I believe Studio Two is set up to work that way. It is built on the same foundation as Wix Harmony, which feels like a base meant to be updated, not replaced. That is my hope.
The other open question is the template marketplace. I do not know when it opens, and I hope Wix keeps a high bar, so it does not fill up with weak, AI-only designs.
Getting back to designing by hand
I have not designed a site by hand in over five months. I have gotten a lot better at designing with prompts, but I believe the skill and the eye for good design still matter. Many AI-generated sites still look AI-generated.
Designing by hand does not feel as appreciated as it used to, and I am looking forward to it anyway. I think building by hand, with AI beside me, will help me make even more creative sites, and I especially want to play with Brik's 3D models in Studio Two. Once my templates are in, Studio Two is where I will start my new builds.
Why I am betting on Wix
I think Wix is in a great position. Studio Two, Harmony and Wix Managed Headless cover professionals, people who want AI to do more, and custom builds, all on top of Wix's business tools.
Wix is moving fast on AI, too. It bought Base44, an AI app builder. It has Wixel for AI design, Symphony by Wix for AI agents that help run a business, and Brik's 3D library coming to Studio Two. It has even built its own AI models, including one that powers Harmony's design engine. These are steps to stay not just relevant but ahead.
I am betting on Wix to be a leader in AI web design, and I think it can do even more once all of these pieces are more aligned and integrated.
What I would love to see next
I am sure Wix will work out the kinks and launch guides that make all of this easier. My wishlist from week one:
- Breakpoints from import, and a view of every breakpoint at once.
- Clearer import errors, and a lint that catches what import will refuse.
- Documented limits, and a check before a page publishes blank.
- Dynamic pages and app widgets in export.
- Design editing through MCP, alongside the export.
- Static repeaters, data expressions and custom member pages.
- More content mode, including opening it from the dashboard.
- A marketplace plan, with a date and review standards.
Where things stand
After week one, I am excited about Studio Two. Getting my templates in has been harder than I hoped, and that is what an early beta is for. The tool works, I can see where it is going, and I am sure it will get easier. For now, plan on some hand work after each import, especially the header, the menu and the tablet layout. I will keep this post updated as Wix rolls out fixes and new features.
My templates are coming soon for both Wix Headless and Studio Two. See them now at allioo.studio/templates and get notified when the one you want is ready.

Questions
Can I import a site into Wix Studio Two from code?
Yes. Export a Studio Two site, edit it, and import it back with the Wix CLI. The feature is in beta.
Does importing publish the site?
No. You review the imported site in the editor and publish it yourself.
Does the import add a tablet breakpoint?
No. In my experience, add the Tablet breakpoint in the editor before your first import.
Can I export a site that has dynamic pages?
No. Wix's docs say sites with dynamic pages cannot be exported.





