If you already extend a Wix Editor or Wix Studio site with code, use this page to see which of those features are supported in Studio Two.
This is the initial release, and more features are planned for later releases. For a supported feature, follow the link to the Studio Two article.
These Wix Editor and Wix Studio features aren't in this release:
$w API, custom elements, and forms with code.You write code in the Code tab.
| Feature | In this release |
|---|---|
| Code editor | Supported, in the Code tab. About the Code Tab |
| Wix IDE | Not in this release. |
| Local IDE and Git integration | Not in this release. This includes the local editor and GitHub Actions. To work on a site's code outside Wix, you can export it to code (alpha). About Exporting Your Site to Code |
| TypeScript | Supported. You write Studio Two code in TypeScript, which compiles to JavaScript. About Extending Websites with Studio Two |
| npm packages | Supported. About npm Packages |
| Velo packages | Not in this release. |
| Site history | Supported. Site history revisions include code changes, and restoring an earlier version also restores the code. To open it, select Site > Site History in the editor's top-left menu. |
| Secrets Manager | Supported. About the Secrets Manager |
| AI assistant | Supported. About the Code Tab |
Studio Two has no $w API. To build custom UI, you write Editor React Components (ERCs), which render their own UI in React.
| Feature | In this release |
|---|---|
| Custom CSS | Not supported yet. |
| Custom code snippets | Supported as embedded scripts. About Embedded Scripts |
| $w API | Not in this release. Instead, an ERC renders the UI, and a Wix user connects its props to values and functions from Data Sources and function libraries. |
| Custom elements | Not in this release. Use ERCs for custom components. |
| Forms with code | Not in this release. |
The Site SDKs give an ERC information about the site and its pages while it renders, and let it navigate and open popups. Studio Two has no $w API, so the Site SDKs replace what site code used to read from wix-location, wix-window, and wix-site. Install each API's package with npm.
| Feature | In this release |
|---|---|
| Site pages and the current page | Supported. Pages API, @wix/site-service-pages. |
| Navigation | Supported. Router API, @wix/site-service-router. |
| Page and site URLs | Supported. URL API, @wix/site-service-url. |
| Popups | Supported. Lightbox API, @wix/site-service-lightbox. |
| Language, regional format, and time zone | Supported. Locale API, @wix/site-service-locale. |
| Site name, ID, and revision | Supported. Site Info API, @wix/site-service-site-info. |
| Site theme colors and fonts | Supported. Site Theme API, @wix/site-service-site-theme. In Wix Editor and Wix Studio, read them through CSS variables. |
| Device class | Supported. Device Info API, @wix/site-service-device-info. |
| Server or browser rendering | Supported. Rendering Context API, @wix/site-service-rendering-context. |
| Page head markup | Supported. Head Appender API, @wix/site-service-head-appender. |
Wix hosts your backend code.
| Feature | In this release |
|---|---|
| Web modules | Not in this release. To call backend code from your site's own frontend, use HTTP endpoints. About HTTP Endpoints |
| Backend events | Supported. About Backend Events |
| HTTP functions | Not in this release. You can't yet create endpoints that external systems, such as 3rd-party services, call. Studio Two HTTP endpoints serve only your site's own frontend code. |
| Routers | Not in this release. Use dynamic pages. |
| Scheduled jobs | Not in this release. |
Wix CMS collections and the Data API work much as they do in Wix Editor and Wix Studio. Connecting page elements to data and responding to data changes work differently. To learn more, see About the Wix Data Ecosystem.
| Feature | In this release |
|---|---|
| Wix CMS | Supported. About Collections |
| Data API | Supported. About the Data API |
| Cached query results | Supported. The Data API caches some read-only queries on a CDN, as in Wix Editor and Wix Studio. About Cached Queries |
| Datasets | Not in this release. Use CMS Data Sources, which only display data. About CMS Data Sources |
| Dynamic pages | Supported. About Dynamic Pages |
| Dynamic page hooks | Not in this release. |
| Data hooks | Not in this release. Data events are a partial alternative: they run after a change is saved, so they can't validate or block it. |
| Data events | Supported, with a limit. Handlers run only for changes to user-created collections, not for Wix app collections or external collections. About Data Events |
| External databases | Supported. About External Databases |
Custom pages in the site dashboard.
| Feature | In this release |
|---|---|
| Dashboard pages | Supported. About Dashboard Pages |
Wix business solutions, such as Wix Stores and Wix Bookings, are available on Studio Two sites.
| Feature | In this release |
|---|---|
| Business solution APIs | Supported. About npm Packages |
| Replace business solution pages | Not in this release. You can't replace a business solution's default page or take over its flow. You can build an ERC that uses a Wix business solution context, which is a narrower customization. Use a Wix Context in an Editor React Component in Studio Two |
| Service plugins | Supported. Add a Service Plugin Extension in Studio Two |
Check code in preview and on a test site before you publish.
| Feature | In this release |
|---|---|
| Preview | Supported. About the Code Tab |
| Test sites | Supported. In the editor, open the Preview menu and select Preview as Test Site. |
| Functional testing | Not in this release. |
| Logs | Supported. Your code writes entries with the monitoring client, and console output isn't logged. About Logs in Studio Two |
Monitoring and logs are in the site dashboard. Open them from Developer Tools on the left edge of the editor.
| Feature | In this release |
|---|---|
| Monitoring | Supported. About the Code Tab |
| Google Cloud Logs and external logging tool connections | Not in this release. To send logs to a tool that accepts OpenTelemetry, use Signal Forwarding. Forward Logs to an OpenTelemetry Endpoint in Studio Two |
Backend code in Studio Two runs with fixed compute limits that apply to every site, with no auto-scaling. In Wix Editor and Wix Studio, the limits depend on the site's premium plan. To learn more, see About Backend Compute Limitations.
Last updated: 2 November 2026