Convert CSV to SQL INSERT statements

How to convert CSV to SQL

1. Open a .csv, .tsv or .txt file, drop it on the tool, or paste rows. The delimiter is detected; set it, the header row or a legacy encoding such as Windows-1252 under Import settings.
2. Choose the Database: PostgreSQL, MySQL / MariaDB, SQLite or SQL Server. Check the Table name, which starts as the file name with spaces and punctuation turned into underscores (sales report.csv becomes sales_report).
3. Choose the Statement and, for UPSERT, UPDATE or DELETE, tick the Key columns that identify a row.
4. Review the preview, then select Copy or download the .sql file and run it with your database client, for example psql -f data.sql.

To script many files with the same settings, choose Batch: convert several files. Each file is converted in turn and the scripts download together as one ZIP.

Statements and options

Column types and quoting

With Keep every value as text (the default) every column is TEXT (NVARCHAR(MAX) in SQL Server) and every value is a quoted string literal, so leading zeros, long IDs and odd dates load unchanged.

With Detect numbers and true/false, a column gets a type only when every non-empty value fits it:

• Table and column names are quoted exactly as written, so spaces, reserved words and non-Latin names work: "order date" in PostgreSQL and SQLite, ` order date in MySQL, [order date]` in SQL Server. Embedded quote characters are doubled.
• In values, a single quote is doubled (O'Brien becomes 'O''Brien'). For MySQL, backslashes are doubled too, because MySQL treats \ as an escape by default. SQL Server literals get the N prefix so Unicode text is kept.
• Line breaks inside a quoted CSV value stay inside the SQL string literal.
• NUL characters can't be stored by most databases; they are removed and the tool reports how many.

When the SQL script fails to run

• The script is all one column. The delimiter was guessed wrong; set it under Import settings and open the file again.
• A number column came out as TEXT. At least one value isn't a plain number, for example 12 kg, 1,5 or 007. Find it in the CSV viewer or fix the column with Clean CSV data.
• The UPSERT fails with a missing constraint. ON CONFLICT and ON DUPLICATE KEY only work when the target table has a primary key or unique index on the key columns. Add the index to the existing table, or let Add CREATE TABLE create the key.
• MySQL or SQL Server rejects the PRIMARY KEY. A key column that stays text is created as TEXT (MySQL/MariaDB) or NVARCHAR(MAX) (SQL Server), and neither database can index those types in full. Create the table yourself with a VARCHAR key, then turn off Add CREATE TABLE.
• SQL Server reports that the table already exists. SQL Server scripts use plain CREATE TABLE. Turn off Add CREATE TABLE to load into the existing table, or turn on Add DROP TABLE IF EXISTS first to replace it.
• The script stops partway through. The database error names the failing statement; the usual causes are a duplicate key or a value that doesn't fit a column type of an existing table. Check the file with Validate CSV and run the script again.

Large files and limits

Files up to 25 MB, 100,000 rows or 2 million cells open with a live preview. Larger files are converted in streaming mode: the preview shows the first 200 rows, the file is read twice in chunks (once to learn the column types and widths, once to write the script), and the download covers every row. A single script is capped at 4 GB.

Conversion runs in a background worker in this tab, so the page stays responsive and Cancel stops it. The CSV is never sent to a server. To get a ready-made database file instead of a script, use CSV to SQLite.

Example: a customer list as PostgreSQL INSERTs

A customer list with a leading-zero ID, a name containing an apostrophe and a comma, and an empty plan, converted with the default settings and the table name customers. With Detect numbers and true/false, signup_date becomes DATE, monthly_fee becomes NUMERIC with unquoted 29.00, and active becomes BOOLEAN with TRUE/FALSE, while customer_id stays TEXT.

customer_id,name,signup_date,plan,monthly_fee,active
00412,"O'Brien, Kate",2026-03-01,pro,29.00,true
00413,Luis Ortega,2026-03-04,,0,false

BEGIN;
CREATE TABLE IF NOT EXISTS "customers" (
  "customer_id" TEXT,
  "name" TEXT,
  "signup_date" TEXT,
  "plan" TEXT,
  "monthly_fee" TEXT,
  "active" TEXT
);
INSERT INTO "customers" ("customer_id", "name", "signup_date", "plan", "monthly_fee", "active") VALUES
  ('00412', 'O''Brien, Kate', '2026-03-01', 'pro', '29.00', 'true'),
  ('00413', 'Luis Ortega', '2026-03-04', NULL, '0', 'false');
COMMIT;