v0 by Vercel: Features, Pricing, and Limits

v0 is Vercel's browser-based platform for generating screens and full-stack web apps, meaning the interface and server code, from prompts, screenshots, Figma files, or existing repositories. It now includes an AI agent, an isolated preview, saved Git code changes, database connections, and direct Vercel publishing.

Choose v0 for a React or Next.js project that already uses GitHub and will deploy on Vercel, and expect more setup and less benefit outside that stack. Generation credits and hosting costs are separate considerations once you have a working app.

See our introduction to vibe coding for the broader approach behind prompt-based app building.

What Is v0, and Who Is It For?

v0 is Vercel’s AI app builder for React developers and technically literate designers who want to turn prompts or designs into editable web applications. It creates a working branch, commits changes, and opens a pull request while leaving the selected base branch protected.

The underlying stack favors Next.js and React with TypeScript, Tailwind CSS, shadcn/ui, and Radix UI primitives. Because Vercel builds v0 and runs the surrounding Next.js deployment platform, one click can take a generated project to a Vercel preview URL.

v0 fits when you can review a codebase and want AI to accelerate frontend and Next.js work.

Its interface also serves founders and designers, but the generated project remains code that someone should inspect. The fit becomes weaker when nobody owns the stack, access rules, environment variables, or production deployment after generation.

What Can v0 Do?

v0 can turn a text brief, screenshot, or Figma frame into a working interface. Vercel's Figma guide supports file or frame links on paid plans and reads layout, tokens, text, and assets for the requested flow.

The current model lineup is v0 Mini, v0 Pro, v0 Max, and v0 Max Fast. The live pricing page also publishes separate input, cache, and output token rates for each tier.

The full editor and agent can work across files, run shell commands, inspect a repository, execute tests, and call Vercel or GitHub tools. Vercel documents those actions as agent capabilities in the product.

That is closer to Bolt or Replit, although v0 remains more tightly integrated with Vercel for Next.js projects.

Git integration supports a familiar sequence: generate a component or feature, push to a working branch, review the GitHub pull request, and merge after the repository's checks pass. Teams already using GitHub and Vercel can review changes and preview the app through the tools they already use.

What Are v0’s Main Strengths?

v0’s main strengths are its React and Next.js focus, design inputs, and integrated GitHub-to-Vercel workflow. Its documentation emphasizes expertise on Next.js, React, Tailwind CSS, shadcn/ui, and the AI SDK. That stack focus gives the agent a clearer default than a platform trying to treat every framework the same.

The Vercel integration gives Next.js projects a short path from generated code to a preview URL. Other platforms can deploy to Vercel, but v0 shares projects, environment variables, integrations, domains, and deployment state with the Vercel account.

The v0 model tiers let you trade speed and cost against reasoning depth. Mini is the low-cost option, Pro is the balanced default tier, and Max or Max Fast cost more for difficult work. Read the live token rates before choosing one for a long generation.

Git Import puts changes to an existing project on a branch you can review, rather than making you copy and paste them. That workflow is easier to audit because the pull request shows exactly which files the agent changed.

What Are v0’s Main Limitations?

v0’s main limitations are its strongest fit with the Vercel stack, usage-based generation costs, and the need for someone to review the resulting code. Git Import lets v0 work with an existing repository, and GitHub becomes the source of truth. The simplest preview and production path still assumes a connected Vercel project.

v0 can generate Next.js server actions and API routes, then connect to Supabase, Neon, Upstash, and Vercel Blob. Complex services outside that model still need separate architecture and deployment work, so check which backend services you would need to host separately before choosing v0 for the whole application.

The credit model gives you token rates for each v0 model, while the final cost still depends on input context and generated output. Check the usage screen after a small task before estimating a long session.

v0 expects someone to review code, branches, environment variables, and deployments. A team without that owner should compare the more managed workflows in the vibe coding comparisons before committing production data.

How Much Does v0 Cost?

v0 has a free plan, Plus at $30 per user a month, and Business at $100 per user a month. Generation uses credits; Vercel hosting and connected services can have separate charges.

Plan	Price	Credits and limits
Free	$0	$5 one-time for new users; 7 daily messages
Plus	$30/user/mo	$30 monthly; $2 daily login
Business	$100/user/mo	$30 monthly; training opt-out
Enterprise	Custom quote	SAML SSO; RBAC; SLAs

Plus and Business accounts can purchase more credits. Plus also includes shared chats and central billing, while Business adds training opt-out by default.

The dollar-denominated balance still maps to model-specific input, cache, and output rates. A longer repository context or a higher-cost model can consume more of that balance, so check the usage record after the same small task used in any platform comparison.

How Do You Start a Project in v0?

Start a v0 project with a text prompt, a screenshot or Figma design, or an existing GitHub repository. A blank prompt works for a new page or a small app with a settled goal. Name the users, main screen, data source, and one action that must work. Ask for the interface first when the data model still needs discussion.

A design input works when visual intent already exists. Attach one Figma frame or screenshot, then check spacing, responsive behavior, keyboard focus, and component states before asking v0 to add backend logic.

Git Import is the path for an existing codebase. The Git Import guide supports public repositories, private repositories, and monorepos that the installed Vercel GitHub App can access.

v0 creates a dedicated working branch from the chosen base. Generated changes are committed to the working branch and previewed through Vercel. Review that branch through a pull request before merging into the base branch.

Starting point	Useful input	First check
Blank prompt	Users and one task	Scope and data flow
Figma or image	One clear frame	Responsive states
GitHub import	Repo and base branch	Diff and tests

How Do You Turn a Design Into Usable Code with v0?

