Web Studio Is Live: Build Websites with AI in Stensyl.

What Web Studio Actually Does

Web Studio is Stensyl's sixth generation pillar, joining Image, Video, 3D, Motion, and Write to complete the platform's creative suite. Where the other pillars handle visual assets, motion, and written content, Web Studio handles structure: it builds web pages.

Depending on your prompt and settings, it produces full single-page layouts, component-level HTML and CSS for use in a larger project, or complete multi-page site structures. You are not getting a rough wireframe sketch or a Figma file you then need to translate. You are getting structured, design-ready web output.

Under the hood, Web Studio draws on the same pool of leading AI models that power the rest of Stensyl's platform. Claude handles semantic structure and content logic. GPT-4-class models contribute to layout reasoning and code generation. Stensyl selects and blends these depending on the output type requested: a landing page optimised for visual impact is handled differently from a portfolio layout that needs clean typographic hierarchy. You do not configure this yourself. The platform makes the call based on what you have asked for.

The distinction from generic AI chat tools matters here. Asking ChatGPT or Claude directly for a web page produces raw code snippets. Useful, but incomplete. You get a block of markup with no visual context, no structured sections, and no way to review or adjust the layout before exporting. Web Studio outputs design-ready, structured web assets with editable sections you can review in a browser-based editor before the code ever leaves the platform.

Who This Feature Is Built For

Web Studio was not built for developers. It was built for designers who occasionally need web output and do not want to depend on a developer or learn a new tool every time a client asks for a project page.

Web designers are the obvious first users. Rapid concept pages for client presentations, before committing to a full Webflow or Framer build, are exactly where Web Studio earns its place. Generating three layout directions in an hour and presenting them as rendered pages rather than static mockups changes the conversation in a client meeting.

Graphic and brand designers will find this particularly useful when a branding project tips into digital territory. Translating a visual identity into a web format has historically meant briefing a developer or learning a visual builder from scratch. Web Studio shortens that path considerably. Feed it your brand direction, colour palette, and tone of voice, and it builds a layout that reflects them.

Interior and architectural designers routinely need project microsites and portfolio pages but rarely have the time or budget to commission a full web build for each one. A project case study page for a completed residential scheme, for example, is a realistic output for Web Studio in a single session.

Product and UX designers prototyping landing pages to test messaging before engineering involvement have long relied on no-code tools or static HTML mocks. Web Studio fits the same niche with less setup. Generate the page, share a link, gather feedback, iterate.

Freelancers and studio leads working across multiple disciplines often need to deliver client-facing assets quickly across formats. A single platform that produces the image, the copy, and the web page around it removes significant friction from that process.

How to Run Your First Web Build in Stensyl

Open Stensyl and select Web Studio from the generation pillar navigation. You will see an output type selector as your first decision point. The current options are:

• Landing page: a single-scroll layout optimised for a clear visual and messaging hierarchy
• Portfolio layout: structured for project showcases, case studies, or professional profiles
• Multi-section site: a linked set of pages with shared navigation and consistent structure

Select your output type, then write your prompt. Prompt quality matters more here than in image generation. Vague input produces generic output. The best results come from prompts that specify three things: the visual direction or style reference, the content intent, and the audience. For example: "A portfolio page for a residential interior design studio. Minimal layout, warm neutral palette, serif headings. The page should feature a hero image, three project case studies, and a contact section. Target audience is high-net-worth homeowners." That level of specificity gives the model enough to build a layout with genuine design intent rather than a placeholder structure.

Once generated, the output appears in the Web Studio editor. Sections are individually selectable. You can swap content, adjust copy, reorder blocks, and replace placeholder assets. The editor is not a full visual builder. Think of it as a structured review and light-edit environment. When you are satisfied, you export clean HTML and CSS.

One of the stronger features at launch is direct asset integration. If you have already generated images in Stensyl's Image pillar, or 3D renders in the 3D pillar, these are accessible from inside Web Studio. You pull them into the layout without downloading and re-uploading. The credit system covers all of this from one pool. Generating assets in Image and then assembling them in Web Studio does not trigger separate charges beyond the credits used for each generation.

Prompt specificity is the most reliable lever you have in Web Studio. Style reference, content intent, and target audience in a single prompt consistently produce better layout results than iterating from a vague starting point.

Web Studio is available on Starter (£22/mo) and above. Lite plan subscribers do not currently have access. Credits are drawn from the same shared pool used across all pillars. A single-page generation uses a comparable credit volume to a detailed image generation.

Web Studio Inside a Real Design Workflow

Here is a concrete example. An interior designer completes a residential project and needs to publish a case study to share with prospective clients. The old workflow looked like this:

