Question 1

How does this tool decide each column's SQL data type?

Accepted Answer

It inspects every value in a column and checks, in order, whether they all look like integers, all look like decimals, are all "true"/"false", are all ISO dates (YYYY-MM-DD, optionally with a time), or none of the above — in which case it falls back to text. A value like "007" is kept as text rather than integer, since leading zeros usually mean it's an identifier (like a postal code), not a number.

Question 2

What happens to empty cells?

Accepted Answer

Any empty cell becomes SQL NULL in the generated statement, regardless of what type the rest of the column was inferred as.

Question 3

What's the difference between batch and per-row INSERT mode?

Accepted Answer

Batch mode produces a single INSERT INTO ... VALUES statement with one row per line, which is faster to run and easier to paste. Per-row mode produces a separate INSERT statement for every row, which is easier to review, edit, or partially re-run if one row fails.

Question 4

Which SQL dialects are supported, and what actually changes between them?

Accepted Answer

MySQL, PostgreSQL, SQLite, and generic ANSI SQL. The dialect controls how identifiers are quoted (backticks for MySQL, double quotes for the others), how boolean values are written (1/0 for MySQL and SQLite, TRUE/FALSE for PostgreSQL and ANSI), and the column types used in the optional CREATE TABLE statement.

Question 5

Can it also generate the CREATE TABLE statement?

Accepted Answer

Yes — toggle "Include CREATE TABLE" to prepend a CREATE TABLE statement built from the same inferred column types, so you can create the table and load your data in one paste.

Question 6

Is my CSV data uploaded anywhere?

Accepted Answer

No. Parsing and SQL generation both run entirely in your browser using the PapaParse library — your data never leaves your device.

Question 7

How are quotes and special characters inside my data handled?

Accepted Answer

Single quotes inside text or date values are automatically doubled (the standard SQL escape) so they don't break the statement, e.g. O'Brien becomes O''Brien. Commas and newlines inside a CSV field are handled correctly as long as that field is wrapped in double quotes in the source CSV.

CSV to SQL INSERT Statement Generator

Result

How This Tool Works

Frequently Asked Questions

How does this tool decide each column's SQL data type?

What happens to empty cells?

What's the difference between batch and per-row INSERT mode?

Which SQL dialects are supported, and what actually changes between them?

Can it also generate the CREATE TABLE statement?

Is my CSV data uploaded anywhere?

How are quotes and special characters inside my data handled?

Related Tools

CSV to JSON Converter

XLSX to CSV Converter

JSON to YAML Converter