What input shape does the tool expect?▾
The tool expects a JSON array of objects at the top level, such as [{"id":1},{"id":2}]. A single object is also accepted and produces a one-row CSV. Primitive arrays like [1,2,3] produce a single-column file.
How are nested objects handled?▾
Nested objects can be flattened to dot-notation columns (address.city) or serialized as JSON strings. Arrays within objects are serialized as JSON strings by default since they cannot map cleanly to flat columns.
What happens when records have different keys?▾
The tool unions all keys found across every record to build the header row. Records missing a key get an empty cell in that column, which is the correct behaviour for sparse data.
Does it handle special characters and Unicode?▾
Yes. The output is UTF-8 encoded. Values containing commas, double-quotes, newlines, or multibyte characters are correctly quoted per RFC 4180.
Why does Excel show garbled text when I open the CSV?▾
Excel may not detect UTF-8 encoding automatically. Add a UTF-8 BOM (byte order mark) at the start of the file, or import via Data > From Text/CSV and choose UTF-8 encoding in the wizard.
Can I convert back from CSV to JSON?▾
Yes — UtilityKit's csv-to-json tool handles that direction, automatically detecting headers and producing a JSON array of objects.
What is the maximum size the tool can handle?▾
The tool is browser-based and handles typical API export sizes (tens of thousands of rows) without issues. Very large files above a few MB may slow down the browser tab; for those use a command-line tool like jq or csvkit.
How do I choose between comma, semicolon, and tab delimiters?▾
Use comma for most English-locale tools. Use semicolon for European tools where the comma is the decimal separator. Use tab when pasting directly into a spreadsheet, since tab-separated values paste into separate cells without needing an import dialog.