Stensyl Web Studio: Design and Prototype Sites with AI.

What Web Studio Actually Does

Web Studio lives inside Stensyl's Publish section, at /web, alongside Marketing and Editing. It is purpose-built for generating landing pages and microsites from a written brief. It is not a general-purpose site builder or a developer-grade CMS. That distinction matters: Web Studio is optimised for the moment when a creative professional needs a structured, visual page quickly, without assembling components from scratch or opening a separate tool.

The core workflow is direct. You describe the page: its goal, its audience, its tone. Web Studio uses that input to generate a full layout, with visual hierarchy, section structure, and copy placeholders already applied. One step from brief to structured visual. For a UX designer, that means skipping the blank-canvas phase entirely. For a marketing professional, it means a campaign landing page shell exists before the first internal review.

The use cases extend well beyond web and UX work. Exhibition designers can generate event microsites to accompany a physical show. Product designers can build showcase pages for client review, where a real layout communicates far more than a static PDF. Graphic designers moving from a brand identity project to a launch page can carry their assets directly into a web layout without rebuilding anything.

Web Studio shares the same credit system as every other Stensyl surface. There is no separate subscription, no export fee, and no wall between the web generator and the rest of the platform. Building and iterating on a page is available on every plan, including Free. Publishing it live and connecting a custom domain is a Pro or Studio tier feature. The design and prototyping workflow is fully open at every tier; the hosted, public URL is the gated step.

From Brief to Layout: The Generation Workflow

The generation workflow starts with a written brief. Describe the page goal, name the audience, define the tone. Web Studio takes that input and returns a structured layout: sections ordered by visual hierarchy, copy placeholders in place, and a page shape that reflects what the brief asked for. This is not a template system where you choose from a gallery. The layout is generated from the specific brief you write.

Iteration works the same way. Refine the prompt, adjust a section, request a different tone for the hero copy. Because generation is prompt-driven, changes are fast and non-destructive. There is no need to redraw frames in a separate tool or undo a manual layout change. You adjust the brief, and the output follows.

A practical example: a graphic designer launching a brand identity project writes a brief for a minimal portfolio page. The brief specifies a clean hero section, a case study grid, and a contact area. Web Studio returns exactly that structure in one pass, with placeholder copy that reflects the portfolio context. The designer then swaps in real project images and refines the copy, rather than building the layout from zero.

The same logic applies across disciplines. A content creator building a campaign microsite writes a brief for a product announcement page: short-form hero, feature list, email capture. Web Studio generates the shell. Real assets go in. The page is ready for review before any external tool is opened.

Because Web Studio is inside Stensyl, assets generated in Image, Graphics, or 3D feed directly into the page without exporting and reimporting files. A product render created in the 3D studio is already inside the project. A brand graphic from the Graphics studio is already available. The connection is not a workaround. It is how the platform is structured: one asset pool, shared across every surface in the workspace.

Using Write and Canvas to Shape Copy Before the Page Exists

A layout generated from a weak brief produces a weak layout. The quality of the output tracks the quality of the input, which means shaping the copy before the page is generated is time well spent. Stensyl's Write studio is the right place to do that work.

Write is a long-form document drafting surface with a multi-model picker. The six writing models available are GPT-5.4 mini, Gemini Flash, Gemini Pro, GPT-5.5, Claude Sonnet 4.6, and Claude Opus 4.7. All six are available on every plan. The choice between them is a creative decision, not a plan-gating issue. A marketing professional writing persuasive campaign copy for a product launch might reach for Claude Opus 4.7 for its editorial range. A UX designer drafting plain, functional microcopy for a checkout flow might prefer GPT-5.4 mini for its directness.

Ray, Stensyl's creative-decision assistant, helps with exactly that call. Describe what the copy needs to do and Ray will point you to the model most suited for the task. It is a fast way to avoid model indecision when a brief has to move from draft to page in the same session.

The Canvas LLM Chat node takes this further. Canvas is Stensyl's node-based workflow editor, and its LLM Chat node allows copy to be drafted and then piped directly into generation nodes. A web designer can refine messaging in the chat node and feed it into a page layout generation without copy-pasting between windows. The copy lives in the same workflow graph as the layout generation. When the copy changes, the pipeline updates, rather than the designer manually shuffling content between surfaces.

For teams, Projects holds the brand identity, copy drafts, and page assets in a shared workspace. A UX designer and a marketing lead iterating on the same campaign page are working from the same brief, the same assets, and the same copy drafts. There is no version-control friction from separate file systems or shared drives. The project is the single source of truth for the whole page.

Prototyping for Clients: What to Show and When

A Web Studio-generated page is not a wireframe. It has real copy, structured sections, and visual hierarchy applied. That makes it a credible starting point for a client presentation, not just an internal reference. The difference between showing a grey-box mockup and showing a layout with real content and structure is the difference between a concept and a near-final artefact. Clients respond differently to the latter.

