What you choose to build on Wix shapes the tools you work with, the audience you reach, and how Wix services fit into your project. There are 3 main paths to choose from:
When you extend a Wix site, you add custom code that runs on the site itself, in the frontend and the backend. You have full access to Wix business solutions like Stores, Bookings, and Events, plus the Wix CMS for data.
Extending a Wix site is a good fit when:
Notes:
Studio Two uses its own code model. Wix Studio and Wix Editor share the same code model.
Studio Two is an AI-powered editor, like Wix Harmony. Aria, Wix's AI assistant, can write and modify code for you, or you can write TypeScript yourself in the Code tab, a Visual Studio Code environment in the browser. You add functionality with the Wix Extension Builder. Custom UI is built with React. The site is built on Astro, and Wix hosts the backend.
To get started, see About Extending Websites with Studio Two. If you already extend a Wix Studio or Wix Editor site, see Compare Extending Websites in Studio Two to Wix Editor and Wix Studio.
You add code on these sites with the JavaScript SDK. The editors differ in their design tools and target audience:
From a developer's perspective, the 2 are very similar. They share the same site code model, business solution access, and app-extension support. The choice is primarily about design tooling, as well as several additional differences, such as:
To get started, see Extend Websites with SDK.
In a headless project, you build your own site or app using any framework and any tech stack. You then connect to Wix services like the CMS, eCommerce, and Bookings through Wix APIs. Wix users manage these services through the same dashboard used for Wix sites built in the Wix editors.
Going headless is a good fit when:
Headless projects can be Wix-managed or self-managed:
Both give you full access to Wix's services and APIs. The choice is primarily about how much infrastructure you want to manage.
To get started, see Go Headless.
When you build an app, you create an installable package that Wix users add to their sites. Apps bundle extensions for site UI, dashboard functionality, backend logic, and business-solution integrations. You distribute apps through the App Market or privately to specific sites.
Building an app is a good fit when:
Apps can be installed on most Wix site types. Some extension types are limited on certain site types.
Apps use one of the following frameworks:
These frameworks aren't mutually exclusive. You can mix them within a single app, with extensions using different frameworks if it makes sense. Most apps start with the CLI and add other frameworks only when needed.
To get started, see Build Apps.
Wix hosts the backend on some paths. On others, you host the code that calls Wix. The first group is Wix-managed.
On a Wix-managed path, your backend code runs on Wix. Wix handles deployment and the runtime. You don't provision servers. These paths are Wix-managed:
On a self-managed path, you host the code. You choose the runtime, framework, and language, and you handle hosting, deployment, and scaling. The project calls Wix through the JavaScript SDK or the REST API. These paths are self-managed:
An app can mix the two. An extension deployed with the CLI is Wix-managed. An extension you host yourself is self-managed.
Use this decision tree to find the right Wix tool for what you're building. Start at the top and follow the branches that match your needs.
Last updated: 4 November 2026