YAML → CSV — tabular slices from structured configs
Flatten YAML that unwraps to JSON arrays/objects into spreadsheet rows with the same dotted-column rules as JSON → CSV.
Developer notes
• If YAML parses to scalars, CSV export may be empty — reshape into tables. • Nested maps flatten with dotted headers like JSON exports.
When teams pick this route
• FinOps translating YAML price sheets into Sheets. • SRE snapshots needing spreadsheet filters.
About these options
CSV exports: choose a delimiter (Auto follows locale — semicolon on /fr), RFC-minimal vs always-quoted fields, line endings, and whether to emit a header row. CSV imports: delimiter + whether row 1 holds column names (Auto delimiter follows locale only for convenience). JSON output (XML, YAML, or CSV sources): indentation (including compact one-line) and optional recursive key sort. JSON → XML: toggle pretty-printing and indent width. YAML output: indent width, readable vs tighter layout, and deterministic string quoting (there is no source YAML file to “preserve”). XML comments are not represented in the intermediate JSON tree.
Worked examples
Uniform list
Sample input
Sample output
Wrapper unwrap
Sample input
Sample output
Navigate related converters
Stay tabular with JSON → CSV, inspect trees via YAML → JSON, or export XML using YAML → XML.
YAML → CSV FAQ
Flattening caveats
Mixed-type columns?
Everything becomes strings in CSV cells — cast downstream.
European delimiters?
Use Auto on /fr routes or pick semicolon explicitly.
Comments in YAML?
Comments vanish after JSON intermediate — capture them elsewhere.
Quoted commas inside cells?
Exporter handles RFC-style quoting per options.
Looking for every converter, encoder, and minifier in one place? Developer tools hub Open the curated developer tools catalogue.