window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'AW-17391183273');
top of page
Minimalist White Calendar Icon.png

Holidays Sorted! We’re working right through December & January.

LowCodeWebsite is a brand of  iView Labs Pvt. Ltd.

Wix Studio Two for Agencies: How Custom Code Changes From Velo to React

3 days ago
7 min read

In Wix Studio Two, custom code is written in React and TypeScript inside a Code tab, not in Velo. Studio Two has no Velo page code and no $w API. Custom screens are built as Editor React Components, and data, backend logic, and dashboards use new extension types. Existing Wix Studio sites with Velo stay supported, but their code does not carry over automatically, so plan to rebuild custom features in React when you move.


Introduction

For years, custom work on Wix meant Velo. Agencies used Velo to add forms with logic, custom pages, data rules, scheduled jobs, and connections to other tools. Now Wix has announced Studio Two, and the way custom code works has changed in a big way.


If your agency builds client sites on Wix, this matters. Some things get easier. Some things work differently. And a few things are not in the first release yet.


In this guide, we explain how custom code changes in Wix Studio Two for agencies, in simple words and with clear examples, so you can plan your next projects with confidence.


What Is Changing in Wix Studio Two for Agencies?

Wix announced Studio Two on November 2, 2026, and is rolling it out gradually. It is a separate editor from Wix Studio. It is not an update to your existing sites.


Here is the big change in one line:

  • Before (Wix Studio): Custom code used Velo, with page code and the $w API.

  • Now (Studio Two): Custom code is standard React and TypeScript, written in a Code tab that is a Visual Studio Code environment inside the editor.


Wix says this first release does not include everything from Velo, and more features are planned.


Wix Studio Two for Agencies: How Custom Code Changes From Velo to React

How Does Custom Code Work in Wix Studio Two?

Studio Two uses a few simple building blocks:

  • Editor React Components (ERCs): React components that you build and that Wix users place on a page. These replace most custom page code.

  • Data Sources: Pieces that supply data to components, such as data from a CMS collection.

  • Function libraries: Reusable functions that components can use.

  • HTTP endpoints: Backend routes that your site’s own frontend calls to run code on Wix servers.

  • Backend events: Code that runs when something happens, such as an event in a Wix business tool.

  • Site plugins and service plugins: Ways to add custom behavior to Wix business tools.

  • Dashboard pages: Custom pages inside the site’s dashboard.

  • Embedded scripts and custom code snippets: For adding outside scripts.


You can also use npm packages, work with the Secrets Manager for keys, and get help from Aria 2.0 while coding.


What Is Not in Wix Studio Two Yet?

Wix lists these Wix Studio coding features as not in the first release:

  • Development tools: Wix IDE, local IDE and Git integration, GitHub Actions, and Velo packages

  • Frontend: The $w API, custom elements, and forms with code

  • Backend: Web modules, HTTP functions (endpoints that outside systems can call), routers, scheduled jobs, custom automation actions, and triggered emails

  • Data: Datasets, data hooks, and dynamic page hooks

  • Business tools: Replacing the default pages of a Wix business solution, such as Wix Bookings or Wix Stores, with your own

  • Other: Functional testing, and Google Cloud Logs


Also note that backend code in Studio Two runs with fixed compute limits that apply to every site, with no auto-scaling. In Wix Studio, the limits depend on the site’s plan.


What Stays the Same?

Not everything changes. Wix says these are supported in Studio Two:

  • Wix CMS collections and the Data API

  • Wix business solutions like Stores and Bookings (available on Studio Two sites)

  • TypeScript and npm packages

  • Secrets Manager for keys and passwords

  • Site history, including code changes

  • Preview and test sites

  • External databases

  • Custom CSS for each element, and custom code snippets

  • Dashboard pages and service plugins


Simple Examples: What This Means for Real Client Sites

Example 1: A custom price calculator. In Wix Studio, a developer might build this with Velo page code. In Studio Two, the developer builds it as an Editor React Component, and the designer places it on the canvas.


Example 2: A booking site that needs a custom flow. In Studio Two, you cannot replace the default page of a Wix business solution like Bookings. You can build an ERC that uses a Wix business solution context, but this is a narrower kind of customization. If a client needs a fully custom booking flow, stay on Wix Studio for now or check what Studio Two allows.


Example 3: A client wants a webhook from another tool. HTTP functions that outside systems can call are not in the first release. Studio Two’s HTTP endpoints only serve your site’s own frontend. This kind of project may need a different approach for now.


