Every API Returns JSON. Stakeholders Want Spreadsheets. This Is the Bridge.
I can't count how many times I've exported data from an API or a database, opened the JSON, and immediately needed to send it to someone who wanted it in Excel. It's not a technical problem. It's a format problem. JSON is how machines talk to each other. CSV is how people talk about data. You need a conversion step, and you want it to take ten seconds, not ten minutes.
This tool takes a JSON array of objects and converts it to CSV with a header row, properly escaped values, and your choice of delimiter. Paste in, copy out. No libraries to install, no Python scripts to write, no spreadsheet formulas to wrangle.
How the Conversion Works
The input format expected is a JSON array of objects — the most common shape you get from REST APIs. Something like: [{"name":"Alice","role":"Engineer"},{"name":"Bob","role":"Designer"}]. The tool scans all objects to collect every unique key across the entire array, then builds a column for each key. Each object becomes a row, with empty cells for any keys that object doesn't have.
Values that contain the delimiter character, quotes, or newlines are automatically wrapped in double quotes and escaped per the RFC 4180 CSV standard. So you don't need to worry about breaking the spreadsheet with commas inside address fields or line breaks in description fields.
You can choose between comma, semicolon, tab, or pipe as the delimiter. Semicolon is the right choice if you're in a European locale where Excel defaults to semicolon-delimited CSV. Tab-separated is useful when values might contain commas and you want a cleaner separator.