Convert JSONL to SQL free in your browser. Paste your JSON Lines on the left, press Convert, and copy clean SQL INSERT on the right. No sign-up, no uploads.
Converter
Paste JSON Lines below, press Convert, and copy the SQL INSERT output.
Advertisement
How JSON Lines becomes SQL
Each non-empty line is parsed as its own JSON object and treated as one row, so a 10,000-line file is simply 10,000 rows. The converter collects the union of all keys across lines to build the column set, which means ragged objects with different keys still convert cleanly, with blanks where a line lacked a key.
Tips for the SQL output
Set the table name before converting, and check that the auto-detected columns match your schema, adding NOT NULL defaults or indexes afterwards in your own migration. The single multi-row INSERT keeps imports fast, and because strings are escaped with doubled quotes, the output runs as-is in MySQL, MariaDB, PostgreSQL and SQLite.
One complete JSON object per line, with no commas between lines and no outer array brackets. Each object becomes one row, and the union of all keys becomes the SQL INSERT columns. Blank lines are ignored, and the tool tells you the exact line number if one line fails to parse.
Can I control the table and column names?
Yes, type the target table name in the field above the input; it is sanitized to letters, digits, _ and $. Column names come from your JSONL headers and are backtick-quoted. Strings are single-quoted with '' escaping, NULL stays NULL, and every row lands in one multi-row INSERT.
What about nested objects inside a line?
Nested objects and arrays are kept as compact JSON strings inside their cell, so nothing is dropped. If you need them flattened into dotted columns, convert to JSON first and flatten there; this tool keeps the SQL INSERT one row per line.
Is there a size limit for JSONL input?
No hard limit, but everything runs in your browser tab, so tens of thousands of rows convert in seconds while millions of rows may slow the page. For very large JSONL files, split them into smaller chunks and convert each separately.
Is my JSONL data private, and who uses this?
Yes. The conversion runs 100% in your browser; nothing is uploaded to any server. Developers, analysts and DBAs use it to move JSONL data into SQL INSERT for migrations, reports and config work without installing anything.