YAML to CSV Converter

No. The conversion runs entirely in your browser with js-yaml and PapaParse, so your YAML never leaves your device and nothing is stored on a server.

A sequence of mappings, where each list item is a record with roughly the same keys. A single mapping also works and becomes one CSV row. A bare scalar like a lone number or string is rejected because it has no columns to build.

The header is the union of keys across every record, in the order they first appear. Records that are missing a column get an empty cell, so heterogeneous data still aligns under the right headers.

CSV cells hold flat text, so any nested mapping or array is written as compact JSON inside its cell, such as {"city":"Portland"}. Top-level scalars like strings, numbers and booleans stay as plain values.

Comma, semicolon, tab or pipe, chosen from the Delimiter menu. Any field that contains the delimiter, a quote or a line break is wrapped in quotes automatically so the file stays valid.

Rows are separated by a carriage return and line feed, the line ending the CSV standard recommends and that Excel expects. Most spreadsheet apps and parsers read it without any trouble.

If a top-level array item is a scalar or a nested list, it is placed under a single value column so nothing is lost. Mixing objects and loose values in one list is allowed but usually means the source YAML needs tidying.

The input must be valid YAML that describes a list of objects or a single object. A syntax slip, wrong indentation, or a top-level value that is only a number or string will be rejected with a short message.

Not with this tool, which only goes one way. To move in the other direction, or to reshape data, pair it with the related JSON and CSV converters listed below.