YAML to CSV Converter
Convert YAML files to CSV format
Paste or upload YAML and get a CSV table back. It is the fastest way to review a long list of YAML records — environments, services, users, feature flags — in a spreadsheet instead of scrolling through indentation.
A YAML list of records becomes rows, and nested keys are flattened into columns so structure is preserved rather than discarded. Records that do not share identical fields still line up, because the header row covers every key found across the document.
Conversion happens in your browser, which matters for YAML in particular: config files routinely sit next to secrets and infrastructure detail you should not paste into an unknown website.
Drop your file here or browse from your device
Accepts YAML, YML. Maximum input: 10 MiB. Files above this hard limit are rejected before local processing.
How to Convert
- Paste your YAML or upload a .yaml or .yml file
- Check the parsed columns in the preview table
- Confirm nested keys flattened the way you expect
- Download the CSV file
Features
- Converts a YAML list of records into rows
- Flattens nested keys into dot-notation columns
- Builds a header row from every key found across records
- Handles quoted strings, booleans, numbers, and null values
- Preview the parsed table before downloading
- Proper CSV quoting for values containing commas or newlines
- Runs entirely in your browser — no upload
Use Cases
- Review a long YAML config as a sortable, filterable table
- Audit environment or service definitions side by side
- Move YAML-managed reference data into a spreadsheet for editing
- Compare two config files by converting both and diffing the CSVs
- Hand structured config to colleagues who work in Excel or Sheets
Frequently Asked Questions
What YAML structure does this expect?
A list of records — a top-level sequence where each item is a mapping of keys to values. That is the shape that maps cleanly onto rows and columns.
How is nested YAML handled?
Nested keys are flattened into dot-notation columns, so a database block containing host and port becomes database.host and database.port columns.
What if my records have different keys?
The header row is the union of all keys found. A record missing a field gets an empty cell rather than shifting its remaining values into the wrong columns.
Does it work with .yml files?
Yes. The two extensions are the same format, and both are accepted.
What happens to booleans and nulls?
Booleans are written as true and false. Null and empty values become empty cells, which is what a spreadsheet expects.
Is my config file uploaded anywhere?
No. It is parsed in your browser and never sent to the app server — worth knowing, since config files often sit close to credentials and infrastructure detail.