Is converting XLS 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 XLS 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 XLS to PGSQL

Upload a .xlsx or .xls 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 .xls file

A .xls file is BIFF8, the binary format Excel used through 2003. Its hard ceiling is 65,536 rows and 256 columns per sheet, which is the single most common reason a spreadsheet has to become a database: the data outgrew the file format, not the machine.

→The .xls path reads through pandas and xlrd, which does not expose cell number formats - so a column formatted as currency arrives as a floating-point number rather than a fixed-point decimal.
→The preview screen is where to correct that: retype the column to decimal before converting, or re-save the workbook as .xlsx, which does carry its formats through.
→If your file is near the 65,536-row limit, check whether it was already truncated when it was saved - the conversion moves what is in the file, and cannot recover rows Excel dropped.

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 XLS

→Numbers, dates and booleans are read as Excel stored them, never converted to text and re-parsed.
→Cell number formats are read out of .xlsx workbooks, so a column formatted as currency becomes a fixed-point decimal rather than a floating-point number — which is how money avoids acquiring a rounding tail. Legacy .xls is the exception: the xlrd path exposes no formats, so its currency columns come across as ordinary numbers.
→A column formatted as a date becomes a date, not a timestamp at midnight; one formatted with a time keeps its time.
→One sheet becomes one table. Empty sheets are skipped, and sheet names are sanitised for the target.

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 XLS 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 XLS 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.