Wix Studio Two vs Wix Studio: who should switch now and who should wait

2 days ago

9 min read

Updated: 2 hours ago

Wix Studio Two is not an update to Wix Studio. It's a separate editor on a new architecture, with React components instead of Velo page code, fixed backend limits and a first release that leaves out several things agencies use every day. It's a strong choice for design-led sites with custom components, and a risky one for member portals, deep integrations and existing Velo projects.

Status: Studio Two launches on 10 November 2026. Wix calls this the initial release and says more features are planned. Everything below reflects the developer documentation as of 4 November 2026 and Wix's official feature list for the editor as of 6 November 2026.

Updated 6 November 2026: we compared this article with Wix's official feature list for the Studio Two editor. The answers on custom CSS, the IDE and the infinite canvas are corrected, and Content mode and Multilingual are added.

Wix Studio Two vs Wix Studio: the short answer

Since the announcement, the same questions keep coming up in the Wix partner community: where is the Members Area, can I move my Velo site, does my favorite app work.

Most of them have one answer:

not in this release.

So before the details, here is how we'd decide today.

Start in Studio Two if

The site is design-led: a brand, campaign or marketing site
You want custom interactive blocks built in React
A store, blog, events or portfolio site needs your own blocks inside Wix pages
There is a React developer on the team

Stay in Wix Studio if

You need a Members Area, member roles or a client portal
You need deep Bookings customization or your own checkout
Other services send data to the site, or tasks run on a schedule
The site already runs on Velo code or Blocks apps
The backend does heavy work

A different way to build, not a newer version

The biggest change is invisible in the editor.

Studio Two has no $w API and no page code. Custom UI is built as Editor React Components:

React components with a manifest that tells the editor which parts a designer can change. The editor then builds the settings panels on its own, so a custom component feels like a native Wix element.

Code tab of the Studio Two editor with a React component file open in the code editor — A React component in the Code tab of Studio Two. Image: Wix

Shared state lives in Data Sources: invisible components with no UI of their own that hold data and actions, such as the current product, a search filter or a list of results. A designer attaches a Data Source to a page, section or container, and every element inside that area works with the same data. Change the filter once, and the list, the counter and the heading above them all update together. It's a cleaner model than wiring elements together with code, and it's much closer to how React developers already work.

It also means that Velo code from an existing Wix Studio site doesn't carry over. It has to be rewritten.

The quiet limit: you can extend Wix pages, not replace them

This is the part we found most interesting in the new documentation.

Wix business solutions now share their data with your components through so-called business contexts. A price block you build yourself can read the product's current price, stock and selected options, and call "add to cart". When the visitor picks another size, your component updates on its own.

Two catches.

First, the context only exists on the solution's own pages, inside a Data Source, or inside an item of a list. Place the component anywhere else and it fails.
Second, and more important: in Studio Two, you can't replace a business solution's page or take over its flow. Wix itself calls a component with a context "a narrower customization". You can build your own buy box on the product page. You can't build your own product page or checkout from scratch, which many agencies did in Wix Studio with Velo.

And for now, only four business solutions share their data this way:

Your components can read their data

Wix Stores: product, category and product lists
Wix Blog: feed, post and related posts
Wix Events: event and event list
Wix Portfolio: project and project list

Not yet

Wix Bookings
Pricing Plans
Restaurants
Cart and checkout
Members

The solutions in the second column still work on Studio Two sites. Your own components just can't read their data in code yet, so any custom block around them has to wait.

What didn't make the first release

Collage illustration for the section about features missing from the first Studio Two release — Not everything made the first cut.

Here are the questions we see most often, answered from Wix's own comparison of Studio Two with Wix Studio and Wix Editor.

Where is the Members Area?

The Studio Two developer documentation doesn't mention a Members Area, and there is no member context for custom components. If your project depends on member pages, roles or a client portal, plan it on Wix Studio for now. We're testing what works on our own Studio Two site and will update this answer.

Can I move my Velo site to Studio Two?

Not as it is. Page code, the $w API, custom elements, web modules, routers, datasets, data hooks and dynamic page hooks aren't in this release. Custom CSS is a mixed case: Wix's feature list for the editor includes it, while the developer documentation still says it isn't supported yet, so test it before you plan around it. Data events are only a partial stand-in for data hooks: they run after a change is saved, can't block it, and work only for your own collections, not for Wix app or external ones. A move means rebuilding the frontend as React components and rethinking the data layer.

Can my site receive webhooks from other services?

Not yet. Studio Two has HTTP endpoints, but they serve only your site's own frontend. Endpoints that an external system calls, like a payment provider or a CRM sending a webhook, aren't available. Scheduled jobs aren't either.

Will my apps work?

It depends on how they are built. Apps made with Wix Blocks or legacy custom elements can't be installed on Studio Two, and legacy iFrame widgets are only partly supported. App developers can't yet ship their own Data Sources or function libraries, their components can't share values with other components, and their plugins can't slot into the Wix widgets that have already been rebuilt in React. Wix says support for those plugins is planned.

Can I work in my own IDE with Git?

Not outside the browser. Code lives in the Code tab: a built-in VS Code IDE where each user works in an isolated environment, with live collaboration, revision history and Aria as the AI assistant. There is no local development, no Git integration and no GitHub Actions, and the Wix IDE known from Velo projects isn't part of this release. Velo packages aren't available either; npm packages are. The only way to work on the code outside Wix is the export to React (beta).

Can I move a Harmony site to Studio Two?

Not yet. The Studio Two landing page lists "Harmony to Studio" as coming soon: a button that creates a Studio Two version of a Harmony site, with no need to start over, since both editors run on the same infrastructure. Until it ships, a Harmony site stays in Harmony.

Where is the infinite canvas?

