無料オンラインJSONからCSVへのコンバーター
APIレスポンス、MongoDBエクスポート、または設定データをExcelやGoogleスプレッドシートで開けるCSV行に変換します。各オブジェクトが1行に、各プロパティが1列になります。ネストされたオブジェクトと配列は、セル内のJSON文字列としてシリアライズされます。
区切り文字（カンマ、セミコロン、タブ、パイプ）を選択し、ヘッダー行を切り替え、結果をコピーするか、.csvファイルをダウンロードします。すべての変換はブラウザで行われます -何もアップロードされません。
Frequently Asked Questions
What JSON structure works for CSV conversion?
An array of objects works best: [{"name": "Alice", "age": 30}, {"name": "Bob", "age": 25}]. Each object becomes a row; each property becomes a column. A single object converts to one row. Nested objects and arrays are serialized as JSON strings in the cell.
Which delimiter should I use?
Comma is standard for US English locales and most APIs. Semicolon is common in European Excel locales where comma is the decimal separator. Tab (TSV) works well for copy-pasting into spreadsheets. Pipe is useful when your data contains commas.
Can I open the output in Excel?
Yes. Download the .csv file and open it in Excel or Google Sheets. If Excel misreads encoding or delimiters, try semicolon delimiter for European locales, or paste tab-delimited output directly into a spreadsheet.
How are nested JSON objects handled?
Nested objects and arrays are converted to JSON strings in a single cell. For example, {"address": {"city": "London"}} produces a column with the value {"city":"London"}. Flatten deeply nested data before conversion if you need separate columns.
Is there a row or column limit?
No server-side limit. Conversion runs in your browser. Very large datasets (100,000+ rows) may be slow on older devices. For massive exports, consider streaming tools or database-native export.