Convert TSV to Postgres
Upload a .csv or .tsv file and get back a Postgres SQL script you can load straight into your database. Types are preserved rather than flattened to text. Free, no registration, up to 10MB.
Click to upload or drag and drop
CSV, Excel, SQLite, SQL, DBF (max 10 MB)
How your data is typed in Postgres
Generated from the converter's own Postgres type mapping — this is what it actually emits, not an example.
| Your data | Postgres 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 .tsv file
Tab-separated files come out of database shells, BI exports and anything that had to avoid commas inside its own values. They go through the same reader as CSV - the tab simply wins the separator sniff - so there is nothing to configure.
- →The extension is what routes an upload, and only .csv and .tsv reach this reader. A tab-separated file saved as .txt or .tab is not recognised, so rename it before uploading.
- →Because the separator is detected from the content and not the extension, a file named .csv that is really tab-separated is still read correctly.
- →Quoting rules still apply: a double quote opening a field is treated as a quote character, which is worth knowing for exports that never intended to quote anything.
The oldest PostgreSQL this loads into
Postgres is the informal spelling and the one most people type. Since the name says nothing about a version, the useful question for this page is which server releases the generated script runs on, and that is decided by the newest piece of syntax in it.
- →The identity clause on auto-increment columns is the newest thing in the file, and it arrived in release 10. That is the floor for loading the script unedited.
- →Everything else is far older: the hex escape the script uses for binary values has been accepted since 9.0, and jsonb, which is what a JSON column is declared as, since 9.4.
- →On a server below the floor the script still loads if you delete the identity clauses by hand. The columns keep every value they were given, because each INSERT names them explicitly; they simply stop assigning new ones.
Reading TSV
- →Leading zeros are preserved. A column containing 01234 is kept as text, never turned into the number 1234.
- →A row with more fields than the header, usually an unquoted comma inside a value such as Acme, Inc., is left out and reported by line number instead of sliding every later value one column right. A trailing comma on every line adds no column.
- →An empty cell becomes NULL, not an empty string — the two mean different things once the data is in a database.
- →Amounts in accounting style, 1,250.00 with a thousands separator or (84.30) for a negative, become exact decimals when the column also has a decimal point; a lone 1,250 stays text because in much of Europe it means 1.25.
- →A file that is not UTF-8 is read as Windows-1252, unless the text reads as Russian in Windows-1251 or DOS 866, which are checked as well; the warning names the code page chosen.
- →Dates are only treated as dates when the format is unambiguous. 03/04/2025 could be March 4th or April 3rd, so it stays text unless another value in the column settles it.
Writing Postgres
- →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.
- →All-uppercase names from dBase, FoxPro or Oracle, such as CUSTNO, are written in lower case, so queries need no double quotes. Mixed-case names such as OrderID keep their spelling.
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 TSV to Postgres 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 TSV data keep its types in Postgres?
- Yes — that is the point. Whole numbers, decimals, dates and booleans are mapped to real Postgres 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.