--- title: Deployments description: Deploy your v0 chats to Vercel with one click and manage production deployments. product: v0 type: guide prerequisites: - /docs/quickstart related: - /docs/custom-domains - /docs/vercel-integration - /docs/projects --- # Deployments Deploy your v0 chats to Vercel with just a few clicks. v0 integrates seamlessly with Vercel's platform to provide enterprise-grade hosting, automatic deployments, and global CDN distribution. ## Publishing to production To deploy your v0 chat to production: 1. **Open your chat** in v0 2. **Click "Publish"** in the chat interface, and then choose **Publish to Production** 3. **Wait for deployment** - v0 will automatically build and deploy your code to Vercel's platform 4. **Get your production URL** - Your app will be live at a unique Vercel URL The "Publish to Production" action creates a **Production deployment** of your application using Vercel's infrastructure. This deployment is optimized for performance and includes features like: * Global CDN distribution * Automatic HTTPS * Edge caching * Performance monitoring * Analytics integration ## Project and URL management ### One production URL per Project Each [project](/docs/projects) has **one production URL**. This means: * When you publish a chat for the first time, a new Vercel project is created with its own production URL * If you connect multiple chats to the same Vercel project, deploying from any of them updates the same production URL * The production URL remains consistent for your Vercel project across all deployments ### Managing multiple deployments If you want to maintain multiple versions of your application: * **Deploy to separate Vercel projects** for different versions or features * **Use our [GitHub integration](/docs/github)** to publish previews before going live * **Leverage Vercel's branching strategy** for development workflows For more information on managing deployments with Git, see the [GitHub documentation on branching](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) and [Vercel's preview deployments guide](https://vercel.com/docs/deployments/preview-deployments). ## Updating your deployment As you continue to iterate on your application: 1. **Make changes** to your code or chat with v0 2. **Open the Publish menu** in your chat 3. **Click "Publish Changes"** to update your production deployment 4. **Your app updates instantly** with zero downtime Each "Deploy Changes" action creates a new deployment that replaces the previous production version, ensuring your users always see the latest version of your application. ## Built with v0 badge Deployed apps can display a **"Built with v0"** badge in the bottom-right corner of the page. The badge links visitors back to v0 and the project that created the app. * **Toggle**: Go to **Project Menu** `...` → **Vercel Project** to turn the badge on or off. * **Default behavior**: The badge is shown by default for free-plan users. Paid users can disable it from the **Project Menu** `...` menu. * **Dismissable**: Visitors can close the badge on any individual page. ## Advanced deployment settings For fine-grained control over your deployment: 1. **Click "Inspect on Vercel"** from the **Publish** card 2. **Access the Vercel Dashboard** for your deployment 3. **Configure advanced settings** including: ### Environment variables * Set production environment variables * Configure API keys and secrets * Manage different environments (production, preview, development) ### Domain management * Add custom domains * Configure DNS settings * Set up domain redirects ### Web analytics and speed insights * Track page views and user interactions * Monitor Core Web Vitals and performance metrics ### Deployment protection * Enable password protection for your deployment * Restrict access to specific users or teams * Set up deployment previews for testing ### Monitoring and analytics * View deployment analytics * Monitor performance metrics * View error tracking For detailed information about Vercel project settings, see the [Vercel documentation on project configuration](https://vercel.com/docs/projects/project-configuration). ## Deployment policies Teams can configure **Deployment Policies** — a set of rules that control which Git sources and deployment mechanisms (Git, Vercel CLI, REST API, Deploy Hooks, Marketplace integrations) are allowed to create deployments for the team or a specific project. If your team has a deployment policy that restricts deployment sources, publishing from v0 may be blocked for the affected environments. A team Owner can adjust the policy at the team level, or override it for a specific project, to allow v0 deployments. To learn more, see the [Deployment Policy documentation on Vercel](https://vercel.com/docs/deployments/deployment-policy). ## Troubleshooting ### Common issues **Deployment fails:** * **Use Fix with v0** — When a deployment has errors or warnings, click the **Fix with v0** button in the deployment popover. v0 will diagnose the issue and apply a fix. You get up to 20 free uses per day on unedited code; after that, fixes cost credits like a normal prompt. See [Agentic Features — Fix with v0](/docs/agentic-features#fix-with-v0) for details. * **Go back one version** — If v0 can't fix it, revert to the previous working version. * **Re-prompt to avoid the error** — Adjust your prompt to generate code that won't cause deployment issues. **Deployment is blocked by your team:** * Check whether your team has a [deployment policy](#deployment-policies) restricting deployment sources for the environment you're publishing to. ## Next steps * [Learn about custom domains](/docs/custom-domains) * [Explore Vercel's advanced features](https://vercel.com/docs) * [Set up monitoring and analytics](https://vercel.com/docs/analytics) * [Configure environment variables](https://vercel.com/docs/environment-variables) --- For a semantic overview of all documentation, see [/docs/sitemap.md](/docs/sitemap.md) For an index of all available documentation, see [/docs/llms.txt](/docs/llms.txt) For agent-facing discovery, including API and MCP surfaces, see [/docs/agents.md](/docs/agents.md)