Free · No signup · Browser-based

Convert JSON to SQL.

Drop a JSON file and get CREATE TABLE + INSERT statements, with column types inferred from the data. Nested objects and arrays are flattened into dot-notation columns — every value kept, structure not. Runs in your browser.

To convert JSON to SQL, drop or paste a JSON file — csvtodashboard parses it into rows and columns in your browser, then emits CREATE TABLE + INSERT statements, with column types inferred from the data. You get CREATE TABLE plus INSERT statements with column types inferred from the data and string values quoted and escaped. Nothing is uploaded; the whole conversion runs on your device.

01 · How it works

Three steps, then done.

This reads your JSON — an array of objects becomes rows, then writes CREATE TABLE + INSERT statements, with column types inferred from the data. Because SQL is a flat, tabular format, nested objects and arrays in your JSON are flattened into dot-notation columns (e.g. user.address.city) — that keeps every value but does not preserve the hierarchy, so the conversion is one-way. Everything runs locally in your browser.

i. drop

Drop or paste

Drag a file, click to choose, or paste data directly into the input pane.

ii. detect

We read the shape

Types are inferred so the output is correctly formatted — not strings everywhere.

iii. use it

Copy, download, or dashboard

Copy the output, download it, or hit 'Build dashboard' to chart what's in the data.

02 · Why ours

Smart SQL conversion by default.

Free SQL converters often produce sloppy output — every value quoted, types lost, errors swallowed. Ours infers types where it can, fails loudly when it can't, and pairs the conversion with a one-click path to a dashboard.

  • 01

    Correct types

    Numbers, booleans and nulls are preserved wherever SQL supports them — not every value dumped as a quoted string.

  • 02

    Local-first

    Your file is parsed and converted in your browser — verify in DevTools → Network. Nothing is uploaded, logged, or stored.

  • 03

    Fails loudly

    Malformed input gives a clear, specific error instead of silently wrong output — so you can trust what comes back.

  • 04

    One click to a dashboard

    Every conversion keeps a tabular copy, so you can send the data straight to our visualization tool to chart it.

"Needed a conversion. Ended up with a dashboard. That's the pattern."
— the typical csvtodashboard arc
Good to know

json to sql notes.

Format-specific details worth knowing before you convert JSON to SQL.

  • Nesting is flattened, not kept

    JSON can nest objects and arrays; converting to SQL flattens them into dot-notation columns. Every value is preserved, but the hierarchy is not — it is a one-way conversion.

  • Types are inferred

    Column types (INTEGER, REAL, TEXT) come from the data, not VARCHAR everywhere, so the generated CREATE TABLE matches your actual values.

  • Quotes are escaped

    String values are single-quoted with embedded quotes doubled, as in O''Brien — the standard SQL escape — so the INSERTs run as written.

  • Blanks become NULL

    Empty cells are emitted as NULL rather than an empty string; rename any header that clashes with a SQL reserved word before importing.

03 · FAQ

json to sql questions.

What JSON input works?
Any JSON that is an array of objects (the most common data shape); a single object becomes one row. Deeply nested JSON works too — it is flattened with dot notation.
Nested objects and arrays are flattened into columns using dot notation (user.name, user.address.city). Arrays of scalars are joined; arrays of objects are JSON-stringified into a single cell. Your data is preserved, but the nested structure is not — this is a one-way conversion.
A CREATE TABLE plus INSERT statements. Column types (INTEGER, REAL, TEXT...) are inferred from the values, which are quoted and escaped correctly.
No. The whole json-to-sql conversion happens locally in your browser — the file never touches a server.