SQL INSERT to JSON Converter

Single-row and multi-row INSERTs, multiple statements in sequence, multiple tables in the same input, backtick/double-quote/bracket identifier quoting, and schema.table names.

NULL, TRUE/FALSE, integers, decimals, scientific notation, and single-quoted strings with doubled-quote escapes. Comments (-- and /* */) are skipped.

With multiple tables, output becomes {table1: [...], table2: [...]} for easy routing. Off, the output is a flat array with a __table key on each row.

Yes, the SQL INSERT to JSON Converter is 100% free with no registration, no hidden fees, and no usage limits. All processing happens locally in your browser, ensuring complete privacy.

Absolutely. The SQL INSERT to JSON Converter processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the SQL INSERT to JSON Converter is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the SQL INSERT to JSON Converter in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The SQL INSERT to JSON Converter works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

The most common reasons are a missing column list or a value count that does not match the columns. This is a focused, regex-based parser, not a full SQL engine, so it only understands the literal "INSERT INTO table (col1, col2) VALUES (...)" shape. An INSERT written without an explicit column list cannot be mapped to keys and is skipped, and a tuple with too many or too few values for its columns is flagged with a clear parse error. Crucially, one bad statement never blocks the rest: valid statements still convert while the broken one is reported separately, so a single malformed row in a large dump does not lose your data. Check that every statement names its columns and that each VALUES tuple has a matching count, then paste it back in to convert the rest instantly.

By default the converter turns a single-quoted value like '42' into the JSON number 42, because most quoted numerics in a dump are genuinely numbers. Turning Coerce numeric strings off keeps that value as the string "42" instead. This matters whenever a column holds digits that are really identifiers rather than quantities — zero-padded codes such as '007', phone numbers, postal codes, or ID strings — where silently converting to an integer would strip leading zeros or break downstream matching. Unquoted numbers, decimals, and scientific notation are always parsed as numbers regardless of this setting; the toggle only affects values that arrived wrapped in single quotes. If your JSON consumer expects exact string keys or codes, switch the option off before copying. Paste your SQL above and flip the toggle to see both results side by side.

Running SQL in a database executes the statements: it inserts rows, evaluates functions, applies defaults, and changes data on a live server. This converter does none of that. It reads the literal text of your INSERT statements and reshapes the values you already wrote into JSON, entirely in your browser, without connecting to any database or executing anything. That means expressions, function calls like NOW(), subqueries, and DEFAULT keywords are not evaluated — only literal values inside the VALUES clause are parsed. The upside is safety and privacy: you can paste a dump full of production rows and nothing runs, uploads, or mutates. Use a real database when you need to actually load or query data; use this tool when you only need the data shaped as JSON for a fixture, mock, or document store. Paste your INSERTs above to convert them safely.

Paste an entire dump and every INSERT is parsed in one pass, even across semicolons, multiple statements, and several different tables. Non-INSERT statements such as CREATE TABLE are ignored, and line comments (--) and block comments (/* */) are stripped, so a full export still parses cleanly. A live counter shows how many statements, rows, and distinct tables were found, and a preview table displays the first five parsed rows so you can sanity-check the column mapping before you trust the output. When more than one table is present you can group the result into a keyed object per table, or keep a single flat array. Input and output byte counters help you gauge size. When the result looks right, copy it to the clipboard or download it as a .json file. Drop your whole dump above to convert it in one step.

Yes. An Indent control lets you pretty-print the JSON with either 2 or 4 spaces, or choose Minified to produce the smallest possible single-line string with no extra whitespace. Two-space indentation is the common default for readable config and fixture files, four-space suits codebases that follow that style, and minified is ideal when you are embedding the JSON in a script, sending it over the wire, or want the tightest byte count. The indent choice is purely cosmetic — the parsed values, keys, types, and structure are identical across all three modes, so you can switch freely without changing your data. A byte counter next to the output shows exactly how much each mode saves or adds. Pair it with the group-by-table and numeric-coercion options to get output in precisely the shape your consumer expects, then copy or download the result above.