Free · No signup · Browser-based

Convert YAML to CSV.

Paste a YAML list of mappings, get a CSV with one row per item. Nested objects are flattened with dot notation. Free, browser-based.

01 · How it works

Three steps, then done.

This converter handles the most common YAML shape — a top-level sequence of mappings — and turns it into a CSV. Nested mappings get flattened with dot notation (e.g. <code>user.address.city</code>). Unsupported YAML features (anchors, aliases, tags, multi-document, block scalars) raise a clear error rather than silently corrupting data.

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

Free CSV 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 dates are detected as you import, so the CSV (and any dashboard built from it) treats them correctly — not everything as text.

  • 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
03 · FAQ

yaml to csv questions.

What YAML shapes are supported?
A top-level sequence of mappings (the most common shape for data), a single flat mapping (becomes one row), and basic scalars. Block style only — flow style ([…], {…}) is preserved as raw text.
Anchors and aliases (&id, *id), tags (!!str etc.), block scalars (| or >), multi-document streams (---), and complex flow-style nesting. The converter raises a clear error when it sees these.
Yes — using dot notation. user: { name: Alice, address: { city: Berlin } } becomes columns user.name and user.address.city.
Unquoted YAML scalars are parsed as their type (numbers, booleans, null). Quoted scalars are kept as strings. The resulting CSV preserves these as cell text.