Is converting pg_dump to PGSQL 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 pg_dump data keep its types in PGSQL?

Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real PGSQL 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 pg_dump to PGSQL

Upload a .backup or .dump file and get back a PGSQL 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 PGSQL

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

Your data	PGSQL 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 pg_dump file

pg_dump has enough flags to change what its output even contains, and a few of them decide whether the file in front of you is convertible at all. These are the ones that matter here.

→pg_dump -Fc and a plain pg_dump > file.sql both work, and so does --inserts or --column-inserts, though neither is necessary: the default COPY output is read too.
→--schema-only gives you the tables with no rows in them. That is a valid conversion, and almost never the one that was wanted.
→--data-only is the opposite problem: rows arrive with no CREATE TABLE to name their columns, and the conversion says so rather than inventing names for them.
→Ownership and privilege statements are dropped while the archive is unpacked, so a dump taken as one role converts without that role having to exist anywhere.

Loading into an application's database

PGSQL is the name PostgreSQL wears inside application code: PHP's pgsql extension, Laravel's pgsql connection driver, the pdo_pgsql DSN prefix. If that is where you met the name, the database you are loading into probably belongs to a framework, which changes what to watch for.

→The script creates its own tables. Point it at a schema your migrations own and the next migration run and this file will disagree about who defines the table - load into an empty schema, or a database of its own, and point the application at that.
→Because every identifier is double-quoted, the case the source used is the case that gets stored. A column that arrives as "CustomerID" has to be quoted in your queries too: an unquoted CustomerID folds to customerid and is not found.
→No FOREIGN KEY, index or view statement is generated at all, so a framework that introspects the database finds unrelated tables. Declare the relations in your models, or add them with ALTER TABLE once the rows are in.

Reading pg_dump

→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 PGSQL

→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 pg_dump to PGSQL 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 pg_dump data keep its types in PGSQL?: Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real PGSQL 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.