This guide will help you use Snaplet to create and subsequently restore a safe, anonymized snapshot of your production data into your Neon database.


  • You'll need a Neon account, and an existing Neon project with a PostgreSQL database, and that database's connection string. If you haven't set this up yet, Neon has a tutorial (opens in a new tab) to guide you through the getting started process.
  • You'll need a Snaplet account, and you'll need to have connected to your existing production database and captured a snapshot of it. If you're new to Snaplet, you can follow our Getting Started guide.

Restoring your snapshot to Neon

Step 1: Have a snapshot ready

Ensure you have an active snapshot of your production database - it's easiest to check this from inside Snaplet Cloud. You can create a new snapshot if your previous snapshot has been deleted, or is out of date.

Snaplet snapshot ready to go

If you haven't previously created a snapshot at all, follow our Getting Started guide. Alternatively, you can follow along in the video guide below.

Step 2: CLI installation and setup

You'll need the Snaplet CLI to be installed and setup to restore your snapshot to Neon. If you haven't installed the Snaplet CLI, our Getting Started guide and our Configuration guide will take you through the process.

At the point where you're prompted to provide a target database URL, instead of using a local development database URL, provide your Neon database connection string: Snaplet CLI config - providing the Neon database string

The connection string to your Neon database can be found on your Neon database dashboard: Neon connection string

If you have installed and used the Snaplet CLI previously, jump ahead to step 4.

Step 3: Restore your Snapshot to Neon (new CLI users)

From within the Snaplet CLI, use the snaplet snapshot restore command to restore your production database snapshot to your Neon development database.

Because you're not restoring a snapshot to a local database, Snaplet will prompt you to confirm the overwrite, as this will result in your Neon database being overwritten with the schema and data from your snapshot. Press ‘Y' to confirm and proceed.

Confirmation when restoring your snapshot to Neon

Step 4: Change development database to your Neon database (existing CLI users)

If you've already installed the Snaplet CLI and configured Snaplet to restore snapshots to a different development database, you can change this easily by either editing the .snaplet/config.json file for your current working directory, or using the SNAPLET_TARGET_DATABASE_URL environment variable when running the snaplet snapshot restore command:

>_ terminal

SNAPLET_TARGET_DATABASE_URL='postgresql://username:password@hostname:5432/database_name' snaplet ss restore


We hope this guide has helped. If you experience any problems restoring your snapshots to your Neon database, come chat to us on Discord (opens in a new tab).