---
title: Using Non-default Branches for Production Deployments
description: Learn how to set a non-default branch as Production on your Vercel project.
url: /kb/guide/can-i-use-a-non-default-branch-for-production
canonical_url: "https://vercel.com/kb/guide/can-i-use-a-non-default-branch-for-production"
last_updated: 2025-11-10
authors: Allen Hai
related:
  - /docs/git
  - /docs/platform/projects
  - /docs/concepts/projects/overview
  - /docs/platform/deployments
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

Different organizations have different workflow requirements. Sometimes, that might entail going to [production with a branch](https://vercel.com/docs/git#production-branch) that isn't set as the default. Read on to learn about how Vercel supports this use case.

## Production Branch Project Setting

In the **Environments** [menu item](https://vercel.com/docs/platform/projects#git) of your [project's](https://vercel.com/docs/concepts/projects/overview#project-settings) settings page, you'll find a [fieldset](https://vercel.com/design/fieldset) that allows you to select which branch you'd like to associate with production. You can choose between the `main` branch, your repository's default branch, or any other custom branch in your repository.

Once you've entered the new branch you want to use as your [Production Branch](https://vercel.com/docs/git#production-branch), click "Save". All future pushes made to that branch will be [Production Deployments](https://vercel.com/docs/platform/deployments#production).