pg_restore: error: input file appears to be a text format dump. Please use psql.
A plain .sql dump was given to pg_restore, which only reads custom/directory/tar formats.
input file appears to be a text format dump Meaning
pg_dump default output is plain SQL — restore it with psql. Use pg_dump -Fc to create archives for pg_restore.
Common causes
- Plain SQL dump passed to pg_restore
- Backup tool/hosting panel exported plain SQL while the restore script expects -Fc archives
⚡ Quick fix
- psql -d dbname -f dump.sql
- Create archives with pg_dump -Fc next time
Detailed fix by platform
PostgreSQL
psql "$DATABASE_URL" -f dump.sql
How to diagnose
- Format — Plain text or custom archive?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in PostgreSQL
- prepared statement exists ERROR: prepared statement "s1" already exists (PgBouncer transaction mode)
- 23505 PostgreSQL: ERROR: duplicate key value violates unique constraint
- incompatible data directory FATAL: database files are incompatible with server — The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026