Convert JSON to CSV

JSON to CSV conversion turns structured objects into rows and columns that open cleanly in spreadsheet applications. Each object becomes a row, while its property names become CSV column headers. It is useful for reviewing API responses, preparing imports, sharing data with non-technical collaborators, and moving records into Excel or Google Sheets.

FileGizmo performs the entire conversion inside your browser. Select a .json file or paste JSON text, choose a delimiter and nested-value option, then preview and download the generated CSV. The source data is never uploaded or stored on a processing server.

The converter accepts an array of objects or a single object. Missing properties become empty cells, and values containing commas, quotes, or line breaks are escaped correctly. Nested objects can remain as compact JSON strings or be flattened into dot-separated columns. Choose comma-separated output for most uses, semicolons for regional spreadsheet settings, or tabs when another program expects TSV data.

Tabular conversion works best when the JSON contains similarly shaped records. An array of customer objects, event objects, or product objects maps naturally to rows. A single object becomes one row. When records use different properties, FileGizmo builds the available column set and leaves cells empty where a record lacks a value. Review that shape before importing it into a strict database or reporting template.

Nested data requires a deliberate choice because CSV has no native object or array type. Compact mode keeps a nested value as JSON text inside one escaped cell, preserving structure for a later parser. Flatten mode turns nested object paths into dot-separated headings, which is easier to filter and sort in a spreadsheet. Arrays can still require interpretation; a list stored in one cell is not the same as creating a separate row for each item.

Delimiter selection should match the destination. Comma is the conventional CSV separator, semicolon is common in locales that use decimal commas, and tab output can avoid conflicts in text-heavy fields. Proper quoting protects embedded delimiters and line breaks, but an importing application must also be configured for the same delimiter and text encoding. FileGizmo writes Unicode text so names and non-Latin scripts can remain intact.

Before download, inspect headings, a few complete records, missing values, and nested examples. Spreadsheet programs may automatically reinterpret long identifiers, dates, or values beginning with = after the CSV is opened. CSV itself has no type metadata. Import sensitive identifiers through the spreadsheet’s text-import controls, and treat untrusted formula-like content cautiously.

Parsing and serialization happen in your browser. API responses can contain credentials, customer attributes, or internal operational details, so local conversion avoids creating another processing-server copy. The resulting CSV is easier to share and therefore easier to leak; store and distribute it according to the sensitivity of the source JSON.