What is YAML / CSV Converter?
YAML and CSV Converter moves object arrays between configuration text and spreadsheets. Nested objects use dotted headers, arrays stay JSON text, imported CSV cells remain strings, and spreadsheet-safe mode reduces formula-like cell risk. Common workflows include the following. Export a YAML list for spreadsheet review. Convert table data into YAML configuration or fixtures. Inspect nested headers, quoted line breaks, and formula risk. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.
When to use it
- Export a YAML list for spreadsheet review.
- Convert table data into YAML configuration or fixtures.
- Inspect nested headers, quoted line breaks, and formula risk.
How to use it
- Choose comma, semicolon, or Tab delimiter.
- Use an object array for YAML conversion.
- Enable spreadsheet-safe mode when required.
- Convert and review string typing and dotted headers.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
- Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.
Runnable examples
The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.
Example 1
- name: Ada
role: admin
profile:
city: Shanghai
- name: Lin
role: editor
profile:
city: ChengduExample 2
name,role,note
Ada,admin,"Review YAML, CSV, and formula safety"
Lin,editor,"The second row contains ordinary text"Input rules
- The YAML root must be a non-empty array of objects.
- The first CSV row must contain unique, non-empty headers.
- Confirm delimiter and spreadsheet-safety options before conversion.
- Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
- YAML must be a non-empty array of objects.
Output rules
- Nested objects use dotted column headers.
- Arrays remain JSON text inside cells.
- Imported CSV values stay strings and are emitted as YAML.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- CSV cells remain strings after import.
Limitations and cautions
- YAML must be a non-empty array of objects.
- CSV cells remain strings after import.
- Nested objects use dotted paths and arrays remain JSON text.
How your data is handled
All parsing, conversion, binary encoding, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.