SQL to CSV Converter
Extract data from SQL INSERT statements to CSV
Paste a SQL dump or a set of INSERT statements and get the rows back as CSV. This is the fastest way to read data out of a .sql file when you do not want to spin up a database just to run a SELECT against it.
The parser reads INSERT INTO statements, takes column names from the statement itself, and splits the VALUES tuples while respecting quoted strings — so a value containing a comma or an escaped quote stays in one field instead of splitting the row. NULL becomes an empty cell rather than the literal text.
CREATE TABLE statements in the same dump are read for column structure, and each table found is offered separately so a multi-table dump does not have to be split by hand first.
Supports INSERT INTO statements. Each table will be converted to a separate CSV.
How to Convert
- Paste your SQL statements or upload a .sql file
- Choose the table if the dump contains more than one
- Review the extracted rows in the preview
- Download the CSV file
Features
- Parses INSERT INTO ... VALUES statements, including multi-row inserts
- Takes column names from the statement or an accompanying CREATE TABLE
- Respects quoted strings so commas and escaped quotes do not split a row
- Converts SQL NULL to an empty cell instead of the text "null"
- Handles multiple tables in one dump and lets you pick which to export
- Preview the extracted rows before downloading
- Runs entirely in your browser — the dump is never uploaded
Use Cases
- Read the contents of a database backup without restoring it first
- Pull rows out of a .sql dump for analysis in Excel or Sheets
- Move seed data between projects or environments
- Review what a migration script will actually insert
- Convert a legacy export into a format a modern tool can import
Frequently Asked Questions
What SQL does this understand?
INSERT INTO statements with an explicit column list, including multi-row VALUES tuples. CREATE TABLE statements in the same file are also read to recover column structure.
Does it work with a full mysqldump file?
It extracts the INSERT statements from it. Surrounding dump content such as SET commands, comments, and index definitions is ignored rather than turned into rows.
What happens to NULL values?
They become empty cells, which is what a spreadsheet or CSV import expects — rather than the literal four-character text "null".
Will a comma inside a quoted value break the row?
No. Values are split with quoting respected, so a string containing commas, or an escaped quote inside a string, stays in a single field.
Can it handle a dump with several tables?
Yes. Each table found in the file is available separately, so you can export just the one you need.
Do I need a database to use this?
No, and that is the point — the statements are parsed as text in your browser, so you can read a dump without a server, a client, or a restore.
Is my SQL file uploaded?
No. Parsing happens in your browser and the contents are not sent to the app server, which matters because dumps often contain production data.