For an automotive designer presenting a vehicle launch microsite, or an interior designer pitching a studio website to a prospective client, having a working layout in the room changes the nature of the conversation. Instead of asking a client to imagine what the page might look like, you are asking them which section needs adjusting. That is a more productive meeting.

Building and sharing a preview of a Web Studio page is available on every plan. Clients can review the layout before any hosting decision is made. Pushing the page live and connecting a custom domain requires Pro or Studio, so if the client review leads to a sign-off and an immediate launch, that step is where tier matters. On lower tiers, the full design and iteration workflow remains open. The hosting and domain connection is the paid gate, not the design work itself.

Iteration speed compounds the value here. Because generation is prompt-driven, updating a layout between client meetings is fast. A section reorder, a tone shift in the hero copy, a different visual weight on the feature list: these are prompt adjustments, not full redraws. A freelancer running three client projects simultaneously can move between briefs without the layout rebuild overhead that slows down traditional prototyping.

Boards adds a useful front-end to this process. Stensyl's Boards surface is a fluid canvas for collecting visual references and organising first and last-frame scenes for video generation. Before committing to a page layout, a designer can use Boards to lock the visual direction: gather reference images, establish a colour language, note the structural register. When the page generation runs, it draws on a brief that already has a clear aesthetic behind it, rather than one that is still being discovered mid-generation.

Credits, Plans, and What It Costs to Publish

Stensyl's pricing is built around a single credit system. Every surface, including Web Studio, draws from the same balance. There is no separate web generation subscription, no hosting add-on billed independently of the plan, and no model locked behind a higher tier.

Plan	Price	Monthly Credits	Concurrent Generations	Chat-Widget Messages	Web Publishing
Free	£0	150 one-time credits	1	20/day	Build and preview only
Lite	£10/mo	1,000	1	20/day	Build and preview only
Starter	£22/mo	2,500	2	Unlimited	Build and preview only
Pro	£42/mo	6,000	3	Unlimited	Live publishing + custom domain
Studio	£84/mo	12,500	4	Unlimited	Live publishing + custom domain

The Free tier is not a time-limited trial. Sign up without a card, receive 150 one-time credits, and access every model and studio on the platform. The credits do not reset monthly. For a designer evaluating whether Web Studio fits their workflow before committing to a paid plan, the Free tier is a genuine test environment, not a gated demo.

For a freelance UX designer or small creative studio running multiple client projects at once, Pro is likely the practical starting point. Three concurrent generations mean that a web layout, an image asset, and a motion graphic can process simultaneously. Six thousand monthly credits cover a full client sprint. And web publishing with a custom domain means client hand-off is handled inside the same platform where the page was built.

The Starter plan sits in a useful middle position for studios that need Canvas and Write workflows but are not yet publishing client-facing pages live. Two concurrent generations and 2,500 credits support the design and prototyping workflow without the hosting overhead.

Where Web Studio Fits in a Broader Stensyl Workflow

Web Studio does not exist in isolation. It is one surface inside Stensyl's Publish section, alongside Marketing and Editing. All three share the same asset pool and credit balance. That adjacency is not cosmetic. It shapes what is possible inside a single project.

A marketing team running a product launch can use the Marketing studio to build ad creative and social carousels, then use Web Studio to build the destination landing page. Both live in the same project workspace. The brand assets used in the ad are available in the web layout. The copy drafted for the ad informs the page headline. There is no file transfer, no version mismatch, no separate tool for each stage of the campaign.

A motion designer building a personal portfolio site can generate a layout in Web Studio, pull in motion graphics produced in the Motion studio, and publish without opening a third-party CMS. The Motion studio uses Remotion-based export, which means the output is production-ready. The web layout is already waiting for it inside the same project.

Canvas extends this further. Its node-based workflow means generation pipelines can feed Web Studio indirectly. Generate images in an Image Generate node, refine copy in an LLM Chat node, connect the outputs into a single canvas, and bring the assembled assets into a web layout when everything is ready. The page does not have to be built before the assets exist. The workflow can run in parallel, with the layout generated once the upstream inputs are confirmed.

The Research surface adds another layer for briefs that need grounding before layout generation begins. A content creator building a microsite around a new product category can run a Perplexity-backed research session inside Stensyl, extract the key claims and positioning points, pass them into Write for copy drafting, and carry the finished copy into a Web Studio brief. The research, the writing, and the page layout are all part of the same project record, rather than scattered across browser tabs and shared documents.

The practical value of Web Studio is not just generation speed. It is the removal of the context-switching that slows down every web project regardless of discipline. The switch from design tool to copywriting tool to CMS is where time disappears and creative intent dilutes. Keeping the brief, the assets, the copy, and the layout inside one platform removes those switches. The page you publish reflects the brief you wrote, rather than a compressed version of it that survived the hand-off.

For creative professionals across disciplines, from a graphic designer carrying a brand identity into a launch page, to an exhibition designer building an event microsite alongside physical production work, Web Studio is most useful when it is treated as part of the broader Stensyl workflow rather than a standalone tool. The generation is fast. The integration is what earns the time back.