Wix Studio 2 First Impressions: What Works, What Feels Rough, and What Matters Most

Wix Studio 2 is starting to roll out, and this early access walkthrough offers a useful first look at what the new editor is actually like in practice. Based on my unsponsored hands-on walkthrough, the big picture is clear: Wix is pushing further into AI-assisted site creation, but the real story is in the details. The planning flow is interesting, the generated designs are solid but somewhat repetitive, the editor feels more advanced than Harmony, and the code experience raises important questions for developers.

What Wix Studio 2 is trying to be

From the opening screen, Studio 2 looks less like classic Wix Studio and more like an AI-first builder. You can start with a prompt, add references or existing content, include reusable skills, and enable plan mode before the site is generated. In many ways this product looked closer to Harmony than to the original Studio editor, and that impression seems to hold up throughout the test.

That positioning matters. Studio 2 appears to combine visual editing, AI guidance, and custom functionality in one place. In theory, that should make it useful for both DIY users and professionals. In practice, the first impression is that Wix is still balancing simplicity, depth, and polish.

The onboarding flow: prompt, plan mode, and brief generation

The walkthrough begins with a playful business idea: a New York real estate company that rents out street corners to food vendors. Instead of jumping straight into generation, Studio 2 allows the user to shape the project first. That includes choosing a prompt, adding references, and turning on plan mode to create a brief before design generation starts.

• You can begin from a prompt or pick from starter templates.

• The prompt input supports design references, media, text, and reusable skills.

• Plan mode adds a briefing step before the site is generated.

• The Aria assistant asks follow-up questions about branding, goals, audience, and sections to include.

• There is also an option to skip ahead to the editor if you do not want to wait for planning.

This briefing step is promising, especially for freelancers and agencies. A structured brief can save time, clarify direction, and reduce unnecessary revisions.

That leads to an important takeaway: Studio 2 can help refine a concept, but it should not replace deliberate planning. If you are building a real client site, you still need your own requirements process rather than relying completely on whatever questions the AI happens to ask that day.

Generated designs: good quality, limited variety

Once the brief is complete, Studio 2 generates three design directions. The overall quality looks good, and the interface gives clear next actions: preview a concept, generate a site from it, regenerate the options, or skip to the editor. That said, one criticism stands out: the designs feel too similar to each other.

• The generated layouts appear polished and usable.

• Each option includes preview and site-generation controls.

• The three concepts share a lot of the same visual language.

• Some repeated elements, including matching footer structures, make the options feel less distinct than expected.

For a real workflow, that similarity matters. If the point of multiple concepts is to compare different directions, the variations need to be meaningful enough for a client or team to react to them. Based on this first look, Studio 2 may still need more diversity in its design exploration stage.

Inside the editor: familiar ideas, uneven usability

After site generation finishes, the editor itself becomes the focus. The interface is clearly more advanced than Harmony, but the first impression is mixed. It uses dark mode, shows Aria on the left side, keeps a detailed inspector on the right, and places a styling control bar near the bottom of the screen. For me some controls are hard to notice, and that parts of the layout feel unintuitive or visually cramped.

• The editor opened in dark mode, with no obvious light mode option during the walkthrough.

• Aria moved to the left side, likely to make room for the inspector on the right.

• The inspector exists, but it can feel hidden unless you know where to look.

• Desktop and mobile breakpoints were visible, but tablet was not shown as a default breakpoint.

• The styling toolbar appeared near the bottom, which felt less natural than a top placement.

• Aria can be collapsed, but doing so did not fully reclaim or recenter the canvas area during the demo.

The editing model itself still feels recognizably Wix: click an element, open controls, adjust styling, drag elements around, and refine visually. That part should feel approachable to existing Wix users. The concern is less about capability and more about clarity. Several useful controls seemed buried or easy to miss.

CMS and elements: promising, but with familiar limits

One of the more practical parts of the walkthrough is the CMS check. Studio 2 includes a repeater element and gives CMS a dedicated entry point in the interface rather than hiding it until certain elements are added. That is a welcome improvement in discoverability. However, the first pass suggests that the CMS field options may still feel limited compared with older Wix editors.

