Wix provides different coding environments, management consoles, testing options, and supporting tools depending on what you're building.
Each development path comes with a primary coding environment suited to how you build and deploy code.
| Project type | Coding environment |
|---|---|
| Studio Two sites | Code tab in the Studio Two editor |
| Wix Studio and Wix Editor sites | Built-in code editor or local IDE with the CLI for Sites |
| Wix-managed apps | Local IDE with the Wix CLI |
| Self-managed apps | Your own tooling |
| Wix-managed headless | Local IDE with the Wix CLI |
| Self-managed headless | Your own tooling |
| Blocks apps | Blocks editor |
Note: Studio Two is rolling out and is not yet available to all users.
The Wix CLI is the command-line tool for Wix-managed apps and headless projects. It scaffolds new projects, generates extensions, runs a local dev server, and deploys code to Wix's cloud.
The CLI starts a local development environment with hot reloading:
wix app dev serves your app on a development site, with links to view it in the site, the editor, and the dashboard. App projects use TypeScript, React, and Node.js.wix dev starts a local Astro-based server with a link to your project's dashboard. Headless projects add the Astro web framework for the site's frontend.In both, Wix handles authentication, so you can call JavaScript SDK methods without manually setting up a client or managing tokens.
The Wix CLI for Apps replaces the two legacy CLIs for apps. Existing legacy projects still work. Create new apps with the Wix CLI.
For the full command reference, see Wix CLI Command Reference.
Studio Two sites are coded in the Code tab of the Studio Two editor, a Visual Studio Code environment in the browser. The tab includes the Wix Extension Builder for adding extensions, Aria, which can write and modify code for you, and a terminal. There's nothing to install before you start. For what the tab contains, see About the Code Tab.
A browser-based editor that runs alongside the visual site editor, available on Wix Studio and Wix Editor sites. Code runs directly in the context of the site, with access to the full Wix JavaScript SDK.
For Wix Studio and Wix Editor sites, you can connect your own IDE through Git integration and the CLI for Sites. Your code lives in a GitHub repo, giving you version control, branching, and team collaboration. wix dev opens a Local Editor in the browser that syncs with your local changes in real time.
The CLI for Sites is a different tool from the Wix CLI used for apps and headless projects.
A browser-based editor for building Blocks apps. The canvas lets you design widget layouts, configure properties and events, and write backend code. The Blocks editor is also where you preview, test, and release app versions. The Wix IDE can be used for writing code, but preview, testing, and releasing must be done in the Blocks editor.
Wix provides two management consoles for different aspects of your work.
| Project type | Management dashboard |
|---|---|
| Studio Two sites | Site Dashboard |
| Wix Studio and Wix Editor sites | Site Dashboard |
| Wix-managed apps | App Dashboard |
| Self-managed apps | App Dashboard |
| Wix-managed headless | Site Dashboard |
| Self-managed headless | Site Dashboard |
| Blocks apps | App Dashboard |
The App Dashboard is the management console for Wix apps. You register apps here, configure extensions, set up OAuth and permissions, and handle launch tasks like pricing, market listing, translations, and analytics.
How much you rely on the App Dashboard depends on your framework. Self-managed apps use it most: you register extensions and configure integrations here by pointing to your own hosted assets. With the Wix CLI, most of that setup happens in code, so you mainly use the App Dashboard for launch and management tasks.
The Site Dashboard is the admin console for managing a Wix site's business data and settings. It covers content (products, bookings, members), installed apps, and site configuration. Headless developers use it to manage the business data layer even when the frontend is fully custom. For site and headless developers, it also includes a Developer Tools section with tools for logging, monitoring, and debugging.
How you test and preview your work depends on your development path:
wix dev: opens the Local Editor with real-time sync from your local IDEwix preview: generates a shareable preview URL from a published branchwix app dev: serves your app on a development site with hot reloadingwix app preview: shareable links that install a preview of your app's latest build on a development sitewix dev: starts a local server (port 4321) with hot reloadingwix preview: shareable preview URLs for both site and dashboardnpx wix preview if the project is connected via wix initDevelopment and test sites are separate from your production site, so nothing you do there affects live users. On Wix Studio and Wix Editor sites and in Blocks apps, backend events and scheduled jobs run only on a published site. They don't run in preview. Studio Two sites don't have scheduled jobs.
These tools are available across development paths to complement your primary environment.
For platform capabilities like the CMS, Secrets Manager, Media Manager, and Automations, see Site Features and Tools.
Last updated: 11 November 2026