CSV to SQL Converter

How to use it

1. Add your CSVOpen a .csv, .tsv or text file. The separator is detected, and you can change it.
2. Choose your databasePick MySQL, PostgreSQL, SQLite or SQL Server, then set the table name and the options.
3. Copy or downloadCopy the SQL, or save it as a .sql file.

Good to know

Text is escaped for the database you pick: quotes everywhere, backslashes in MySQL, and N'...' for text with accents or other non-ASCII letters in SQL Server. A column is written as numbers only when every value in it is a plain number, so zip codes like 01234 and long ids stay text, and one stray value such as N/A makes the whole column text. Empty cells become NULL. This tool writes INSERT statements only, so create the table first, and try the script on a copy of your database before you run it on the real one.

Worked example: one CSV, two databases

This is the CSV we used in our tests. It has the awkward things real files have: a zip code with a leading zero, a 20-digit id, a price with a trailing zero, a quote mark, a backslash and an empty cell.

people.csv

id,name,zip,note,amount
1,Ana O'Neil,01234,C:\temp\new,12.50
2,Zoë Müller,90210,,3
12345678901234567890,Sam Lee,007,"say ""hi""",-4.5

MySQL output (table name: people)

INSERT INTO `people` (`id`, `name`, `zip`, `note`, `amount`) VALUES
  ('1', 'Ana O''Neil', '01234', 'C:\\temp\\new', 12.50),
  ('2', 'Zoë Müller', '90210', NULL, 3),
  ('12345678901234567890', 'Sam Lee', '007', 'say "hi"', -4.5);

SQL Server output

INSERT INTO [people] ([id], [name], [zip], [note], [amount]) VALUES
  ('1', 'Ana O''Neil', '01234', 'C:\temp\new', 12.50),
  ('2', N'Zoë Müller', '90210', NULL, 3),
  ('12345678901234567890', 'Sam Lee', '007', 'say "hi"', -4.5);

What to notice:

• 01234 and 007 stay text in quotes. A column is written as numbers only when every value in it is a plain number, so the zip column is safe.
• The 20-digit id is also kept as text. A number that long would lose its last digits in most databases and in JavaScript.
• 12.50 stays 12.50, and -4.5 is written as a number because every value in the amount column is a plain number.
• The empty cell becomes NULL, and the apostrophe in O'Neil is doubled, which every database accepts.
• MySQL doubles the backslash (C:\\temp\\new) because MySQL reads \t and \n as escapes; SQL Server and PostgreSQL leave it alone.
• SQL Server puts N in front of text with accents (N'Zoë Müller') so the characters are not lost in a non-Unicode column. MySQL does not need this.

What changes between the four databases

Standard SQL / other writes double-quoted names and no special prefixes. The statements create no table, so create the table first with column types that suit your data, and try the script on a copy of your database. Going the other way, the SQL to CSV tool turns INSERT statements back into a CSV. If your data starts in Excel, use XLSX to CSV first.

How we tested this

On 31 October 2026 we ran the live page in headless Chromium on a Linux cloud server, driving it the way a person would (adding files, clicking the buttons, saving the download) and checking the files it produced.

Not tested: MySQL, PostgreSQL and SQL Server themselves. The MySQL and SQL Server text follows each database's documented escaping rules, and the PostgreSQL-style output was loaded into SQLite, which reads the same syntax, not into PostgreSQL.

Where to go next

• To go the other way, read INSERT statements back into a CSV.
• Your data is in Excel? Convert the sheet to CSV first.
• Remove duplicate rows before loading, so the table does not get them twice.

When people use it

• You have a CSV and need INSERT statements to load it into a database.
• You want to try the same data on MySQL and on PostgreSQL and see how the statements differ.
• A teammate sent a spreadsheet and you want it as a quick test table.