CSV → YAML — tabular data as readable nested text
Great when analysts hand off CSV extracts that GitOps reviewers prefer as indented YAML lists.
Developer notes
• Scalar casting still manual — YAML receives strings. • Align quoting mode with team style guides.
When teams pick this route
• Support exporting ticket CSV into Ansible-friendly lists. • Teaching how tabular data nests visually.
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
Inventory snapshot
Sample input
Sample output
Wide rows
Sample input
Sample output
Navigate related converters
Mirror XML export via CSV → XML, structured JSON via CSV → JSON, or reverse via YAML → CSV.
CSV → YAML FAQ
Emitter nuances
Quoted scalars?
Controlled via YAML string quoting options — deterministic, not source-preserving.
Maps vs lists?
Uniform rows become sequences of mappings.
Comments?
Add manually after conversion.
Delimiter mistakes?
Mis-selected delimiter yields noisy warnings — adjust CSV input options.
Looking for every converter, encoder, and minifier in one place? Developer tools hub Open the curated developer tools catalogue.