1. Generate hero visuals in Midjourney (separate subscription, separate browser tab)
2. Write the case study copy in ChatGPT (another tab, manual formatting)
3. Export both, then manually assemble them in Webflow or Framer
4. Adjust layout to fit the assets, realise the image proportions are wrong, go back to Midjourney
5. Publish after three to four hours of context-switching

The same workflow inside Stensyl looks different. Generate the hero image in Image. Write the case study in Write. Open Web Studio, select portfolio layout, reference the assets already in your Stensyl library, and build the page around them. The outputs were designed together, in the same environment, with the same creative intent running through each generation. The result is more coherent and the process is faster.

The credit system is a practical advantage that compounds over time. Rather than managing three separate subscriptions (image generation, AI writing, web output), one Stensyl plan covers all of them. The Starter plan at £22 per month gives you access to Image, Write, and Web Studio from a single credit pool. There is no premium tier locked behind each pillar.

It is worth being clear about where in the process Web Studio belongs. It is a concept and presentation tool. It is strong at the stage where you need to show a client or stakeholder what a web presence could look like before committing to a production build. It is not a replacement for a CMS-backed site built in Webflow, WordPress, or a custom development stack. The output is static HTML and CSS. It will not connect to a content database or handle dynamic user behaviour. That distinction matters, and the next section covers it directly.

Stage	Web Studio fit	Better served by
Concept and direction	Strong	Web Studio
Client presentation	Strong	Web Studio
Messaging and copy testing	Strong	Web Studio
Production CMS build	Not applicable	Webflow, WordPress, custom dev
Dynamic data and user accounts	Not applicable	Full-stack development

Current Capabilities and Known Limits

Web Studio at launch exports three types of output: clean HTML and CSS files, individual component code blocks for use in an existing project, and structured layout files with sections clearly delineated. The HTML is semantic and reasonably clean. It is not production-optimised code, but it is readable, editable, and usable as a handoff starting point for a developer.

The current limitations are real and worth naming directly.

No live CMS connection. The output is static at launch. If you need a blog with editable posts, a product catalogue, or any content that updates dynamically, Web Studio is not the right tool for that stage. It generates a fixed layout that you then take into a CMS environment if ongoing content management is needed.

Browser-based editing has constraints. The Web Studio editor is not a dedicated visual builder. Webflow and Framer offer substantially more granular control over layout, interactions, and responsive behaviour. Web Studio's editor is designed for light adjustments and review, not pixel-level construction. If your process normally involves deep layout customisation, plan to export early and continue in your preferred environment.

Responsive behaviour is included but not fully configurable. Generated layouts are built with responsive breakpoints, but fine-tuning how a section behaves between breakpoints requires editing the exported code directly. The editor does not yet expose responsive controls at the level of a dedicated visual builder.

The Stensyl team has flagged several additions currently in development. These include interactive component support, expanded template libraries oriented around specific design disciplines, and improved integration between the Web Studio editor and assets generated in the 3D pillar. Specifics and timelines will be communicated through the Stensyl platform updates channel.

Feedback on Web Studio goes directly to the product team via the feedback panel inside the Stensyl dashboard. This is the most direct route to influencing the roadmap. The team actively reviews submissions, and several features added to other pillars since launch have come directly from user input.

Getting Started: Plans, Access, and First Steps

Web Studio is available on Starter (£22/mo), Pro (£42/mo), and Studio (£84/mo). Lite plan subscribers do not have access to this pillar. If you are already on a qualifying plan, the Web Studio tab is live in your dashboard now. No upgrade required, no separate activation.

If you are new to Stensyl, the Starter plan is the logical entry point. It gives you access to all six pillars from a single credit pool, which means your first web build session can include image generation, copy writing, and page assembly without switching plans or paying extra for any individual mode.

For your first Web Studio project, a single-page portfolio or a project case study layout is the best test. Both output types are well-suited to the current feature set, involve a realistic volume of content to work with, and give you a clear sense of where the tool fits in your process. They are also genuinely useful outputs: a case study page you can share with a client is a better test than a throwaway experiment.

The asset integration angle is worth testing early. Generate a hero image in Image, draft a short project description in Write, then bring both into a Web Studio layout. That single session demonstrates the core value of having all six pillars under one roof. The assets are coherent because they were created with the same brief. The page comes together faster because nothing needs to leave the platform.

Web Studio does not replace your existing web production tools. It replaces the gap between a design concept and a shareable, structured web layout. That gap has historically cost designers hours of context-switching, manual assembly, and dependency on other people. It no longer needs to.