Turn a design into usable code with v0 by supplying a focused screenshot or Figma frame, specifying interactive states, and reviewing the generated components against your project’s conventions. Before generation, list the interactive states the image cannot show: loading, empty, error, validation, keyboard focus, long content, and narrow screens.

For a large Figma file, name the page or flow you want v0 to build. Start with one component or page region, compare it against the source at desktop and mobile widths, and correct the design tokens before composing the full route.

Give repeated colors, spacing, and typography a named home in the generated project. A request such as Use the existing design tokens and components; report any missing token before adding a new value limits one-off styling and produces a smaller diff.

When v0 opens a pull request, review the semantic structure before pixel detail. Check heading order, form labels, button names, focus behavior, image alternatives, and the DOM order used on small screens. A close screenshot match can still leave keyboard and screen-reader users with a broken flow.

Next, check how the generated code fits the rest of the project. Confirm that the generated component uses the repository's existing primitives, data-fetching pattern, route structure, and test setup. Reject a parallel component library or duplicate helper unless the change explains why the existing code cannot serve the requirement.

The final check is responsive behavior with real content. Use long names, missing images, validation errors, and an empty result set. Design input gives v0 a useful starting shape; repository conventions and state coverage determine whether the result belongs in the product.

For repeated work, Design Systems 2.0 can save your team's components, shared style values, and conventions for later chats. Supply the actual component source and an app that uses it, then review the starter before saving it. This gives future screens a consistent foundation instead of another description of your brand.

Can v0 Build the Backend?

v0 can generate a Next.js backend and connect database and storage services. Vercel's full-stack guide documents Next.js server actions and API routes as v0's primary backend path. It also lists Supabase, Neon, Upstash, and Vercel Blob among the database and storage connections.

Each connection introduces credentials and provider-specific access rules. Store secrets through the environment-variable interface, use server-only variables for privileged keys, and verify which values are available in preview and production. A successful preview can still use a different database or missing secret after deployment.

Database work needs a schema review and two-account authorization test. Inspect migrations, uniqueness rules, foreign keys, indexes, and row-level policies. Then create records as one user and attempt to read or change them as another user through both the interface and a direct request.

How Do You Recover a Broken v0 Project?

Recover a broken v0 project by restoring the last working generation from the version menu, then checking the restored preview and any external data separately. v0 creates a new latest version from the restored code, so the failed attempt stays in the chat history. Narrow the next prompt to one failed behavior and name what must not change.

If repeated repairs fail or a change affects private data, payments, or secrets, pause further generation. Keep the working version deployed while a qualified reviewer checks that path. Restoring generated code does not prove that an external database was rolled back.

A Vercel preview proves that the project builds and serves a page. Data rules, error paths, and payment safety need separate checks while the work still sits on the v0 branch.

Start with the generated diff, the list of files and lines changed on the v0 branch. Open it in v0 or the GitHub pull request, then look for new dependencies, public environment variables, broad database policies, and server actions that trust browser values.

Any secret prefixed with NEXT_PUBLIC_ becomes available to client code. Keep privileged service keys in server-only variables and check the preview and production settings separately.

Run the repository's existing checks from the sandbox or continuous integration. A useful request is: Run the unit tests, report every failure, and do not change code until you explain the likely cause. That keeps diagnosis separate from a broad repair pass.

How Does v0 Compare With Other Builders?

v0 occupies the React and Vercel-focused part of the platform category. Managed app builders put more backend setup behind their own services, while editor tools such as Cursor or Copilot begin inside an existing local repository.

The closest comparison is with Lovable and Bolt. All three can produce a running application from a prompt. v0 concentrates on React and Next.js output plus the Vercel workflow.

Lovable provides a more managed backend experience for non-developers, while Bolt keeps a browser terminal and broader scaffolding workflow central. Replit covers more languages through a full cloud IDE.

For the closest matchups, see v0 versus Bolt and Lovable, Bolt, and v0 compared. For a broader comparison, the vibe coding comparisons hub breaks down the full category.

v0 Verdict

v0 is the best match among these browser builders for a React or Next.js project that already uses GitHub and will deploy on Vercel. Its branch-based import path makes generated work inspectable, while teams outside that stack should expect more setup and less benefit from the platform's tight Vercel connection.

Frequently Asked Questions

Which frameworks does v0 handle best?

Vercel's documentation says v0 supports popular frontend frameworks and UI libraries, with its strongest expertise in Next.js, React, Tailwind CSS, shadcn/ui, and the AI SDK. Other frameworks can work, while the official full-stack guide calls Next.js the most reliable route for server actions, API routes, and Vercel deployment.

How much does v0 cost?

v0 Free includes $5 in one-time credits for new users and seven messages a day. Plus costs $30 per user monthly with $30 monthly credits and $2 in daily login credits. Business costs $100 per user monthly with the same included credits plus training opt-out, while Enterprise uses custom pricing.

What models does v0 use?

v0's pricing page lists v0 Mini, v0 Pro, v0 Max, and v0 Max Fast model tiers. Vercel AI Gateway is a separate integration that v0 can add to an application you are building, giving that app access to external models.

Can v0 build a full-stack app?

v0 can build full-stack Next.js apps with server actions, API routes, database and storage integrations, and Vercel deployment. Its documented integrations include Supabase, Neon, Upstash, and Vercel Blob. Next.js is its most reliable full-stack path. Complex services outside that model still need deliberate architecture, security testing, and cost controls.

Can v0 work with an existing GitHub repository?

v0 Git Import can open a public, private, or monorepo project that your Vercel GitHub App can access. v0 creates a working branch, commits generated changes, and opens a pull request rather than modifying the base branch directly. Once connected, GitHub is the source of truth, so protect the repository and review every generated change.

Pricing and Git Import behavior were checked against official sources on October 17, 2026.