LOCAL DATA CONVERTER / YAML TO CSV

YAML to CSV

Project a YAML sequence of flat mappings into formula-protected UTF-8 CSV with stable union columns.

Processed in this browserOne UTF-8 .yaml or .yml file up to 5 MB. It must contain one non-empty top-level sequence of flat scalar mappings within 50,000 records, 200 columns, 1,000,000 values, and 20 MB output.

Step 1 / source

Choose the source

YAML - flat mapping sequence

Drop one file here

Choose the flat yaml record sequence you want to turn into utf-8 csv table.

Browse filesChecking publication status...

No file upload

This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.

Original stays unchanged

The converter creates a separately named output. It never writes back into the source file.

Bounded work

One UTF-8 .yaml or .yml file up to 5 MB. It must contain one non-empty top-level sequence of flat scalar mappings within 50,000 records, 200 columns, 1,000,000 values, and 20 MB output.

Plain-language method

How YAML to CSV works

The browser parses exactly one YAML document with unique-key and alias safeguards, requires a sequence of mappings with scalar values, builds headers in first-seen order, and writes one formula-protected CSV row per mapping.

01
Choose a valid source
Use a dash-led top-level sequence. Every item must be a mapping whose values are strings, numbers, booleans, or null.
02
Review the conversion choices
Keep formula protection enabled when the CSV will be opened in a spreadsheet. It does not affect numbers or ordinary text.
03
Inspect the separate result
The result ends in _nirmion_tools.csv. Missing and null mapping values become empty cells.

Useful when

Practical jobs this tool handles

Review flat YAML records in spreadsheet software.
Prepare configuration lists for a CSV import.
Audit property coverage across mapping items.

Before converting

Check the source and destination rules

Confirm there is only one YAML document.
Flatten nested mappings and sequences.
Review empty cells and union headers.

Know the boundary

Know what the destination format cannot keep

CSV cannot preserve comments, anchors, tags, nested structures, or the difference between null and a missing property. Nested data is rejected.

Quick answers

Questions before you convert

The conversion contract is deliberately explicit.

Can YAML contain several documents?

No. This route requires exactly one document for one clear output table.

Are aliases expanded?

Bounded aliases may resolve during parsing, but alias-heavy or unsafe input is rejected.

Why are nested mappings rejected?

There is no universal, reversible way to flatten them into CSV columns.