Jenny Golden
Product Lead, Shepherd
Alloy is probably the one I use most, especially if I’m talking to users and showing them a prototype. It’s just easier for them to understand when it actually looks like our product.
Start with the interface running in your browser, make the change with an AI agent, and take the reviewed result into your codebase.
Free to start · No credit card required
Chrome extensionCapture the exact live state, including signed-in screens
Live UI, not a flattened reference
A screenshot preserves appearance but discards the system that created it. The DOM, layout rules, loaded fonts, images, and current interaction state all have to be guessed before an AI tool can write anything useful.
Alloy records the working page as the starting point. That gives the agent concrete UI context before you ask for a change, and it lets reviewers test the result inside a familiar product rather than interpret another detached mockup.
Move from the current browser state to a tested implementation path in three steps.
Product Lead, Shepherd
Alloy is probably the one I use most, especially if I’m talking to users and showing them a prototype. It’s just easier for them to understand when it actually looks like our product.
Backend Developer
I’m able to just ship things on my own without talking to anybody — I just use Alloy to do the design. It just fits in my workflow of just shipping things.
Product Designer, Disqus
Almost every day I’m using Alloy. My PMs also like it a lot, receiving the Alloy prototype to review and send some feedback.
Product Manager, PedidosYa
I think that your product is amazing. It’s one of the tools I use the most in my job and it really makes my life simpler when doing definitions.
Product Manager, Fanvue
You guys have built something that’s actually fundamentally very useful. If Alloy disappeared today, I’d be like, ah, what do I use now?
VP Product
I really like the Alloy app. I’ve already bought it at two companies.
Screenshot and design-to-code tools
Builder.io Visual Copilot, v0, Anima, and Locofy each offer capable paths from designs or visual references to code. Alloy is purpose-built for work that begins inside an existing, functioning product.
| Capability | Alloy | Builder.io Visual Copilot | v0 | Anima | Locofy |
|---|---|---|---|---|---|
| Primary source | A running browser screen or public page URL | A selected Figma frame or layer | A prompt, screenshot, mockup, or Figma design | A Figma file, image, or public website URL | A Figma, Penpot, or Adobe XD design |
| Signed-in product UI | Captures the state already open in your authenticated browser | Works from design files rather than a browser session | Accepts an uploaded image of a private screen | Uses a public URL or uploaded visual reference | Works from design-tool source files |
| Fidelity anchor | The captured page structure, styles, fonts, images, and visible state | Figma layout plus mapped design-system components | An AI implementation inferred from the supplied reference | Structure inferred from Figma, an image, or a public page | Design layers, constraints, and configured UI libraries |
| Code handoff | Shareable prototype, React export, or pull request in the connected repo | Framework code through Builder, an IDE extension, or CLI | Editable application code with a Vercel deployment path | React, HTML, and other export formats or a published site | Web and mobile framework code through download or CLI |
| Best fit | Changing and validating UI inside an existing live product | Moving polished Figma work into an established codebase | Generating new applications from conversation and visual inputs | Turning Figma, images, or public sites into frontend code | Structured design-to-code handoff across web and mobile |
Design-to-code products are often the right choice when the source of truth is a polished Figma file. Alloy is the better fit when the source of truth is the UI already running in front of a customer. For file-based conversion, start with image to HTML.
Screenshot to code is the process of turning a visual interface into editable frontend code. A conventional tool reads a PNG or JPG and writes a new implementation based on what the model can infer. Alloy can start from the live page instead, keeping the rendered structure and styling available while you make the change.
The Alloy browser extension records the page you are viewing as a high-fidelity capture, including its structure, presentation, assets, and current visible state. The capture opens in an AI prototyping session where you can request changes in natural language, inspect the result in the browser, and keep iterating without rebuilding the surrounding product.
An uploaded image contains pixels but no page structure, so an AI model has to infer the DOM, layout rules, fonts, assets, and behavior. Browser capture to code begins with the rendered page that produced those pixels. When a static file is the only source you have, Alloy's image to HTML tool supports that workflow too.
Yes. The extension works from the browser session you already authenticated, which makes it useful for account settings, internal operations tools, SaaS dashboards, and other screens a public URL service cannot reach. You should only capture interfaces and data you are authorised to use.
A live capture starts from the browser page's HTML and CSS. When you need a standalone handoff, Alloy can export the prototype as a React app. For an existing application, connect the repository so the agent can implement the approved change using that codebase's components and conventions.
Capture the state you want to work on while it is visible. An open menu, expanded panel, selected tab, or modal can become part of the editable prototype instead of disappearing into a generic reconstruction. Complex server-backed behavior may still need to be reconnected when the change moves into production code.
Yes. After you validate the direction in a capture-based prototype, you can use GitHub codebase connectivity to run the application in an Alloy workspace, apply the change to the repository, and open a pull request for engineering review.
Product managers and designers use it to propose changes that already look at home in the product. Researchers use it to test alternative flows with familiar UI. Engineers use it to remove ambiguity from implementation discussions and, when a repository is connected, turn the agreed direction into reviewable code.
You can capture product screens, edit prototypes, and share them on the free plan without a credit card. React code export is a Pro feature, and repository workflows may depend on your plan. The pricing page lists the current limits and team features.
Only capture and reuse interfaces, content, data, and assets that you own or have permission to use. A capture is designed for legitimate product work such as prototyping changes to your own application, evaluating authorised client work, or documenting an approved internal workflow.