V0 vs Figma Make. Designers experience prototyping from scratch 

I’ve recently been testing out Figma Make and seeing how it compares to v0. To keep it fair, I tested both on paid plans and used Make in the same scenarios as v0. I always start from a blank canvas, no library, no prepared design and the goal is always  to get a working prototype up and running fast.

What I noticed

Understanding prompts

• Figma Make: in some cases, the tool does not understand the command, even when the exact page and block are specified. For example, I asked to round corners on a card. It said “done”, but nothing changed. The system kept telling me that the process was complete, even though it wasn’t. After a long back-and-forth, I finally gave up. Even after rephrasing my inputs and restarting the system, the issue persisted.
• V0: follows commands more consistently.

Context and targeting

• Figma Make: if I don’t set the exact page and block in the prompt, edits often end up in the wrong place. In addition each time I open the prototype, it takes me back to the home page not the page I was working on.
• v0: content stays intact, edits go to the right place. The prototype opens on the same page I was working on.

Text and content

• Figma Make: it is not possible to rewrite text directly in the interface. Instead, all text edits have to be made through a prompt.
• v0: texts can be edited manually, headings can be replaced, and typos can be fixed without prompts.

Edits without prompts

• Figma Make: manual controls are very limited. For example, it is not possible to set font weight numerically. You can only toggle Bold, like in a basic text editor.
• v0: most tasks can be done by hand. I can adjust alignment, spacing, sizes, radii, colors, typography, position, shadows, and more.

Saving manual edits

• Figma Make: manual edits can be overwritten by the next prompt, so it is important to double-check them before saving.
• v0: edits are saved reliably using the save button and won´t be changed with the next prompt.

Media and formats

• Figma Make: accepts only raster images. SVG logos must be converted first.
• v0: accepts many file types, you can even make a table from an excel file. Places them correctly and adjusts size automatically.

Matching references and grid quality

• Figma Make: mainly generates basic layouts. If an element sits slightly outside a standard grid, the composition breaks. Getting a solid bento grid did not work on the first try.
• v0: most often gives a one-to-one match with the reference, including complex layered layouts.

Speed and predictability

• Figma Make: needs more iterations and checks, which slows down the progress.
• v0: I reached the desired result faster and with more consistency.

The prototype is ready. What next?

• Figma Make: this is a separate file type. You cannot bring it back into regular Figma Design or Figma Sites to continue polishing. You can publish the prototype, but the it lives on Figma’s side like Sites. When switching pages, the URL does not change. Because of that any workarounds and exports feel inconvenient.
• v0: the result is a React plus Tailwind project. You can hand it to developers or host it directly. If I need a mock in Figma, it is possible to import it with the html.to.design plugin and refine there.

Takeaway: The v0 → Figma Design flow is faster and more logical than Figma Make → Figma Design. With v0 I can build, export, and refine in one clear sequence. With Make, I spend extra time trying to understand how to transfer it to Figma Design. The ideal setup would be a single cloud flow where Design, Make, and Sites connect seamlessly, and switching between them feels natural.

My thoughts 

If I explain it with a simple metaphor. The two tools are like brothers in one family. v0 behaves like a diligent straight-A student. It understands the task, keeps context, and moves forward step by step. Figma Make feels like the restless brother who keeps forgetting where the door is and never quite remembers the route, even if directions are shown again and again. In professional terms, this is about predictability, control, and ability to stay stable through repeated changes. Right now, v0 gives me more of that.