Lovable vs Bolt vs v0: what each one ships.

What are Lovable, Bolt and v0, and who are they for?

You are choosing between three AI app builders that turn your written description into working software. Open Lovable's comparison guide and you will see the split. It calls Lovable your route from description to full-stack app on React and Supabase. Bolt is code-first, with a browser-based editor you work in. And v0 generates full-stack Next.js apps with API routes.

Build This Now frames the choice by audience. Pick Bolt if you are technical and want control of your code. If you are a non-technical founder building a full-stack MVP, pick Lovable. Designers and developers who already work in Vercel and Next.js should pick v0. Lovable's guide recommends Lovable for visual full-stack creation, which you would expect from a Lovable page, so read it as a vendor's view. Whichever you pick, judge it by what your site ships to a browser. The label tells you little, and the output tells you everything.

What stack does each one generate?

Your project gets React and Tailwind, whichever you pick. The framework differs: Vite or TanStack Start on Lovable, Next.js on v0, and your choice of JavaScript frameworks on Bolt. Your package file shows which one you are on. Reflex says you can build on Bolt with React, Vue, Svelte, Next.js or Astro, while v0 ties you to React and Next.js. But Vercel says Lovable gives you TanStack Start, with no framework selection.

Your Lovable stack depends on when you started, and the sources disagree. A DEV Community post lists the old stack your older projects use: React with TypeScript, Vite, Tailwind, shadcn/ui and React Router. Reflex says projects you created since May 2026 use TanStack Start, while older ones stay on Vite. Another source puts the shipping date at 20 April 2026. Check your creation date against your package file. Need mobile? Your only listed option is Bolt, through React Native and Expo. Pick v0 and you get Tailwind v4, per Vercel's knowledge base.

How do their sites render, and what does that mean for search?

If you built with v0 or started a new Lovable project, your pages are server rendered by default, and you can confirm it. But if your Lovable project is older, you ship client-side React. For Bolt, the sources give no default, so check your own output. Run view-source on your page and look for your headline in the HTML. Missing? Then crawlers get an essentially empty shell (The SEO Agent recommends the same test). Before the change, Lovable acknowledged that you could wait 'days instead of hours' for indexing, and that your social previews were broken by default. That is a rough start for a launch.

Vercel says your v0 site uses the App Router and Server Components, so your pages return full HTML at request time. But the sources disagree on the date, so check yours. One says you get server rendering if you created your project on or after 20 April 2026. Reflex says you have had it since May 2026. And The SEO Agent says the 13 May 2026 announcement also gave your existing apps pre-rendered snapshots, served to verified crawlers. Rendering is only your first gate. Check your robots.txt and your sitemap too, and verify both on your domain before you call your launch ready.

Which one handles hosting, auth and data, and which hands you code?

Lovable and Bolt come with hosting and a backend built in. v0 takes a different route: it relies on Vercel hosting and database integrations. All three give you a codebase. In Lovable's table, your backend is Supabase (Lovable Cloud) if you choose Lovable, Bolt Database if you choose Bolt, and API routes plus database integrations if you choose v0. So your pick sets your backend, and that is worth weighing before you commit. Bolt's blog says Bolt Cloud gives you authentication, databases, storage and server functions, plus hosting, Code View and GitHub integration. On Bolt, your backend and your host arrive as a pair (which is either convenient or confining, depending on your plans).

Build on v0, and Coursiv says your apps are full-stack Next.js, but v0 hosts no database for you. You connect Supabase, Neon, Upstash and Vercel Blob through the Vercel Marketplace. Lack coding experience? Coursiv says Lovable is easier for you, because hosting, database and sign-in come built in. Vercel says your new Lovable projects export by Git sync to a new repository, while v0 can work from your existing GitHub repositories. Either way, your repository holds your code. Build This Now warns that you will have to harden whichever codebase you pick, so plan that work before you ship your app. And the real prize is ownership: once you have real users or payments, owning your code is what pays off.

Where do sites from each tool usually lose points?

The public sources publish no per-tool score data, so the honest answer is that each tool's defaults leave gaps in what you ship. View the source of your page. Check your HTML body, your headings, your structured data and your `robots.txt`. If you built on an older Lovable project, an empty shell can cost you points (and you may not notice until someone looks). A DEV Community post says Google takes approximately 9x longer to index JavaScript-heavy pages than static HTML, so look at what your body holds on each page. LaSoft says Lovable's Cloud Only tier lets you edit your meta tags, titles and descriptions, but server-side rendering and structured data in depth are out of reach. And that ceiling is real, not a quirk you can configure away. Check your tier before you plan your fixes.

Server rendering still leaves gaps in your build, so open your `robots.txt`. A write-up says a server-rendered Lovable site can still have `robots.txt` problems, and yours may be one of them. The SEO Agent says keeping your sitemap accurate and submitting it to Google Search Console is your job. Verify yours. On v0, Vercel says hand-rolled components do not inherit shadcn/ui's accessibility primitives, so audit yours against WCAG criteria. For Bolt, the sources describe no rendering default, which means you shouldn't assume one for your site. Your own public read of your site settles it. A brochure never will.

Which should you choose for a marketing site, a dashboard, or a prototype?

Choose by rendering for your marketing site, by code control for your dashboard, and by working style for your prototype. On your marketing site, view your source and confirm your copy sits in your HTML. Vercel says v0 returns full HTML at request time, and sources say your new Lovable projects are server rendered, so you can check yours. Building a marketing site rather than an application? Reflex lists Framer as the better fit.

For your dashboard, Build This Now points you to Bolt if you are a technical builder who wants code control. Your backend choice matters too: Lovable's table lists Supabase as its backend, and v0 generates API routes and database integrations for you. For your prototype, only Lovable among the three gives you a point-and-click visual editor, while your v0 Free plan has a daily limit of 7 messages. Whatever you pick, plan to harden your code before real users or payments arrive (doing it before costs you less than after). Nobody enjoys that bill late.

How do you check a site built with any of them?

To check your site, run the free assessment on your live URL and read the evidence behind your score. You enter your URL and a work email. In about two minutes you get your score out of 100 across eight weighted pillars: architecture 15%, performance 15%, security 12%, search 12%, schema 10%, AI readiness 10%, editorial experience 10% and operational health 16%. And the evidence sits behind every one of them.

It reads your homepage plus up to eight sampled pages, and you see your headers, markup, structured data, headings, script and image weight, and your robots and canonical signals. You hand over no login, analytics or field performance data. Nobody interviews you. A score of 80 to 100 is good standing, 60 to 79 constrained, 40 to 59 at risk, and 0 to 39 legacy condition. Pair your result with the view-source test on a page you care about. Your connection gets three checks per hour, so make one fix, then recheck your URL. That loop beats any guess.

Questions, answered.

Check your own site.

1. 01Next.js SEO auditRendering mode, metadata, hydration cost.
2. 02Website health checkThe general read, all eight pillars.
3. 03Core Web Vitals testLCP, INP and CLS from what the page ships.

More from What Ships.

1. 01AI code vs human code: what the difference looks like on a live website.Evidence · 2026-10-25
2. 02How to build a website with AI without the mistakes everyone makes.Guide · 2026-10-25
3. 03Vibe coding security: what shipped AI sites leak, and how to see it from outside.Security · 2026-10-25