CSV To SQL Converter
Data To SQL And Back Again

What A CSV To SQL Converter Does For You

You often have data in a spreadsheet, and you need it in a database. Typing one INSERT line per row would take hours. So you need a tool that writes the SQL for you.

This tool does that in one box. First, paste your CSV, TSV or JSON. Then pick SQL as the target, and choose the table name and the database. The CREATE TABLE and INSERT statements appear as you type.

It also works the other way, and that direction is the one people need again a week later. Paste SQL with INSERT rows, and the tool reads them back as JSON, CSV, TSV, XML, YAML or an HTML table. So you can move data into a database and out of it.

Everything runs in your browser. So your data never leaves your device. That matters, because exports often hold customer names, emails and prices.

CSV To SQL, Step By Step

First, paste CSV with a header row. The tool reads the delimiter for you, so comma, semicolon, tab and pipe files all work. So each header becomes a column name.

Then it looks at the values in each column. A column of whole numbers becomes an integer. A column with decimals becomes a floating point number. Dates, true and false, and short or long text each get their own type.

Finally, it writes the statements. You get one CREATE TABLE with the columns and one INSERT line per row, or fewer lines if you batch the rows.

For more detail, see: Wikipedia article on SQL INSERT.

Pick Your Database

Databases differ in small ways, and those details break imports. So the tool writes the dialect you pick. MySQL uses backticks around names. PostgreSQL and SQLite use double quotes. SQL Server uses square brackets and an N before text.

Also, types change. A true or false column is BOOLEAN in PostgreSQL, TINYINT in MySQL and BIT in SQL Server. The tool picks the right one.

Then text gets a safe length, such as 50, 100 or 255. Very long text becomes TEXT. SQLite is relaxed about types, so there the tool uses plain INTEGER, REAL and TEXT.

SQL To JSON, CSV And More

First, paste a script with INSERT statements and pick another format. The tool reads every row, and it uses the column list or the CREATE TABLE to name the columns.

Also, if the script holds several tables, a list lets you pick one. NULL becomes null in JSON and an empty cell in CSV. Numbers and true or false keep their type.

Also, it reads multi row inserts, escaped quotes and N strings. It does not run anything, and it ignores statements that carry no rows.

JSON To SQL

A JSON list of flat objects works too. Then each key becomes a column, and the tool joins the keys of all objects. So a missing key becomes NULL.

So nested objects and lists turn into JSON text in one column. That keeps the table flat and loses nothing.

Quotes, NULL And Batches

The tool doubles every single quote in text, so a name such as O'Neil cannot break the statement. In MySQL it also doubles backslashes.

First, empty cells become NULL by default. Switch that off if you want empty strings. Also, numbers stay bare, and text stays in quotes.

Then you can write one INSERT per row, or group ten, a hundred or all rows in one statement. Grouped inserts load faster on big tables. So use them for large files.

Keep Zeros And Long Ids Safe

A ZIP code such as 02134 would lose its zero as a number. So the tool keeps a value with a leading zero as text. It also keeps very long ids as text, because a number type would round them.

Safe By Design

First, the tool reads SQL as text. It never connects to a database and never runs a statement. It also draws results as text, so a hostile file cannot run code in your page.