SQL to JSON / JSON to SQL Converter

What the INSERT reader expects

Statements may span several lines, and a multi-row VALUES (…), (…) from mysqldump gives one object per row. Commas, parentheses, and semicolons inside quoted strings are kept as text. Quoted values stay strings, so '02134' keeps its leading zero; only bare numerals become numbers, and bare TRUE, FALSE, and NULL become JSON's true, false, and null. A statement with no column list gets keys column_1, column_2, and so on. Other statements, such as CREATE TABLE, are skipped.

A function call such as NOW() is kept as its SQL text, not evaluated. For very large dumps, exporting straight to JSON or CSV from the database is faster and more exact.

Checking generated INSERT statements

The column list comes from the first object. Keys that appear only in later objects are dropped, and keys missing from a later object become NULL. Table and column names are written unquoted, so a column named order, user, or group fails as a reserved word; quote it with double quotes in PostgreSQL or backticks in MySQL. Nested objects are inserted as JSON text, which suits a json column. From a spreadsheet, CSV to SQL INSERT is the direct route.

How to use it

1. Choose JSON to SQL or SQL to JSON mode.
2. Paste JSON array or SQL INSERT statements.
3. Click Convert to view, copy, or download the result.

Privacy & limitations

Parsing and conversion run entirely inside client memory.