• A repeater element is available and can connect to data.

• CMS is accessible directly from the interface rather than only through a repeater-first flow.

• The initial field list appeared restricted during testing, which raised concerns about advanced CMS use cases.

• Wix app collections were not visible at first, but they appeared after enabling the relevant setting in advanced options.

For designers building brochure sites, these limits may not matter much. For developers or anyone building more functional websites, they matter a lot. The transcript makes that distinction very clearly: design controls are useful, but advanced functionality is often the real test of whether an editor can support serious projects.

Code mode: more like an app builder than full source access

This is where the review becomes especially interesting. Studio 2 includes a code toggle, which initially suggests a seamless blend between visual editing and source-level control. But once the code panel opens, the experience looks less like editing the site itself and more like building extensions around the site.

In the walkthrough, the file structure feels very similar to Wix CLI app development. Instead of exposing the full editable source for every page inside the editor, Studio 2 appears to center custom components, data sources, function libraries, backend logic, and other extension-style building blocks. That is still powerful, but it is not the same as having direct everyday access to the complete front-end source while you design.

• The built-in code environment resembles a lightweight IDE.

• Custom components, data sources, and function libraries can be created from inside the editor.

• The workflow feels close to Wix app development rather than open-ended source editing.

• This raised concern that Studio 2 may introduce more Wix-specific patterns instead of using a more standard development model.

That distinction shapes the whole review. If you expected Studio 2 to behave like a visual front end on top of fully editable source code, this first impression will feel limiting. If you expected a more integrated way to attach custom functionality to a Wix-built site, it will feel more logical.

Testing AI-generated functionality in code mode

To evaluate the real usefulness of code mode, I asked Aria to build a visitor counter that increments once per session. This is a good evaluation because it requires more than styling. It needs persistence, likely a collection to store data, and a component that can surface the count on the live site.

Studio 2 did make progress on that request. Aria asked a sensible follow-up question about whether the count should be local or persistent across all visitors, then generated files, created a collection, and surfaced the new component in the editor so it could be dragged onto the page. That streamlined handoff from AI to visual placement is one of the more compelling parts of the product.

However, the feature did not appear to work correctly after publishing. The counter stayed at zero during the live check. That does not necessarily mean the platform cannot do it, but it does show the current gap between generated setup and reliable outcome. For early access software, that is not shocking. For production work, it is a meaningful caution.

The export feature may be the biggest story

One of the strongest moments in the entire walkthrough comes towards the end: site export. Export is marked as beta, and the first export attempt ran into an error related to a checkout page. But after switching to a simpler site, the exported files looked much more substantial than just extension code.

• The first export attempt failed on a site with commerce-related functionality.

• A simpler blank site exported successfully.

• The downloaded project included both site code and site app directories.

• The exported files appeared to include actual page-related code, not just the custom extensions shown in the in-editor code panel.

That matters because it suggests Wix is willing to let users take meaningful code artifacts out of the platform, even if the editor itself does not expose them in the same way day to day. In the context of Wix, that is a significant development. It also creates a curious contradiction: if that code can be exported, why is the in-editor code view still so constrained?

What freelancers and developers should take from this

If you build sites for clients, Studio 2 already hints at a useful workflow: prompt the project, generate a brief, review direction, produce design options, refine visually, and extend functionality when needed. But the current experience still feels early. There are permission errors, UI inconsistencies, hidden controls, generation hiccups, and at least one generated feature that did not work out of the box.

For developers, the decision is even more nuanced. Studio 2 does add convenience by keeping custom functionality closer to the editor experience. But based on this first look, it does not yet fully replace the flexibility of a more standard source-first workflow. The coding layer appears powerful, yet deliberately structured around Wix’s own model.

Final verdict

After a first hands-on walkthrough, Wix Studio 2 looks promising but unfinished. The planning flow is a smart addition, the design generation is competent, the editor offers more control than Harmony, and the export feature could become genuinely important. At the same time, the UX still needs polish, the design variations need more separation, and the coding experience may not match what some advanced users were hoping for. In short, Studio 2 feels like a meaningful step forward for Wix, but not yet the complete all-in-one answer that the most demanding designers and developers may have imagined.