Is converting pgAdmin backup to psql free?

Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.

Will my pgAdmin backup data keep its types in psql?

Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real psql types rather than everything becoming text. The mapping table above shows exactly what you get.

Do you store my file?

No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.

Convert pgAdmin backup to psql

Upload a .backup or .dump file and get back a psql SQL script you can load straight into your database. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.

1Upload your file

Click to upload or drag and drop

CSV, Excel, SQLite, SQL, DBF (max 10 MB)

2Choose target format

How your data is typed in psql

Generated from the converter's own psql type mapping — this is what it actually emits, not an example.

Your data	psql type
Whole number	BIGINT
Decimal (money)	NUMERIC(10,2)
Floating point	DOUBLE PRECISION
True / false	BOOLEAN
Date	DATE
Date and time	TIMESTAMP
Short text	TEXT
Long text	TEXT
Binary data	BYTEA

Working from a pgAdmin backup

pgAdmin's Backup dialog is a front end to pg_dump, so what you end up with depends on which format you picked in it - and the default is not plain SQL, which surprises people expecting a file they can read.

→In pgAdmin's server and container modes the backup is written on the machine running pgAdmin rather than on yours, under that installation's storage directory for your login. Fetch it with pgAdmin's own file manager before you can upload it anywhere.
→If the dialog refused to produce a file at all and complained that a utility was not found, that is its Binary Path preference pointing at no pg_dump. It is a pgAdmin setting, not a problem with your database.
→The dialog's "Do not save Owner" and "Do not save Privileges" toggles make no difference to the result: those statements are stripped when the archive is unpacked, whichever way you set them.

Running the script through psql

psql is PostgreSQL's command-line client rather than the database itself, and the script is written to be fed straight into it. Everything here is about the tool you run, not about the server you run it against.

→From inside a session already open, \i dump.sql runs the file without leaving the prompt. The script contains no backslash meta-commands of its own, so nothing in it can collide with yours.
→There is no BEGIN and no COMMIT anywhere in the file. Statements commit as they go, so a failure halfway leaves the tables already created: pass -1 to wrap the whole load in a single transaction, or -v ON_ERROR_STOP=1 to stop at the first error instead of carrying on past it.
→The script switches standard_conforming_strings on itself instead of trusting the server default, so it behaves identically against a session that has been moved off it.
→It sets client_encoding to UTF8 for the same reason. The file is written as UTF-8 with nothing to announce that, and psql would otherwise decode it using whatever the client locale says.

Reading pgAdmin backup

→Reads pg_dump custom-format archives (.backup, .dump) — pgAdmin's default backup option — as well as plain SQL dumps.
→Data written as COPY blocks is read, not just INSERT statements. COPY is pg_dump's default, so a reader that only understands INSERT returns your tables with none of their rows.
→Primary keys declared by a later ALTER TABLE, which is how pg_dump writes them, are preserved.

Writing psql

→Backslashes are left alone, because PostgreSQL treats them as ordinary characters — doubling them would corrupt every Windows path.
→Auto-increment columns become GENERATED BY DEFAULT AS IDENTITY.
→Binary data is written as bytea, and identifiers respect the 63-character limit.

What you get

A ZIP containing dump.sql, plus a README with the exact command to load it. If anything about your data needed a judgement call, a _warnings.txt explains it.

Load this dump into PostgreSQL:

  psql -U USER -d DATABASE -f dump.sql

Create the database first if it does not exist:

  createdb -U USER DATABASE

Questions

Is converting pgAdmin backup to psql free?: Yes. Files up to 10MB convert free with no account. There is a limit of five conversions per day per IP address.
Will my pgAdmin backup data keep its types in psql?: Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real psql types rather than everything becoming text. The mapping table above shows exactly what you get.
Do you store my file?: No. The file is written to a temporary directory, converted, and the directory is deleted as soon as your download has been sent.