How to deploy a v0 project: Vercel, GitHub, and your own domain

v0's deployments docs, last updated November 13, 2026 and read on November 14, 2026, open with “v0 deploys projects to Vercel.” You select Publish in the chat header, and the first publish walks you through the Vercel project, who can open the app, and its domain before it starts “the production deployment.” The app gets a vercel.app address, and “Future production deployments update the app at that URL without changing it.” A project connected to GitHub publishes through a pull request that v0 merges. The deploy goes to the Vercel team the project lives in, so Vercel's plan applies: Hobby is free, and Vercel Pro is $20 a month.

Every quote below comes from v0's docs and pricing page and from Vercel's docs, pricing, and terms, read on November 14, 2026 (JST). Each v0 docs page quoted here is marked last updated November 13, 2026. Prices are in US dollars. Who owns v0's output and when a site counts as commercial are on Can you use v0 output commercially?

Deploy a v0 project

The first publish, as v0's deployments docs give it:

1. Select Publish in the chat header.
2. Create project. “Confirm the Vercel project name if the chat is not already connected to one.” v0's Vercel docs add that “The first time you deploy a v0 chat, a corresponding Vercel Project is automatically created.”
3. Visibility. “Choose who can access the deployed app. Available choices depend on your team's plan and deployment protection settings.”
4. Domains. “Confirm the provided vercel.app domain, select a connected custom domain, or open Vercel to add one.”
5. Commerce mode, when needed. If the app has an unclaimed Stripe test sandbox or Shopify development store, choose whether to claim it.
6. Publish. v0 starts the production deployment, and a deployment card reports the build's progress and its final state, with links to the site, the build logs, and Vercel's deployment inspector.

To publish updates, open Publish, review the production deployment and the domain, and select Publish Changes. “Projects without GitHub deploy the chat's current code directly to the connected Vercel project.”

Preview and production are separate. “Preview deployments are built from working branches. They have unique URLs and do not change the project's production URL.” Only publishing updates the production URL.

Build settings, environment variables, Deployment Protection, analytics, logs, and rollbacks live in the Vercel project, which the deployment's inspector link opens.

What v0 and Vercel charge for a deployment

A deployed v0 project runs on 2 plans. The v0 plan pays for generating code with credits. The Vercel plan of the team the project lives in governs the deployed app. v0's Vercel docs answer “Do I need Vercel Pro to use v0?” with “No, Vercel Pro does not provide any additional v0 features,” and add that “v0 accounts are just Vercel accounts.”

v0's docs don't say whether selecting Publish spends v0 credits. Fixing a failed build can: paid plans get some free fixes a day on unedited code, and “after that, fixes cost credits like a normal prompt.” The docs leave the number of free fixes blank. “When credits are used up, generation pauses,” and v0 Free can't buy more.

On Hobby, Vercel's Hobby docs, last updated November 12, 2026, say “if you exceed your usage limits on the Hobby plan, you will have to wait until 30 days have passed before you can use the feature again.” Section 4 of Vercel's terms, last updated October 19, 2026, says “You shall only use the Services under a Hobby plan for your personal or non-commercial use,” and that Vercel can “disable or remove any Project or website deployment on the Hobby plan with or without notice.” Can you use Vercel's Hobby plan for a commercial site? and Vercel Hobby plan limits go through both.

Deploy v0 to GitHub

v0's GitHub docs connect a project to a repository, and then publishing runs through it.

1. Connect the repository. Open the Project menu ... → Settings → GitHub and select Connect. Under Git Scope, pick the GitHub account or organization, enter a Repository Name, and select Create Repository. “v0 creates a private repository and pushes the project's current code to it.”
2. Work on a branch. v0 commits each code change to a working branch, never straight to the base branch. “Each working branch gets its own Vercel preview deployment.”
3. Publish. Select Publish, confirm the domain and visibility, and select Publish again. “v0 creates a pull request if the branch does not have one, or reuses its existing pull request. It then merges the pull request into the base branch and waits for the production deployment.”

• The repository becomes the source. “Once a GitHub repository is connected, it becomes the source of truth for your project's code. If you delete the repository, the code may become unrecoverable.”
• Branch rules apply. “Required checks, required reviews, draft pull requests, and other branch protections can block the merge.” v0 keeps the pull request open and says what needs attention.
• Import works the other way. Import from GitHub starts a chat from a repository you have. If the repository is missing from the list, install the Vercel GitHub App for that account and give it access.
• Permissions differ. “GitHub sync moves code between v0 and GitHub. It does not grant permission to deploy through GitHub or other Vercel interfaces.”

Add a custom domain to a v0 site

v0's custom domain docs start from the same menu: Publish → Customize Domain, or Project menu ... → Settings → Domains. Select Add, and you get 2 choices:

• A vercel.app domain. “These are free and instantly available,” with HTTPS set up for you.
• Your own domain. Enter it, such as myapp.com, then “Click "Inspect on Vercel"” from the Publish menu and configure the DNS records at your registrar, following Vercel's instructions.

Vercel's domain docs, last updated September 16, 2026, say “Hobby teams have a limit of 50 custom domains per project,” so a free Vercel team connects your own domain. For an apex domain such as example.com, “Vercel will prompt you to add the www subdomain prefix.” In v0, “Custom domains available to assign to your v0 application are inherited from your Vercel Project and team,” and “Unverified domains must be verified in Vercel before you can select them.”

Deploy v0 code somewhere else

v0's FAQ says “For the full experience (environment variables, deployments, previews), your GitHub repo should be connected to a Vercel project. You can still export code and deploy elsewhere.” The ways out its docs describe are GitHub sync and, in the Code tab, Download file for the file you have open. They don't describe a download of the whole project as a .zip in the app.

