Free · No signup · Browser-based

Convert SQL to YAML.

Drop SQL INSERT statements and get a clean YAML list of mappings with real scalar types — unquoted numbers, booleans and nulls. It all runs in your browser — no signup, no upload, no watermark.

To convert SQL to YAML, drop or paste SQL INSERT statements — csvtodashboard parses it into rows and columns in your browser, then emits a clean YAML list of mappings with real scalar types. Numbers, booleans and nulls become unquoted YAML scalars, while values YAML could misread — like NO or a leading-zero code — are quoted so they survive. Nothing is uploaded; the whole conversion runs on your device.

01 · How it works

Three steps, then done.

This converter pulls the rows out of your INSERT ... VALUES statements — column names come from the INSERT column list, or from a CREATE TABLE in the same dump, then writes a clean YAML list of mappings with real scalar types — unquoted numbers, booleans and nulls. Both sides are tabular, so it is a clean, lossless mapping — no nesting to flatten and no structure to guess. Types are inferred as the data is read, and the whole conversion runs locally in your browser, so your file never leaves your device.

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 YAML conversion by default.

Free YAML 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 YAML 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

sql to yaml notes.

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

  • The "Norway problem"

    In YAML, a bare NO, ON, OFF or YES can parse as a boolean. Values that could be misread are quoted so they stay the strings you intended.

  • Leading zeros stay intact

    Codes like 007 or 0123 would read as numbers unquoted, so ambiguous numerics are quoted to preserve them character-for-character.

  • Indentation is structure

    Output is two-space, block-style YAML (never tabs); strings containing a colon, hash, or leading dash are quoted so the document always parses.

03 · FAQ

sql to yaml questions.

What SQL input works?
Standard INSERT INTO ... VALUES (...) statements, single- or multi-row. Column names are taken from the INSERT column list (or a CREATE TABLE if the dump has one). Other statements are ignored.
Numbers, booleans and nulls are emitted as unquoted YAML scalars; only values that need quoting get quoted. The output is block-style and loads in any YAML parser.
No hard limit. Parsing and conversion run in your browser, with large inputs handled off the main thread so the tab stays responsive — you are bounded only by your device's memory.
No. The entire sql-to-yaml conversion happens locally in your browser — the file never touches a server. Watch DevTools → Network to confirm nothing is sent.