SQL to CSV Converter

What the parser accepts

INSERT INTO users (id, email, created_at) VALUES
  (1, 'alice@example.com', '2024-01-12 09:00:00'),
  (2, 'bob@example.com',   '2024-01-13 10:30:00'),
  (3, 'carol@example.com', '2024-01-13 11:15:00');

Becomes:

id,email,created_at
1,alice@example.com,2024-01-12 09:00:00
2,bob@example.com,2024-01-13 10:30:00
3,carol@example.com,2024-01-13 11:15:00

CSV escaping rules applied

• The delimiter is always a comma; there is no separator option.
• Fields containing commas, double quotes or newlines are wrapped in double quotes.
• Internal double quotes are doubled (" becomes ""), per RFC 4180.
• Leading and trailing single quotes from SQL string literals are stripped.
• SQL NULL passes through as the literal text NULL; replace it downstream if your tooling expects empty cells.

Limitations to know

• Column list required. The parser reads the header from the (col1, col2, ...) list before VALUES. A bare INSERT INTO t VALUES (...) without the column list produces CSV rows with no header.
• One table at a time. If your dump mixes INSERTs for different tables, split them first. Rows of different widths produce a ragged CSV.
• No CREATE TABLE parsing. Column types are not used. Dates, JSON and binary blobs come through as raw text.
• Every parenthesis group becomes a row. The parser turns each (...) group into a row, so trailing clauses that contain parentheses (ON DUPLICATE KEY UPDATE, RETURNING), function calls like NOW(), or nested arrays like (1,2,3) inside a value add stray rows. Keep the input to plain INSERT ... VALUES tuples and replace such expressions with literals before pasting.