Our own website runs on Wix Headless. For most of our clients, we'd still pick Wix Studio 2.
Studio Two now writes React, exports code and takes in sites built in Claude. So when does a business still need a fully coded front end? Here's how we decide, with numbers from rebuilding our own site.

TL;DR
For most business sites, Wix Studio 2 is the better choice: visual design, editing in Wix, and React for custom features.
Wix Headless is for sites where the front end has to be custom code: unusual interactions, strict speed targets, or a team that wants every line of HTML.
Studio Two's export is in Beta and can't handle sites with item pages yet, so it doesn't replace a headless build today.
Our headless rebuild went from 64 to 99 for mobile performance, but that took a dedicated speed pass.
On Headless, every layout change is a developer job. On Studio 2, most changes are made in the editor.
Studio 2 or Headless: the short answer
For most business sites, Wix Studio 2 is the better choice. You design it visually, your team edits it in Wix, and custom features can now be written in React inside the editor. Wix Headless is for sites where the front end has to be fully custom code. That means unusual interactions, strict speed targets, or a team that wants to own every line of HTML.
We say that as an agency whose own website runs on Wix Headless. We chose it for features most client sites don't need, and the section on our rebuild below says which.
What is Wix Headless?
Wix Headless splits a site in two. Wix runs the back office: the dashboard, the CMS, the blog, bookings, forms and payments. The pages people see are written in code and talk to Wix through its APIs. Wix-managed projects usually use Astro, which gets SEO and logins built in. Other frameworks work with less done for you.
You can also host the front end yourself, on Vercel or similar. Then Wix gives you nothing for SEO automatically: no tags in the page head, no robots.txt and no sitemap. Your developer builds all of it. Our Headless SEO service covers that set-up.
What is Wix Studio 2?
Wix Studio 2, or Studio Two, is Wix's new professional editor, released to Wix Partners on 2 November 2026 and launched publicly on 10 November. You design on a visual canvas, Aria helps you build, and a Code tab gives you React, TypeScript and npm inside the editor. It can also export the site as a React project and import your changes back, which is in Beta. At the launch, Wix also showed Claude, connected to the Wix MCP, building a whole Studio Two site and bringing it in, so building with AI and code no longer has to mean going headless.
Studio Two's code tools and export now do some of what used to need Headless.
Wix Studio 2 vs Wix Headless, side by side
Wix Studio 2 | Wix Headless | |
How pages are made | Visual canvas, with Aria and React components where needed | Written in code (usually Astro on Wix-managed, any framework if you host it) |
Who changes the layout | A designer in the editor | A developer |
Who edits content | Your team, in the editor and the dashboard | Your team, in the Wix dashboard and CMS |
Wix business apps | Yes: Stores, Bookings, Blog, forms, CMS | Yes, through Wix's APIs. Some apps aren't supported, such as Wix's Reviews app and Wix Video |
Custom code | React and TypeScript in the Code tab | Anything your framework can do |
Backend limits | Fixed on every site: 300 millicores CPU, 400 MB memory, 60 second timeout | On Wix-managed hosting, server code runs as a Cloudflare Workers build. Self-hosted, it's your host's limits |
SEO set-up | Wix's SEO settings, as on any Wix site | Wix-managed Astro: Wix serves SEO tags, sitemap and robots.txt. Self-hosted: built by hand |
Owning the code | Export to React, in Beta. Not for sites with item pages yet | You own the front end from day one |
Hosting | Wix | Wix-managed, or your own host |
Can Studio 2's export replace a headless site?
Not yet. Studio Two's export gives you a React project you can edit with Claude, Cursor or any code editor, then import back. Wix lists these limits for now:
Sites with item pages can't be exported.
Lightboxes don't show on the exported site.
Member login doesn't work.
Some app widgets break the preview and build.
An exported site you host yourself still loads its fonts, media and business features from Wix. And an import replaces the site's pages, theme and code, so edits made in the editor since the export are lost. It's a promising route for small sites. It isn't a way to run a CMS-driven business site outside Wix today. Our guide to exporting a Wix Studio Two site to code has the details.
What we learned rebuilding our own site on Headless
Headless gave us features an editor makes hard, and it cost us extra work on speed and on apps that don't run headless.
Our site was designed on one canvas of 275 artboards, then built page by page in Astro. Wix runs the CMS, blog, bookings and forms behind it. It has two calculators, a chat-style brief builder and a live booking diary. Those are the features an editor makes hard, and they're why we chose Headless.
Speed took work. The first build scored 64 for mobile performance on the homepage. After a speed pass it scored 96, then 99 on the live domain, without cutting a feature.
Page (mobile, PageSpeed, 29 October 2026) | Performance score |
Home | 99 |
Blog post | 98 |
Wix SEO service page | 98 |
Blog index | 97 |
About | 96 |
It also took work Wix would normally do for us. We built our own reviews page and video library from the CMS, because Wix's Reviews app and Wix Video don't run on Headless. The full story is in how we rebuilt our own website on Wix Headless.
Which should you choose?
Choose Studio 2 for most business sites, and Headless only when the front end has to be custom code.
Your site | Choose | Why |
A business site with pages, a blog, a CMS and bookings | Wix Studio 2 (or Wix Studio) | Visual editing, no developer needed for layout changes |
A site with a few custom features | Wix Studio 2 | React components in the Code tab cover most of these |
A site built around custom tools, unusual interactions or strict speed targets | Wix Headless | Full control of the HTML, scripts and loading |
A site that has to live on your own host | Wix Headless, self-managed | Studio Two's export can't handle sites with item pages yet |
A site that relies on Velo today | Stay on Wix Studio for now | Studio Two has no Velo, and Headless is a full rebuild |
What does each cost?
Wix Headless is free to start, but taking payments and using a custom domain need a Wix premium plan. Our Wix Headless builds start from £5,000 + VAT, because a developer builds every page. Our Wix Studio sites start from £2,500 + VAT.
The running cost differs too. Every layout change on a headless site is a developer job. On Studio 2, most changes are made in the editor.
If you're not sure your site needs a coded front end, book a free call and we'll tell you honestly. You can also see how we build on Wix Studio 2.
Sources: our post How we rebuilt our own website on Wix Headless (2 November 2026), About exporting your site to code, About backend compute limitations, Compare extending websites in Studio Two, Meet Wix Studio Two, About supported frameworks (Wix Headless) and Wix's 10 November launch event. PageSpeed scores from our performance log, 29 October 2026.
Frequently asked questions
Do I need to learn React to use Wix Studio 2?
No, not for design or content. Code is only for custom features, and Aria can write it for you to check. On Wix Headless, someone on the team needs to code.
Can I export a Wix Studio 2 site and host it myself?
Partly, in Beta. You can export a React project and build a Node server, but the site still loads media, fonts and business features from Wix. Sites with item pages can't be exported yet.
Is Wix Headless better for SEO than Wix Studio 2?
Not by itself. On Wix-managed Astro, Wix serves the SEO tags and sitemap, and the rest depends on how the pages are built. Self-hosted headless sites start with no SEO set-up at all. See our Headless SEO service.
Is Wix Headless faster than Wix Studio 2?
It can be, because you control every script, but speed takes work. Our first headless build scored 64 on mobile before a speed pass and the move to the live domain took it to 99.





