Adding & Configuring a Custom Domain
Vercel provides all deployments with a vercel.app URL, which enables you to share Deployments with your Team for collaboration. However, to provide greater personalization and flexibility to your project, you can instead add a custom domain. If you don't own a domain yet, you can purchase it with Vercel.
You can manage all domain settings related to a project from Settings and then Domains in the sidebar, regardless of whether you are using apex domains or subdomains in your project. This document will guide you through both options.
Hobby teams have a limit of 50 custom domains per project.
The following steps provide an overview of how to add and configure a custom domain in Vercel:
On the dashboard, pick the project to which you would like to assign your domain.
Once you have selected your project, open Settings in the sidebar and then select Domains.
From the Domains page, click the Add Domain button:


The button to click on the domains page. Input the domain you wish to include in the project:


Text input on the add domain page to input your domain name in. If you add an apex domain (e.g.
example.com) to the project, Vercel will prompt you to add thewwwsubdomain prefix. For more information about why we recommend using awwwdomain, see "Redirectingwwwdomains".You can also use your custom domain as a wildcard domain by prefixing it with
*..To add a wildcard domain, use the prefix
*, for example*.acme.com.

A wildcard domain being deployed. Once you have added your custom domain, you will need to configure the DNS records of your domain with your registrar so it can be used with your Project. The dashboard will automatically display different methods for configuring it:
- If the domain is in use by another Vercel account, you will need to verify access to the domain, with a TXT record
- If you're using an Apex domain (e.g. example.com), you will need to configure it with an A record
- If you're using a Subdomain (e.g. docs.example.com), you will need to configure it with a CNAME record
Both apex domains and subdomains can also be configured using the Nameservers method.
You can configure apex domains with an A record.


DNS configuration for an apex domain. You can configure subdomains with a CNAME record. Each project has a unique CNAME record e.g.
d1d4fc829fe7bc7c.vercel-dns-017.com.

DNS configuration for a subdomain. If you choose to use a wildcard domain Vercel's nameservers will be automatically enabled for you on saving the domain settings. You will then be provided with the Vercel nameservers to copy and use with your registrar.


DNS configuration for Vercel nameservers. If the domain is in use by another Vercel account, you may be prompted to verify access to the domain. Note that this will not move the domain into your account, but will allow you to use it in your project. If you have multiple domains to verify, be aware that you can only set up one TXT record at a time, but you can modify it after the domain is transferred.


Verify domain access.
Once the domain has been configured and Vercel has verified it, the status of the domain will be updated within the UI to confirm that it is ready for use.


If the domain does not show a valid configuration, compare the records at your authoritative DNS provider with the values shown in the project's Domains settings.
| Symptom | What to check |
|---|---|
| The domain has an invalid configuration | Check for conflicting A, AAAA, or CNAME records for the same hostname. Use the values shown for your project rather than copying another project's records. |
| A subdomain does not resolve | For www.example.com, use www as the record name in Vercel's DNS form. Other DNS providers may use a different name format. |
The apex domain works but www does not, or the reverse | Add both domains to the project and configure a redirect to your preferred domain. |
| Email stopped arriving after a nameserver change | Restore your email provider's records using the email troubleshooting steps. |
DNS changes can take time to propagate. Use DNS verification to compare the published records, and see domain troubleshooting for configuration and certificate errors.
Was this helpful?