Convert a PostgreSQL dump to CSV
Have a pg_dump .sql export with INSERT statements? Drop it in or paste it and get clean CSV or Excel back — every table separated, nothing uploaded.
Works with MySQL, PostgreSQL, SQLite and SQL Server dumps · smooth up to tens of MB; ~100 MB+ works but is slower
Your data stays private
Files are read and converted locally. They never leave your computer or touch a server.
Every table, separated
A dump with many tables becomes one tidy spreadsheet per table — not one giant blob.
CSV or Excel
Download a single CSV, all tables zipped, or one .xlsx workbook with a tab per table.
Keeps your tab responsive
Parsing runs off the main thread in a worker, so the page never freezes — even while it chews through a big dump.
How it works
- 1
Drop your file
Drag in any .sql dump from MySQL, Postgres, SQLite or SQL Server — or paste the SQL directly.
- 2
Preview the tables
See each table as a real grid and check the data looks right.
- 3
Download
Grab CSV, a zip of all tables, or an Excel workbook.
Questions
Which pg_dump exports work here?
Plain-format dumps where the data is written as INSERT statements — i.e. pg_dump run with --inserts or --column-inserts, or any .sql file built from INSERTs. The tool reads CREATE TABLE for column names and INSERTs for the rows.
My pg_dump file shows COPY ... FROM stdin, not INSERT. Why?
That's pg_dump's default plain format, which streams data with COPY blocks instead of INSERTs. To use this tool, re-export with `pg_dump --inserts your_db > dump.sql` and the data becomes INSERT statements it can read. (Direct COPY-block support is on the roadmap.)
Is my PostgreSQL data uploaded anywhere?
No. The .sql file is parsed entirely in your browser with a local worker. Nothing leaves your device, so it's safe for production dumps.
Does it handle double-quoted identifiers and schemas like public.table?
Yes. Double-quoted identifiers are unquoted and schema-qualified names like public."customers" resolve to the table name, with one spreadsheet per table.
What about NULLs and quoted text?
NULL becomes an empty cell, single quotes escaped as '' are handled, and commas or newlines inside values are quoted correctly for CSV and Excel.