When your PostgreSQL database is first initialized, a single production branch is created called `main` which acts as the default branch. You can then create development branches that you can use for development before shipping schema changes to production. Branches are completely isolated databases. Changes made in one branch, whether to the schema or the data, do not affect any other branches for a given database. There is no data replication between branches, so writing data into one will not replicate to another.

New branches incur additional charges. The cost depends on the selected resources for the branch. The monthly price for the new branch will be shown during branch creation. See [pricing](https://planetscale.com/docs/postgres/pricing) for more information.

## Development and production branches

PlanetScale Postgres provides two types of database branches:

- **Development branches** — Development branches run on `PS-DEV` instances that have limited performance capabilities, different egress rates, and no replicas. This is great for experimentation, testing new schemas, and limited exploration of your data.
- **Production branches** — Production branches are intended for production traffic and include optional replicas for high availability. Production branches can be created on non-HA ( [single node](https://planetscale.com/docs/postgres/cluster-configuration/single-node)) or HA (primary + 2 replicas) nodes.

## Create a branch

We are still in the process of building out our full branching functionality Postgres. You can currently create a new empty branch with no schema and no data or create a branch from a backup, which includes schema and data.

There are two ways to create a new Postgres branch: from the Branches page (no schema or data included) or by restoring from a backup (schema and data included). Each branch is its own isolated database and uses its own storage separate from production. You will be charged for the storage consumed by all production and development branches. We do not recommend using production data for development environments.

### From the Branches page

This method does not include schema or data. Branches created via this method will always initialize as a single node `PS-DEV` database, which does not have any replicas and begins at $5/month, depending on the region. After initialization, you have the option to upsize the branch or add replicas from the “Clusters” page in the dashboard.

1. Click **Branches**  
2. Click **New branch**  
3. Give the branch a name  
4. Choose the base branch. This currently does not copy the schema.  
5. Select a region  
6. Click **Create branch**

### From a backup

This method includes both the schema and the data for the selected backup. The cluster size, and therefore cost, is inherited from your main parent branch.

1. From the PlanetScale organization dashboard, select the desired database  
2. Navigate to the **Backups** page from the menu on the left  
3. Select the backup you wish to restore from  
4. Click **Restore to new branch**  
5. Configure the restored branch:  
   - **Branch name**: Name for the new branch  
   - **Cluster size**: Choose the desired size of the new cluster  
6. Click **Restore backup**

A new branch will be created based on this backup and will become visible under the **Branches** page.

## View all branches

To view all branches for your PostgreSQL database:

1. From the PlanetScale organization dashboard, select the desired database  
2. Click on the **Branches** drop down  
3. You’ll see a list of all branches with their type (development/production)  
4. You can select a branch by its name to see its **Dashboard**

## Connect to a branch

Each branch has its own connection details. To connect to a specific branch:

1. Navigate to the desired branch following either of the paths shown above  
2. Click the **Connect** button  
3. If you haven’t already, follow the instructions to **Create the default role**  
4. Choose your preferred connection method ( [direct or PgBouncer](https://planetscale.com/docs/postgres/connecting))  
5. Copy the connection string or credentials  
6. You should create new roles for specific use-cases and tailor their permissions appropriately for them  
7. In your application, use the specific role(s) and the preferred connection method.

For detailed connection instructions, see the [PostgreSQL connection documentation](https://planetscale.com/docs/postgres/connecting).

## Rename a branch

To rename a branch:

1. From the PlanetScale organization dashboard, select the desired database  
2. Navigate to the **Branches** page from the menu on the left  
3. Click on the three dots (”…”) next to the branch you want to rename  
4. Select **Rename branch**  
5. Enter the new branch name  
6. Click **Save changes**

Renaming a branch does not affect that branch’s credentials. You do not need to regenerate credentials if you rename a branch.

## Set as default branch

The default branch serves as the source branch when creating new development branches. To change the default branch:

### From the Branches page

1. From the PlanetScale organization dashboard, select the desired database  
2. Go to the **Branches** tab in your database dashboard  
3. Click on the three dots (”…”) next to the branch you want to set as default  
4. Click **Set as default branch**

### From the Settings page

1. From the PlanetScale organization dashboard, select the desired database  
2. Navigate to the **Settings** page from the menu on the left  
3. Select the branch from the **Default branch** dropdown you want to be the default branch  
4. Scroll down and click **Save database settings**

If you change the default branch and intend for it to power your production application, you may need to update your application credentials to reference the new default branch.

## Delete a branch

You can delete a branch that you no longer need:

1. From the PlanetScale organization dashboard, select the desired database  
2. Go to the **Branches** tab in your database dashboard  
3. Click on the three dots (”…”) next to the branch you want to delete  
4. Select **Delete**  
5. Confirm the deletion

**Important notes:**
- You cannot delete the default branch. You must first set another branch as the default branch.
- You cannot set development branches as the default branch.
- Only [Organization Administrators and Database Administrators](https://planetscale.com/docs/security/access-control) have permission to delete production branches. Database Members can delete non-production branches.
- Development branches are billed only for the time they are used, so it’s beneficial to delete them when no longer needed.

## Schema changes

Since PlanetScale Postgres branches don’t use [deploy requests like in Vitess](https://planetscale.com/docs/vitess/schema-changes/deploy-requests), you make schema changes directly on each branch:

1. Connect to your development branch
2. Make your schema changes using standard PostgreSQL DDL commands
3. Test your changes in the development environment
4. When ready, manually apply the same changes to your production branch

There’s currently no automated way to merge schema changes between PlanetScale Postgres branches. You must manually copy your changes from development to production branches.

## Need help?

Get help from [the PlanetScale Support team](https://planetscale.com/contact?initial=support), or join our [Discord community](https://pscale.link/community) to see how others are using PlanetScale.