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

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

Upload a .xlsx or .xls file and get back a PostgreSQL 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 PostgreSQL

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

Your data	PostgreSQL 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 an Excel file

"Excel" covers two entirely different file formats, and which one you have decides how much type information survives the conversion. It is worth checking what your workbook was actually saved as before you upload it.

→Only .xls and .xlsx are recognised. A macro-enabled .xlsm, or a workbook saved as OpenDocument .ods, is refused before anything is read - save a copy as .xlsx first.
→The two extensions take different code paths inside the reader: .xlsx through openpyxl, .xls through pandas and xlrd, and they do not recover the same amount of information from the file.
→Sheet names become table names with every character outside letters, digits and underscores replaced one for one, so "Q1 Sales (2024)" arrives as Q1_Sales__2024: the space and the opening bracket each leave an underscore behind, and the trailing one is trimmed.

What the PostgreSQL script contains

The conversion produces one dump.sql with a README beside it, zipped. It is a script you can open, grep and edit before you run it rather than an archive a tool has to unpack, and it is deliberately sparing in what it declares.

→Every string column is declared TEXT, whatever length the source declared for it. PostgreSQL stores a short value in a TEXT column exactly as cheaply as in a VARCHAR, and an unbounded column cannot reject a row on load for being a few characters too long.
→Identifiers are all double-quoted, and even so a name on PostgreSQL's reserved list is given a trailing underscore: a column called user arrives as user_, order as order_, limit as limit_.
→A decimal column whose source declared no scale is given six decimal places rather than none, keeping whatever precision it did declare: NUMERIC(10,6) from a source that said 10, and NUMERIC(18,6) from one that declared neither. A scale of zero would have the server round 19.99 to 20 as it loaded.

Reading Excel

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

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