106 characters · 8 words · 106 bytes (UTF-8)
Output will appear here
Click in the output to select all text
106 characters · 8 words · 106 bytes (UTF-8)
Output will appear here
Click in the output to select all text
Convert CSV rows into an array of JSON objects with type inference.
Convert CSV data into structured XML.
Convert YAML data into tabular CSV format.
Convert JSON data to clean YAML syntax with configurable indentation.
Beautify and format YAML documents with standardized indentation.
Format and align CSV columns with consistent delimiters and quoting.
Configuration and fixture data often starts life in a spreadsheet — someone maintains a list of environments, feature flags, or seed records in columns — and then needs to become YAML for a config file, a Helm values file, or a test fixture. Retyping that by hand is slow and introduces exactly the indentation mistakes YAML punishes. This converter turns each CSV row into an item in a YAML sequence, using the header row for keys, with correct indentation and quoting applied automatically where a value would otherwise be misread. Quoted fields containing commas or line breaks survive intact, and you can pick the delimiter if your export is semicolon or tab separated. Paste, convert, copy. Everything happens in your browser, so exports containing internal or customer data stay on your machine.
A sequence of mappings: one list item per CSV row, with the header row supplying the keys. That is the shape most config files and fixtures expect.
Values are quoted where leaving them bare would change their meaning — for example text that YAML would otherwise read as a boolean, a number, or a null.
Yes, but only when it is safe. A value becomes a number just when converting it back produces the identical text, so 36 and 3.14 are emitted unquoted while identifiers like 01234 and trailing-zero decimals like 1.50 stay quoted strings. Values reading true or false become booleans.
Yes. Comma, semicolon, and tab are all supported, which covers most spreadsheet exports including European locale files.
It is quoted in the output, because a bare colon followed by a space would otherwise be read by YAML as a key separator.
No. The conversion runs entirely in your browser and nothing is transmitted or stored.