Subframe review

Subframe is a codebase design tool that puts a design canvas, browser preview and coding agent in one workspace. Its canvas is built with HTML and React, rather than treating designs as static mockups. The product description says that means designs can be implemented as designed.

The canvas supports drag-and-drop editing, layers and an inspector. You can view and capture pages in a browser alongside the canvas, while the agent can help with design and building. Subframe’s homepage says it works with Claude Code and Codex. Its agent can also research a codebase and create design variations, according to the product description.

That makes Subframe aimed at teams that want design work close to the codebase, not just a place to hand off visual files. The key question before switching is whether its coding workflow fits your setup—and what it costs. The available pricing information leaves the second question open.

Subframe’s clearest advantage is that design and implementation share a foundation. The canvas uses HTML and React, and the product description says designs can be implemented as designed. That could reduce the translation between a mockup and working UI, though the published information does not quantify any time savings.

The combination of canvas and browser preview also keeps page design and rendered pages close together. Layers, drag and drop, and an inspector provide familiar controls for making and examining changes. For code-first teams, that is a more direct fit than a design workflow built around static mockups.

The coding agent adds another potential use: it can research a codebase and create design variations, rather than only generating a fresh interface without project context. The homepage also names Claude Code and Codex as compatible tools, giving teams using either a stated path to connect their coding workflow.

• The canvas is based on HTML and React.
• Browser preview sits alongside the design canvas.
• The agent can research a codebase and make design variations.

Those are useful ingredients for a design-to-code workflow. The published information does not explain how the agent’s research works or what project setups it supports, so teams should verify fit before moving an established process.

The biggest switching concern is pricing. The available pricing information indicates a free plan, but lists no plan names, prices, paid tiers, add-ons or feature caps. Monthly and annual billing details are also not published. That is too little to estimate what a team would pay after trying the free option, and the pricing data is marked low confidence. Check Subframe’s current pricing page before building a budget around it.

The published product information also leaves practical limits unanswered. It gives no published caps for projects, seats, canvas work or agent usage, and does not specify which codebases or frameworks the research feature supports. Although the homepage says Subframe works with Claude Code and Codex, the available details do not describe setup requirements or the scope of that compatibility.

That does not establish that Subframe lacks those options; it means we cannot confirm them from the available information. For a team considering a switch, the product is worth evaluating for code-first design, but feature fit and total cost remain questions to settle first.

We can’t give you a reliable total from the available pricing information. The pricing record, checked November 7, 2026, marks a free plan, but does not list what it includes, any paid plan names or prices, or add-ons. The starting price is not published, and monthly versus annual billing options are also not published.

That means there’s no documented tier jump to compare and no way to calculate whether annual billing saves money. Don’t treat the free-plan flag as proof that the features your team needs are free; the available details don’t establish its limits or what requires payment.

Before switching, ask Subframe for current plan prices, usage or seat caps, what the free plan includes, and whether any features cost extra. Until those details are public, budget only after getting a quote in writing. Subframe may suit code-first design, but its pricing is a real gap for buyers comparing published plans.

Subframe’s HTML-and-React canvas and codebase-research agent may fit teams that want design work close to implementation. But the available material doesn’t explain how to import an existing project, export designs, or keep canvas work in sync with a repository. Those are the first things to confirm before moving a production workflow: ask what files and components you can export, what remains in Subframe, and how the agent’s changes reach your codebase.

The lock-in risk is therefore unclear, not proven. HTML and React are familiar technologies, but that alone doesn’t tell us whether a project can leave Subframe cleanly. We also don’t have Reddit posts or comments in the published sources, so we can’t responsibly report why users leave or whether migration problems are common. If you’re switching away, test a small project’s export path and confirm what happens to browser previews, design variations, and project history before committing. Pricing is another unresolved switching question: paid plans and limits are not published.