---
title: Why do my Vercel deployments have multiple domains?
description: Learn about why Vercel auto generates URLs for your deployments.
url: /kb/guide/why-do-my-vercel-deployments-have-multiple-domains
canonical_url: "https://vercel.com/kb/guide/why-do-my-vercel-deployments-have-multiple-domains"
published: 2025-11-03
last_updated: 2025-11-10
authors: Allen Hai
related:
  - /docs/git
  - /docs/concepts/projects/overview
  - /docs/platform/deployments
  - /docs/concepts/git
  - /docs/custom-domains
  - /docs/concepts/deployments/environments
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---
<!-- docsgraph:related -->
## Related pages

> **For AI agents:** Follow these links to understand how this page connects to the rest of the Vercel ecosystem. For the full cross-link map (inbound, outbound, prerequisites, and semantic neighbors), see the .graph.md link below.

- [Generated URLs](https://vercel.com/docs/deployments/generated-urls?from=related) — When you create a new deployment, Vercel will automatically generate a unique URL which you can use to access that parti
- [Preview Deployment Suffix](https://vercel.com/docs/deployments/preview-deployment-suffix?from=related) — When you create a new deployment, Vercel will automatically generate a unique URL which you can use to access that parti
- [Deploying & Redirecting Domains](https://vercel.com/docs/domains/working-with-domains/deploying-and-redirecting?from=related) — Learn how to deploy your domains and set up domain redirects with this guide.
- [Deploy from CLI](https://vercel.com/docs/projects/deploy-from-cli?from=related) — Set up and deploy a Vercel project using the CLI, from linking to production.
- [Working with Domains](https://vercel.com/docs/domains/working-with-domains?from=related) — Learn how domains work and the options Vercel provides for managing them.
- [How do I add a custom domain to my Vercel project?](https://vercel.com/kb/guide/how-do-i-add-a-custom-domain-to-my-vercel-project?from=related) — Learn how to add a custom domain to your Vercel project.
- [How do I set up a staging environment on Vercel?](https://vercel.com/kb/guide/set-up-a-staging-environment-on-vercel?from=related) — Information on how to set up a staging environment on Vercel.

Full cross-link map for this page: [/kb/guide/why-do-my-vercel-deployments-have-multiple-domains.graph.md](/kb/guide/why-do-my-vercel-deployments-have-multiple-domains.graph.md)
<!-- /docsgraph:related -->


When taking a look at the deployment overview page or a [Git](https://vercel.com/docs/git#) commit comment, you might have noticed several domains listed and associated with your deployment that you've never configured. Read on to learn about why they exist.

## Preview Links

[Vercel](https://vercel.com/) wants to make it as easy as possible for teams to collaborate on [Vercel Projects](https://vercel.com/docs/concepts/projects/overview). A part of that entails sharing [preview URLs](https://vercel.com/docs/platform/deployments#preview) at different stages of the project. By default, Vercel creates a preview link that contains the name of the project, the account or team name, and the final suffix. A full URL might look like: `project-acme.vercel.app`.

For different [Git branches](https://vercel.com/docs/concepts/git), you'll have a preview URL generated for each of them that includes the project name along with the Git branch and might look like: `project-git-new-feature.vercel.app`.

These domains are generated by default and cannot be turned off. However, changes will likely be made in the future to streamline this experience further.

## Custom Production Domains

Alongside the preview domains that are created by default, you're able to add your own [custom domains](https://vercel.com/docs/custom-domains) for your [Production](https://vercel.com/docs/concepts/deployments/environments#production) and [Preview](https://vercel.com/docs/concepts/deployments/environments#preview) environments. Each additional domain that you configure will also be rendered in the dashboard and Git comments, with your production domain(s) shown where a Production Deployment has been made.