A v0 project is a Next.js app: “v0 uses Next.js, React, TypeScript, Tailwind CSS, and shadcn/ui.” For full-stack features it uses “server actions and API routes,” and it connects to databases such as Supabase, Neon, and Upstash. Another host has to build and run that app, with its environment variables, which v0 keeps in the Vercel project. v0's docs don't name another host or give its steps.

v0 deploy errors and fixes

v0's deployments docs list these problems:

A single HTML page instead

Some v0 projects are one page with no backend: a landing page, a waitlist, a portfolio. That kind of page can go on Convika without a Vercel team. Convika hosts one HTML page at a lasting link. It runs no server code: no Next.js server, no server actions, no API routes, no database. A page's scripts can't send requests to another site's API either, so calls to Supabase or Neon fail on Convika. If your v0 app saves data, logs people in, or uses server actions, Convika is not its host: keep it on Vercel.

A v0 project doesn't upload as it is. It is a Next.js app, and Convika takes one .html or .htm file up to 2 MB, pasted code, or a built folder whose index.html the upload box can combine into one file. For a page with no backend, there are 2 ways in:

• Rebuild it from the vercel.app link. The page must be public. Paste the link into the free rebuild tool and click Rebuild my page, with no account. It writes a new page in your page's colors and fonts and lists what it changed. The rebuild is a new page, not a copy of your project.
• Ask an AI for one HTML file. Paste the page's code into ChatGPT, Claude, or Gemini and ask for “one HTML file from <!DOCTYPE html> to </html>, with no build step, the CSS and JavaScript inside it, and full https:// links for images.”

Free includes 1 published page, 1 custom subdomain such as www.yourbrand.com, a form that keeps entries, 10,000 page views a month, and 90 days of visitor stats, with a small Convika bar at the bottom. Pro costs $12 a month and removes the bar. Section 7 of the terms allows commercial use on every plan, Free included.

Publish a v0 landing page on Convika

1. Get the page as one HTML file

Save the single HTML file an AI wrote from your page's code. For a page you'd rather rebuild from its public vercel.app link, use the rebuild tool instead and skip to step 3.

2. Drop it in the upload box

Drop the .html file in the upload box at the top of this page, or open Paste code and paste it. Click Get my preview link. The preview works for 3 minutes, with the page's scripts and forms off, and needs no account.

3. Keep the page and publish it

Click Keep this page — free, no card and sign up. On the page's screen, click Publish page, choose Public, and click Next. The first time, click Publish free. The page goes live at an address like yourpage.convika.page, with the Convika bar at the bottom.

v0 on Vercel, or Convika

Frequently asked questions

How do I deploy a v0 project?

Select Publish in the chat header. The first time, confirm the Vercel project name, choose who can open the app, and confirm the vercel.app domain or pick a custom one, then select Publish. v0 starts the production deployment and reports its progress on a deployment card. For later changes, open Publish and select Publish Changes.

Does v0 deploy to Vercel?

Yes. v0's docs say “v0 deploys projects to Vercel,” and the first publish creates a Vercel project for the chat. v0 accounts are Vercel accounts, and the app runs on the Vercel plan of the team it lives in.

Is deploying from v0 free?

Yes, on a Vercel Hobby team, which costs $0. Vercel's terms limit Hobby to “personal or non-commercial use,” and its limits include 200 projects and 100 deployments a day. A business site needs Vercel Pro, $20 a month. v0 Free comes with $5 in one-time credits for new users and a limit of 7 messages a day.

Do I need Vercel Pro to use v0?

No. v0's docs say “Vercel Pro does not provide any additional v0 features.” Vercel Pro adds team roles, higher limits, and commercial use of the hosting. The v0 plan and the Vercel plan are separate.

How do I deploy v0 to GitHub?

Open the Project menu ... → Settings → GitHub, select Connect, pick the account under Git Scope, name the repository, and select Create Repository. v0 pushes the code to a private repository. After that, Publish opens a pull request, merges it, and waits for the production deployment.

How do I add a custom domain to a v0 site?

Open Publish → Customize Domain, or Project menu ... → Settings → Domains, and select Add. Pick a free vercel.app domain, or enter your own and configure its DNS records in the Vercel dashboard. Hobby teams connect up to 50 custom domains per project.

Why did my v0 deployment fail?

v0 shows build errors and warnings on the deployment card. Select Fix with v0 or Fix Build, and v0 reads the logs and applies a fix. A GitHub publish can also stop on required checks, reviews, or merge conflicts, and a team's deployment policy can turn Publish off.

Can I deploy v0 to Netlify or another host?

Yes. v0's FAQ says “You can still export code and deploy elsewhere,” through GitHub sync. The new host has to build and run a Next.js app, with the environment variables v0 keeps in the Vercel project. v0's docs don't give steps for another host.

Can I publish a v0 page as one HTML file?

Yes, for a page with no backend. Rebuild it from its public vercel.app link with Convika's free rebuild tool, or ask an AI to rewrite its code as one HTML file and upload that. Convika hosts one static page and runs no server code, so an app with server actions, sign-ins, or a database stays on Vercel.

Sources

Each source was read on November 14, 2026 (JST). Dates in parentheses are the document's own.

• v0 docs: Deployments, Vercel Integration, GitHub, Custom domain, Pricing, FAQs (each last updated November 13, 2026)
• v0 pricing (no date on the page)
• Vercel: Hobby plan (last updated November 12, 2026), Adding a custom domain (last updated September 16, 2026), pricing (no date on the page), and the Terms of Service (last updated October 19, 2026)