Example 4: A scheduled reminder job. Scheduled jobs are not in the first release, so a recurring task would need a different plan.


Should Your Agency Move to Wix Studio Two Now?

There is no need to rush. Wix says existing Wix Studio sites remain supported, and partners can work in both editors during the rollout.


Studio Two is a good fit when:

  • You are starting a new site

  • You want AI-assisted building with Aria 2.0

  • You want custom components in React

  • The project does not depend on the missing features above


Staying on Wix Studio is safer when:

  • The site uses Velo web modules, routers, scheduled jobs, or webhooks

  • A client needs full control of a business solution’s pages

  • You depend on Git, the local IDE, or Velo packages


When we checked, we found no official tool to move an existing Wix Studio site into Studio Two. Third-party guides say a move means rebuilding the site, with your CMS and apps carrying on. Please confirm this in Wix’s documentation before you advise a client.


How Should Agencies Plan Custom Code for Wix Studio Two?

  1. List the custom features on each client site: forms, calculators, automations, data rules, and integrations.

  2. Check each one against Wix’s official comparison page.

  3. Keep Velo code small and well documented on current sites, so a rebuild is easier later.

  4. Test Studio Two on a new, low-risk project first.

  5. Plan for review. Aria can write code, but someone must still check the data structure, business logic, and security.

  6. Line up technical help, so your designers can keep designing while a developer handles React.


Do Designers Need to Learn React for Wix Studio Two?

No. Designers can keep working on the canvas and use Aria for AI help. React is for custom components and logic. An agency can bring in a developer or a white-label team for this part, and the client still sees one brand.


Common Mistakes When Moving From Velo to React

  • Assuming Velo code will carry over to Studio Two automatically

  • Moving a live client site before checking the missing features

  • Planning a webhook, scheduled job, or custom booking flow without checking support

  • Skipping a review of AI-written code

  • Forgetting that backend code has fixed limits in Studio Two

  • Not telling the client what changes and what stays the same


How LowCodeWebsite Helps Agencies With Wix Studio Two

LowCodeWebsite by iView Labs is a Wix Legend Partner from India. We build Wix and Wix Studio websites and custom features with Velo, and we are getting ready for Wix Studio Two now, so you don’t have to. We can help agencies with:

  • Checking each client project: stay on Wix Studio, or start in Studio Two

  • Wix Studio and Velo development for sites that need features not yet in Studio Two

  • Custom components, integrations, and automations as the Studio Two tools grow

  • Rebuilding Velo features in React when the time is right

  • White-label development under your brand, so your client only sees you


Why businesses trust us:

With 14+ years of experience, we have worked with clients across the US, UK, Australia, and other international markets.


See our work in the portfolio, or learn how our white-label team works.


Contact Us for Your Wix Studio Two Project

Planning a client project and not sure whether it fits Wix Studio Two for agencies? Book a free consultation or contact LowCodeWebsite today, and we will help you plan it.


Learn More:


Conclusion

Wix Studio Two for agencies brings a new way to write custom code: React and TypeScript instead of Velo. It opens the door to modern tools and AI help, but the first release does not yet cover every Velo feature. Start new, simple projects in Studio Two, keep complex Velo sites on Wix Studio for now, and plan custom code carefully. With the right plan, the change is manageable.


Frequently Asked Questions


No. Wix Studio Two has no Velo, no $w API, and no page code. Custom code is written in React and TypeScript in the Code tab.

Editor React Components replace page code for custom screens. Data Sources replace datasets, HTTP endpoints replace web modules, and dynamic pages replace routers.

On existing Wix Studio sites, yes. Wix says current Studio sites remain supported. But Velo code does not carry over into Studio Two, so custom features need to be rebuilt in React if you move.

We found no official migration tool for existing Wix Studio sites at the time of writing, so a move means rebuilding the site. Check Wix’s documentation for updates.

Wix lists web modules, HTTP functions, routers, scheduled jobs, triggered emails, data hooks, datasets, Velo packages, and the Wix IDE and Git integration as not in the first release.

No. Designers can keep working on the canvas. React is needed for custom components, which a developer or a white-label team can build.

It is a React component that a developer builds and that a Wix user places on a page in Studio Two. It draws its own screen and connects to data and functions.

It depends on the project. Studio Two is good for new sites that want AI help and React components. Wix Studio is safer today for sites that rely on Velo features not yet in Studio Two.


Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
whatsapp.png
bottom of page