How to Export Data from Supabase

Go to the Supabase Dashboard and navigate to Settings > Database. Scroll to the Connection string section and copy the URI. This connection string includes your host, port, database name, and password. You will use this string with pg_dump and psql. Make sure to use the direct connection string (port 5432), not the pooled connection (port 6543), because pg_dump requires a direct connection to read the full schema.

1# Your connection string looks like this:
2postgresql://postgres.[project-ref]:[password]@aws-0-[region].pooler.supabase.com:5432/postgres

pg_dump is the standard PostgreSQL tool for creating a complete database export. It outputs SQL statements that can recreate your tables, data, functions, triggers, and RLS policies. Run the command in your terminal, replacing the connection string with your own. The --clean flag adds DROP statements so the dump can be restored cleanly. The -F c flag creates a custom-format archive that supports selective restore with pg_restore.

1# Full database export as SQL file
2pg_dump "postgresql://postgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:5432/postgres" \
3  --clean \
4  --if-exists \
5  --schema=public \
6  -f export.sql
7
8# Custom-format archive (supports selective restore)
9pg_dump "postgresql://postgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:5432/postgres" \
10  --clean \
11  --if-exists \
12  -F c \
13  -f export.dump

For quick one-off exports, use the SQL Editor in the Supabase Dashboard. Navigate to SQL Editor in the left sidebar, write a SELECT query for the data you want to export, and click Run. After the results appear, click the Download button (arrow icon) above the results table to save the output as a CSV file. This method is ideal for exporting a single table or a filtered subset of data without needing any CLI tools.

1-- Export all rows from a specific table
2SELECT * FROM products;
3
4-- Export a filtered subset
5SELECT id, name, email, created_at
6FROM users
7WHERE created_at >= '2025-01-01'
8ORDER BY created_at DESC;
9
10-- Export with a join
11SELECT o.id, o.total, u.email
12FROM orders o
13JOIN users u ON o.user_id = u.id;

For automated or recurring exports, use the Supabase JavaScript client to fetch data and write it to a file. This approach respects RLS policies, so the authenticated user will only export data they have access to. If you need to export all data regardless of RLS, use the service role key on the server side only. Install the dependencies, create a script, and run it with Node.js.

1import { createClient } from '@supabase/supabase-js'
2import { writeFileSync } from 'fs'
3
4const supabase = createClient(
5  process.env.SUPABASE_URL,
6  process.env.SUPABASE_SERVICE_ROLE_KEY
7)
8
9async function exportTable(tableName) {
10  const allRows = []
11  let offset = 0
12  const pageSize = 1000
13
14  while (true) {
15    const { data, error } = await supabase
16      .from(tableName)
17      .select('*')
18      .range(offset, offset + pageSize - 1)
19
20    if (error) throw error
21    if (!data || data.length === 0) break
22
23    allRows.push(...data)
24    offset += pageSize
25  }
26
27  writeFileSync(
28    `${tableName}_export.json`,
29    JSON.stringify(allRows, null, 2)
30  )
31  console.log(`Exported ${allRows.length} rows from ${tableName}`)
32}
33
34await exportTable('products')

After exporting, always verify the data is complete. Compare the row count in your export file against the count in the database. For SQL exports, you can also try restoring to a local Supabase instance using supabase db reset or pg_restore to confirm the dump is valid. For CSV and JSON exports, open the file and spot-check a few records against the Dashboard table view.

1-- Check row count in Supabase SQL Editor
2SELECT count(*) FROM products;
3
4-- For pg_dump verification, restore to local instance
5supabase start
6psql "postgresql://postgres:postgres@localhost:54322/postgres" < export.sql
7
8-- Or with custom format
9pg_restore -d "postgresql://postgres:postgres@localhost:54322/postgres" export.dump