Generate MySQL CREATE TABLE and INSERT statements from JSON, with backslashes escaped
Runs in your browser. Nothing you type is sent anywhere. Checked against sources on 17 Oct 2026.MySQL treats a backslash inside a string as an escape character, so a Windows path such as C:\temp pasted into an INSERT by hand silently loses characters. This converter writes MySQL INSERT statements with backslashes doubled, quotes doubled and reserved column names such as order in backticks, plus a CREATE TABLE using VARCHAR(255), DOUBLE, BOOLEAN, DATE and JSON columns.
Paste or type your input.
Choose the options you need.
Press Ctrl+Enter, then copy or download.
Seeding a test database, loading an API response for analysis or moving a spreadsheet into a table all start with the same chore: writing a CREATE TABLE and a pile of INSERT statements. This page writes both from the data itself.
Escaping that differs by database. A single quote is doubled everywhere. MySQL also treats a backslash as an escape character, so backslashes are doubled for MySQL and only there. SQL Server gets an N prefix on text with non-ASCII characters so Hindi or emoji survive. Reserved or mixed-case column names are quoted with double quotes, backticks or brackets as each database expects.
How it was checked. The output for 15 test cases, covering quotes, backslashes, emoji, reserved names, nested JSON, nulls, big integers and timestamps, was run in PostgreSQL 17 and SQLite 3.35, and the rows each engine read back equal the input. Nothing you paste leaves your browser. To go the other way, from INSERT statements back to JSON, use SQL to JSON.
The rest of the article, and all 6 questions about JSON to SQL Converter, are on the JSON to SQL Converter page.
Paste the JSON array here, choose your database and copy the script: a CREATE TABLE with a column per key, then INSERT statements with every value escaped. Run the script in psql, the MySQL client, sqlite3 or SQL Server Management Studio. Nested objects and arrays go into a JSON or text column.
Each column is typed from all of its values: whole numbers become INTEGER, or BIGINT beyond 2,147,483,647; decimals become NUMERIC, DOUBLE, REAL or FLOAT; true and false become BOOLEAN or BIT; YYYY-MM-DD strings become DATE; objects become JSON. Anything mixed becomes text, and the page tells you which columns.
MySQL reads a backslash inside a string literal as the start of an escape such as \n, unless the server runs with NO_BACKSLASH_ESCAPES. Doubling every backslash keeps a path like C:\temp intact. PostgreSQL, SQLite and SQL Server read backslashes literally, so their output leaves them as they are.
SQL Server allows 1,000 rows in one VALUES list and returns error 10738 beyond that. PostgreSQL, MySQL and SQLite have no fixed row limit, but very long statements hit packet or memory limits, so 100 to 1,000 rows per statement is a safe choice. Batches here default to 100 rows.
Rates and rules change; check the source before you rely on a figure.
Still stuck? Ask about JSON to SQL Converter and anybody who knows can answer. No account needed.
Same job, other tools: Query String Parser – Split a URL query string into a table of decoded parameters · TSV to JSON – Convert tab-separated values, such as a paste from Excel, into JSON · JSON to YAML – Turn JSON into clean, readable YAML for configs.