Turn a JSON object (or an array of objects) into ready-to-run
SQL INSERT statements or into a TOML document.
All processing happens locally in your browser — nothing is uploaded.
JSON → SQLJSON → TOML
Quote identifiers:
Column names come from object keys (union over all rows). Column types are inferred: whole numbers → INTEGER, decimals → REAL, booleans → BOOLEAN, everything else → TEXT. Nested objects/arrays are stored as JSON text.
One-way JSON → TOML (TOML 1.0). Objects become [tables], arrays of objects become [[array of tables]], scalar arrays stay inline. JSON null has no TOML equivalent and is omitted with a comment. The input must be an object — top-level arrays are not valid TOML.
Input (JSON)
Output
Converts automatically as you type.
Paste JSON on the left and the SQL / TOML appears here on the right.
SQL notes: strings are wrapped in single quotes with '' escaping; missing values become NULL; booleans become
TRUE/FALSE. TOML notes: strings use double quotes with \n etc. escapes; keys that are not bare-safe are quoted.
What is TOML? TOML stands for Tom's Obvious, Minimal Language. It is a human-friendly configuration-file format that looks a bit like INI, but adds clear rules for nested tables, arrays of tables, inline arrays, strings, numbers, booleans and dates. JSON is great for machines talking to machines; TOML is designed for humans editing settings. The converter turns a JSON object into a TOML document: top-level keys become key = value lines, nested objects become [table] sections, and arrays of objects become [[array of tables]] entries. For example, the JSON {"server":{"host":"localhost","port":8080},"debug":true} becomes:
debug = true
[server]
host = "localhost"
port = 8080
Note: the input must be a JSON object; a top-level array is not a valid TOML document. null values are omitted with a comment because TOML has no null type.
🔷 JSON Tools
Export JSON rows as SQL INSERTs / CREATE TABLE, or serialize a JSON object as a TOML document.