Quick reference
| Setting | Value / behavior |
|---|---|
| Delimiter | comma |
| Header row | required and unique |
| Cell typing | strings only |
Input and conversion rules
The first CSV row becomes the list of property names. Headers must be unique and non-empty, and each following row must contain exactly the same number of columns. The parser supports commas inside quoted fields, doubled quotes, embedded line breaks, CRLF and LF line endings, and an optional UTF-8 byte-order mark. It reports inconsistent rows rather than quietly discarding extra cells. A trailing record separator does not create a phantom data row.
Important edge cases
All cells remain strings. A postal code such as 00123 should not silently become 123, and a date should not be guessed using the browser’s locale. Empty cells become empty strings rather than null. If your destination needs numeric or Boolean values, convert those fields explicitly with knowledge of the schema. Semicolon-delimited spreadsheets and tab-separated files are not supported by this comma-only parser. Normalize their delimiter in a trusted editor first.
A reliable workflow
First run the built-in example to understand the output structure. Replace it with a small representative sample from your own workflow and inspect every field that has special meaning: identifiers, currency, dates, missing values and nested collections. Then process the complete input, up to two million characters. The result can be copied or downloaded. Keep a separate original because conversion is not always reversible, especially when the target format cannot represent all the distinctions in the source.
Privacy and verification
The transformation runs in your browser using local JavaScript. There is no data-upload request and no account requirement. The page does not save your input to browser storage or place it in a shareable URL. Clearing the form removes the displayed input and result; it does not delete the original file or erase your operating system’s clipboard. Check the receiving program with a small import before loading a complete dataset. If the input is untrusted, retain formula protection where available and avoid running exported commands without review.
Frequently asked questions
Are my values uploaded?
No. The conversion is performed in the page.
Is the conversion lossless?
Not always. Review the edge cases above, especially missing values, nested data and number precision.
Why did validation fail?
Check syntax, expected input shape and the specific row or parser error shown by the tool.
About this tool
Built and maintained by Mihai at Void Fabric. This page documents the behavior of the current implementation. Found an error or an unclear assumption? Send a reproducible example with sensitive values removed.
Reference: Void Fabric field notes · Testing and editorial policy