# Backups with pg_dump

This topic describes how to create a backup of your Neon database using the Postgres `pg_dump` utility and how to restore a backup using `pg_restore`.

The same **`pg_dump`** flow applies when you **export** data for a **region migration** or a **Postgres-compatible export from Neon**. For path selection (another Neon region, Lakebase, or export), see **[Region migration](/guides/neon-docs-import-region-migration)**.

:::callout{intent="note"}
Avoid using `pg_dump` over a [pooled connection string](/guides/postgres-reference-glossary#pooled-connection-string). Use an [unpooled connection string](/guides/postgres-reference-glossary#unpooled-connection-string) instead.
:::

## Prerequisites

- Make sure `pg_dump` and `pg_restore` are installed. You can verify by running `pg_dump -V`.
- We recommend using the latest versions of `pg_dump` and `pg_restore`, and ensuring that the client version matches your Neon project's Postgres version.

## Install`pg_dump`and`pg_restore`

If you don't have the `pg_dump` and `pg_restore` utilities installed locally, you'll need to install them on your preferred platform.

1. Install PostgreSQL using the official installer from https://www.postgresql.org/download/windows/.
2. `pg_dump` and `pg_restore` are installed by default and can be found in the PostgreSQL `bin` directory.

## Creating a backup with`pg_dump`

Following this procedure will create a database backup locally, where you're running the `pg_dump` command.

1. Retrieve the connection string for your Neon database by clicking **Connect** in the Console nav to open the **Connect to your branch** modal.

2. Deselect the **Connection pooling** option. You need a direct connection string, not a pooled one.

   Your connection string should look something like this:

   ```bash
   postgresql://alex:AbC123dEf@ep-cool-darkness-123456.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require
   ```

3. Create a backup of your Neon database by running the following `pg_dump` command with your Neon database connection string.

   ```bash
   pg_dump -Fc -v -d "<neon_database_connection_string>" -f <dump_file_name>
   ```

   After adding your Neon database connection string and a dump file name, your command will look something like this:

   ```bash
   pg_dump -Fc -v -d "postgresql://alex:AbC123dEf@ep-cool-darkness-123456.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require" -f mydatabase.bak
   ```

   The `pg_dump` command above includes these arguments:

   - `-Fc`: Sends the output to a custom-format archive suitable for input into `pg_restore`.
   - `-v`: Runs `pg_dump` in verbose mode, allowing you to monitor what happens during the dump operation.
   - `-d`: Specifies the [connection string](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING) for your Neon database.
   - `-f <dump_file_name>`: The dump file name. It can be any name you choose (`mydumpfile.bak`, for example).

   For more command options, see [Advanced pg\_dump and pg\_restore options](/guides/neon-docs-import-migrate-from-postgres#advanced-pgdump-and-pgrestore-options).

For most accidental-delete recoveries you don't need a local file. Neon keeps a change history that supports [instant restore](/guides/postgres-backup-restore-branch-restore) (point-in-time restore) within your project's [history window](/guides/postgres-backup-restore-history-window), which is usually faster. Reach for a local `pg_dump` backup when you need off-platform redundancy, archival beyond your history window, an external copy for compliance, or a copy to move into a different Postgres instance.

## Restoring a backup with`pg_restore`

This procedure shows how to restore a database using the `pg_restore` utility from a backup file created using `pg_dump`, as described above.

1. Create a new Neon project.

2. Create a database with the same name as the one you backed up. The `pg_dump` instructions above created a backup of a database named `neondb`. Your database name is likely different.

3. Retrieve the connection string for your Neon database:

   Go to your Neon project and click the **Connect** button to open the **Connect to your branch** modal.

   Deselect the **Connection pooling** option. You need a direct connection string, not a pooled one.

   Your connection string should look something like this:

   ```bash
   postgresql://alex:AbC123dEf@ep-dry-morning-a8vn5za2.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require
   ```

4. Restore your data to the target database in Neon with `pg_restore`.

   ```bash
   pg_restore -v -d "<neon_database_connection_string>" <dump_file_name>
   ```

   After adding your Neon database connection string and the dump file name, your command will look something like this:

   ```bash
   pg_restore -v -d "postgresql://alex:AbC123dEf@ep-dry-morning-a8vn5za2.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require" mydatabase.bak
   ```

   The example above includes these arguments:

   - `-v`: Runs `pg_restore` in verbose mode, allowing you to monitor what happens during the restore operation.
   - `-d`: Specifies the Neon database to connect to. The value is a Neon database connection string. See [Prerequisites](#prerequisites).
   - `<dump_file_name>` is the name of the dump file you created with `pg_dump`.

   For more command options, see [Advanced pg\_dump and pg\_restore options](/guides/neon-docs-import-migrate-from-postgres#advanced-pgdump-and-pgrestore-options).

## `pg_dump`and`pg_restore`example

The following example shows how data is dumped from source database named `neondb` in one Neon project and restored to a `neondb` database in another Neon project using the commands described in the previous sections. (A database named `neondb` was created in the Neon project prior to running the restore operation.)

Before performing this procedure:

- A new Neon project was created for the destination database, and a database with the same name as the source database was created (`neondb`)

- Connection strings for the source and destination databases were collected:

  - source: `postgresql://alex:AbC123dEf@ep-cool-darkness-123456.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require`
  - destination: `postgresql://alex:AbC123dEf@ep-dry-morning-a8vn5za2.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require`

```bash
~$ cd mydump
~/mydump$ pg_dump -Fc -v -d "postgresql://alex:AbC123dEf@ep-cool-darkness-123456.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require" -f mydatabase.bak

~/mydump$ ls
mydatabase.bak

~/mydump$ pg_restore -v -d "postgresql://alex:AbC123dEf@ep-dry-morning-a8vn5za2.us-east-2.aws.neon.tech/neondb?sslmode=require&channel_binding=require" mydatabase.bak
```

## Related pages

- [Backups](./postgres-backup-restore-backups.md)
- [Instant restore](./postgres-backup-restore-branch-restore.md)
- [Time Travel](./postgres-backup-restore-time-travel-assist.md)
- [History window](./postgres-backup-restore-history-window.md)
- [Automate pg_dump backups](./postgres-manage-backup-pg-dump-automate.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.