The closest swap for Onlook is another in-repo visual editor: an extension that runs inside VS Code or Cursor, or an open-source React editor you embed in your own app. If you'd rather not touch a repo at all, a hosted visual builder that exports code fits better, and if your work starts in Figma or a prompt, go design-to-code or an AI app builder.
Onlook is a free, local-first, open-source visual editor that lets designers work directly in a real React or Next.js codebase. You can self-host it from GitHub without paying a thing, while the hosted cloud version is sold through a contact form or a demo rather than a plan you switch on yourself.
So another kind of tool fits better in a few situations: you want visual editing in your repo without hosting anything yourself, you'd rather design in the browser and export, or your work starts in Figma or a prompt instead of in code.
The bottom line on Onlook alternatives
If what you liked about Onlook was editing the code you already own, stay in that family. An editor extension keeps you inside the IDE you use every day, and an embeddable open-source React editor puts visual editing into your own product, built from your own components. Neither asks you to move your site anywhere.
If the repo was the part you didn't enjoy, a hosted visual builder is the better move. You design in the browser, then publish to the vendor's cloud or export the code when you're ready. That's a different contract: you're trading some control for speed, and I'd use one for marketing sites and landing pages rather than a complex app.
If your designs already live in Figma, skip the editor question and look at design-to-code tools, which turn frames into React or HTML. And if you'd rather describe a screen than draw it, I'd reach for a prompt-first AI app builder, then expect to spend some time making the code it writes feel like yours.
I'd start with an in-repo editor for any team that already has a codebase, and a hosted builder for anyone starting from a blank page.
Visual editors that work on your own code
Pinegrow Piny
A visual editor for React, Next and Tailwind projects that runs inside VS Code and Cursor, so you stay in the editor you already use.
Puck
Open-source React editor you embed in your own app, letting your team and agents build pages from the components you've already written.
GrapesJS Studio
For product teams who want to hand their own users a drag-and-drop editor for emails, landing pages and sites, this is an embeddable SDK with an AI assistant.
Builder.io
Designers, engineers and marketers edit the same codebase visually here, with AI agents and pull requests keeping developers in the loop.
Hosted builders, design-to-code and prompt tools
Plasmic
A hosted visual builder that sits on top of your own tech stack, made for whole teams while developers keep hold of the code.
Webstudio
Open source, with full CSS access, an MCP and AI built in; publish to its cloud or export the site and host it yourself.
TeleportHQ
Low-code and AI-assisted, this design-first builder is aimed at static sites and individual UI elements.
Locofy
When the design already lives in Figma, Penpot or Adobe XD, this plugin, CLI and MCP turns it into React, Next.js and other front-end code.
Anima
Another route from Figma to front end: it turns designs, or a typed prompt, into working code you can export as HTML or React.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
v0
Vercel's prompt-first app builder generates a working web app, lets you tweak it visually and syncs the code to GitHub.
An afternoon test on a real branch
Don't judge any of these on a demo project. Make a throwaway branch of your real codebase, or export a real Figma frame, and run the same small job through your top two picks:
- Change the spacing and colour of one existing component and look at the diff it produces.
- Add a new section built from a component you already have, not one the tool supplies.
- Hand the result to a developer and ask whether they'd merge it as it stands.
- Undo everything and check the repo is back exactly where it was.
If the diff is clean and readable, you can live with the tool. If it rewrites files you didn't touch, adds wrapper markup or invents its own styling layer, you've learned what working with it day to day will feel like. For hosted builders, swap the diff for an export: open the exported code in your editor and ask yourself whether you'd want to maintain it.
Keeping an exit route open
Visual editors come and go. One React visual editor now shows a notice that its journey may be over and points users to a successor, which is a good reminder to check a tool is still being built before you commit a team to it.
I'd favour picks that leave you holding plain code you can keep using without them. With an in-repo editor the files stay in your repo. With a hosted builder, check the export before you build anything big: can you take the whole site out, and does it run without the vendor? If you're weighing a hosted builder against the bigger no-code names, these Webflow alternatives cover the publishing side in more depth.
Three questions that narrow the field
Will the work live in your repo or in theirs? Some of these tools edit your own repo in place; others are hosted builders you export from. I'd ask whether each visual change lands somewhere a developer can review it. If your team reviews everything in pull requests, a hosted builder can feel like a side door.
Do you want to run it yourself? Onlook sits under the Apache licence, so if licence matters to you, the open-source options are the nearest match: one is MIT licensed, and another open-source builder lets you export and host the site yourself. Self-running costs nothing in licence fees but plenty in your own time: updates, hosting and fixing it when it breaks. A paid cloud plan hands that work to the vendor.
Where does the work begin? If you start from Figma, design-to-code tools save the redraw. If you start from a sentence, a prompt-first builder is the natural fit, and there's a wider field of those in this round-up of v0 alternatives. If you start from an existing product, you want something that edits what's there. And whoever ends up doing the daily editing, whether that's a developer, your content team or your customers, should try the tool before you sign up, not after.
Do you make visual editors and builders for React and Next.js? Tool makers can ask to be considered for a featured place on this list.
What to read on each pricing page
Pricing in this category is mostly monthly with a free tier, and design-to-code tools charge by AI credits or usage limits on monthly plans rather than per seat. Beyond that, plans vary, so the figures that matter sit on each vendor's pricing page. These are the questions I'd take to it:
- Is the free option a full free plan, a free trial or open-source code you run yourself?
- Am I paying per user, per plan or by AI credits, and can I buy more credits when I run out?
- If the editor is open source, what does the vendor's own cloud cost once I use it in production?
- Is the headline figure billed monthly, or only when I pay for a year up front?
The cheapest route on paper is self-hosting open source, but count the hours. If nobody on your team wants to own updates, I'd pay for a modest hosted plan instead.
And if what you want is an AI that writes the app for you rather than a canvas to edit it, you're in a slightly different category; this list of Lovable alternatives is the better starting point.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.