The Studio Two landing page lists it as coming soon. Wix promises a space around the canvas where you can drag any element aside, try options without touching the live site, and drag the winner back in. Designers have been asking for this for years, and it's one of the features we're waiting for most. Note that Wix's official feature list for the editor doesn't include it and marks only the Harmony move as coming soon. For now, you work on the page itself.

What about forms with logic?

Forms with code aren't in this release.

What about testing and logs?

Preview and test sites work, but functional testing isn't in this release. Logs live in the site dashboard and only capture what your code writes through the monitoring client: console output isn't logged. Google Cloud Logs and other external logging tools can't be connected, but logs can be forwarded to any tool that accepts OpenTelemetry.

Can I teach Aria about my site?

Partly. A Studio Two site can add App Skills: instructions that tell Aria how to handle a task the same way every time. What a site can't do yet is give Aria tools, your own functions it could call while doing that task.

And one thing that did make it: Brik

Both the landing page and Wix's official feature list include Brik integration: a library of reactive 3D models, animations and interactive experiences, or your own, made with AI. Brik is Wix's own AI tool for interactive visuals at brik.space. A detail we didn't expect: the brik.space app itself runs on Base44, Wix's AI app builder.

Brik is a separate product with its own plans. On the free plan, exports are images and video with a watermark. Code export and embeds start at $12 a month, billed yearly. How the integration inside Studio Two will be billed, Wix hasn't said. And it's not the only way to get there: an AI coding agent with Wix Interact can build similar interactive blocks, as we showed in our Ani-Mate test.

Two things agencies ask about first: Content mode and Multilingual

Wix's feature list includes both in the first release. Content mode lets a client update content without accidentally changing the design, which matters at every handover. Multilingual translates a site into 180+ languages by hand, with automatic translation for 130+, and Wix says the design stays intact.

Backend limits that don't grow with your plan

Collage illustration for the section about Studio Two backend limits — The same ceiling for every plan.

This is new for Wix. For the first time, Wix publishes fixed backend limits for a type of editor rather than for a premium plan: one set of numbers for every Studio Two site. We've compared them with Velo in Wix Studio, Wix Headless and the serverless platforms behind popular AI builders in a separate technical review.

Every Studio Two site, free or premium, runs its backend with the same fixed resources.

In Wix Studio, these limits depend on the premium plan.

Here in Studio Two, paying more doesn't buy more compute:

0.3

CPU cores

Reserved per instance, throttled above that

400 MB

Memory

Per instance, more crashes the process

60 s

Per request

Longer requests end with a 504 error

5 min

Instance uptime

Then the instance restarts

There is one backend instance per data center, with no auto-scaling. Because the instance restarts every few minutes, nothing can be kept in memory between requests.

Data has to go to the Wix CMS or an external database. For a marketing site with a contact form, none of this matters.

For a site with heavy calculations, file processing or long-running imports, it decides the architecture: the heavy work has to run somewhere else.

Where Wix Harmony fits

Harmony is Wix's AI-first editor, built on the same architecture as Studio Two but without the coding environment. If a client wants a site they can manage by talking to Aria and nobody plans to write code, Harmony is the lighter option. Studio Two adds the Code tab, custom React components and Data Sources on top. Once "Harmony to Studio" ships, starting in Harmony also leaves an upgrade path open. You also don't need Aria to work on a Harmony site: we rebuilt a Studio Two template on Harmony with our own AI chat.

How to decide for a new project

Ask four questions before you choose the editor:

Does it need members, bookings customization or a client portal? Then Wix Studio, for now.
Does it receive data from other systems or run on a schedule? Then Wix Studio, or Studio Two with an external backend.
Is it design-first, with custom interactive blocks? Studio Two is built for exactly this.
Is there a React developer on the team? Without one, most of the new freedom stays unused.

Studio Two first release at a glance

Everything from this article, plus the smaller items from Wix's documentation, in one table. Based on the developer documentation as of 4 November 2026, with corrections from Wix's feature list on 6 November 2026:

Area	Not in the first release	Instead, for now
Development	Wix IDE (Velo), local IDE, Git, GitHub Actions	Built-in VS Code IDE in the Code tab; export to React (beta)
Development	Velo packages	npm packages
Frontend	$w API and page code	React components
Frontend	Custom elements	React components
Frontend	Custom CSS	Not supported in the docs; listed in Wix's feature list
Frontend	Forms with code	No alternative yet
Backend	Web modules	HTTP endpoints for your own frontend
Backend	HTTP functions (incoming webhooks)	No alternative yet
Backend	Routers	Dynamic pages
Backend	Scheduled jobs	No alternative yet
Data	Datasets	CMS Data Sources, display only
Data	Data hooks, dynamic page hooks	Data events, after save, own collections only
Business solutions	Replacing pages and flows	Components that read business contexts
Apps	Blocks widgets, legacy custom elements	Rebuild with the Wix CLI
Apps	Legacy iFrame widgets and pages	Partly supported
Apps	Own Data Sources, function libraries, plugins in new Wix widgets	Not yet; plugins planned
Aria	Tools in App Skills	Skills with instructions only
Testing	Functional testing	Preview and test sites
Logs	Google Cloud Logs, external logging tools	Forwarding to OpenTelemetry
Editor	Harmony to Studio Two	Coming soon
Editor	Infinite canvas	Coming soon on the landing page; not in the feature list

parnii note

We'll start new design-led projects in Studio Two and keep everything with member areas, bookings logic or integrations in Wix Studio until the next releases. The new model is better, but a client site can't wait for a roadmap.

FAQ

Should I move my Wix Studio site to Studio Two?

Not now if it uses Velo code, a Members Area or integrations that send data to your site. Studio Two is a separate editor, and the code has to be rebuilt as React components.