SQL INSERT to CSV. Straight from the dump.
Paste INSERT statements from a database dump and get the rows back as a CSV table, without a database anywhere in sight.
Your table preview will appear here
How to use SQL INSERT to CSV
Paste the statements
One INSERT or a whole dump. Statements for different tables are separated automatically, each becoming its own table.
Check the columns
Column names come from the statement's own column list. Quoted strings, escaped quotes and NULL values are read properly rather than split on the wrong comma.
Download or copy
Take a CSV file, or copy the rows and paste them straight into a spreadsheet.
Why use Parsefy SQL INSERT to CSV?
Your data never leaves your device
Everything runs in your browser tab — there is no upload step and no server to store anything. That makes it safe for API responses, database dumps and production data you could not paste into a hosted converter.
Commas inside values do not break it
Splitting a VALUES list on commas is the obvious approach and the wrong one: a value like 'Berlin, Germany' immediately shifts every column after it. The statements are scanned properly, so quoted text, escaped quotes and brackets inside a value all stay where they belong.
No database required
The usual way to read a dump is to restore it somewhere first, which means having a server available and being willing to run someone else's SQL. Reading the statements directly avoids both, and nothing is executed.
Keeps working offline
Once the page has loaded, no network connection is required. Drop your Wi-Fi and the tool keeps running, which is handy on a plane or inside a locked-down corporate network.
SQL INSERT to CSV — frequently asked questions
Which SQL dialects does this read?
The INSERT syntax common to MySQL, PostgreSQL, SQLite and SQL Server: backtick, double-quote and bracket quoted identifiers, single-quoted strings with either doubled-quote or backslash escapes, NULL, and multi-row VALUES lists. Statements other than INSERT are ignored.
Is my dump uploaded anywhere?
No. The statements are read in your browser tab and nothing is executed or transmitted. That matters here more than usual, because a dump is production data by definition and pasting one into a hosted tool would be handing over the database.
What if the INSERT has no column list?
The columns are numbered column_1, column_2 and so on, and a notice says so. The statement simply does not record what the fields are called, so inventing names would be guessing — add a column list to the statement to get real headers.
What happens if the dump is cut off?
The complete rows are recovered and you are told how many, with the unfinished one left out. Copying part of a large dump out of a terminal is the usual way this happens, and losing the whole conversion over the last partial row would not help.