Manage domains for branch deploys
By default, branch deploys use the Netlify subdomain netlify.app with your branch name but you can customize your branch deploy URL with an automatic deploy subdomain.
# Default URL for branch deploys
By default branch deploys use the Netlify subdomain netlify.app with the branch name, such as https://staging.netlify.app where staging is your branch name.
# Custom branch subdomains for branch deploys
This feature is available in our UI with Netlify DNS.
Netlify can generate a branch subdomain for specified branch deploys using your site’s primary custom domain designated for your production site.
The resulting branch subdomains use the fixed syntax branchname.yourcustomdomain.com and can’t use a different pattern. For example, if your custom domain is example.com and your branch is staging, you can check the latest deploy of that branch at staging.example.com.
Before you can enable branch subdomains, you must enable branch deploys for your branch and successfully deploy your branch.
To add a new branch subdomain, go to
, and select New subdomain.
A branch subdomain can be deleted by using the x button in the corresponding subdomain row.
Visit our Forums for a verified Support Guide on setting up branch subdomains without Netlify DNS.
# Compare subdomain options for branch deploys
For an overview of the main differences between these subdomains, consider these key differences.
| Automatic deploy subdomains | Branch subdomains | |
|---|---|---|
| Custom domain options | Can use your production site’s primary domain or any other custom domain or subdomain managed by Netlify DNS and available to your team. | Can only use your production site’s primary domain, which must be managed by Netlify DNS. |
| Additional subdomain support | X | |
| Requires Netlify DNS | X | X |
| Pricing plan | Core Pro plan and above | All plans |
| Branch deploy scope | Applies to all branch deploys. | Applies to user-specified branch deploys: individual branches or all branches except the designated production branch. |
| Setup interactions | Once set up, becomes the primary deploy URL for branch deploys. Cannot change existing branch subdomain settings without removing your automatic deploy subdomain. | Once automatic deploy subdomains are set up, cannot change existing branch subdomain settings but branch subdomain URLs still resolve for pre-existing branches. |
# Set up both a branch subdomain and an automatic deploy subdomain
If you want to use both branch subdomains and an automatic deploy subdomain for branch deploys, ensure that you set up any branch subdomains before your automatic deploy subdomain.
We recommend setting up only stable or internal branch subdomains since you would need to remove your automatic deploy subdomain to make changes to your branch subdomain settings.
Also, note that the Netlify UI, CLI, and API will use the automatic deploy subdomain for branch deploys configured with a branch subdomain. The branch deploy URL featuring your branch subdomain, such as staging.company.com should still resolve and work for site visitors though.
Learn more about limitations to using both types of subdomains for branch deploys.
Did you find this doc useful?
Your feedback helps us improve our docs.