Question 1

What JSON shape does the converter expect?

Accepted Answer

A top-level array of objects: `[{...}, {...}]`. Single objects, scalars, or other shapes return an error explaining what's needed.

Question 2

How are nested objects and arrays handled?

Accepted Answer

They're JSON-stringified into a single cell so the CSV stays a flat rectangle. Downstream code can `JSON.parse` the cell to get the original structure back.

Question 3

What happens when objects have different keys?

Accepted Answer

We collect the union of every object's keys (in first-seen order) as the header row. Objects missing a key produce an empty cell in that column.

Question 4

Will my JSON be uploaded?

Accepted Answer

No. Conversion happens entirely in your browser; the JSON never touches our server.

Question 5

Can I pick a different output delimiter?

Accepted Answer

Yes. Comma, semicolon, tab and pipe are all supported. Tab is downloaded with a `.tsv` extension.

Question 6

Are special characters escaped properly?

Accepted Answer

Yes. Cells containing the delimiter, a quote or a newline are wrapped in `"…"` with embedded quotes doubled (RFC-4180), so re-importing into Excel or Sheets is lossless.

Question 7

Does it preserve key order?

Accepted Answer

Yes — the first object's keys come first, and any additional keys from later objects are appended in the order they appear. JavaScript preserves insertion order for object keys, so this is deterministic.

Question 8

What's the largest JSON file I can convert?

Accepted Answer

There's no fixed cap. Files with hundreds of thousands of objects work fine; the limit is your browser's memory budget.

Question 9

Will scalars or null values appear in the output?

Accepted Answer

Null and undefined become empty cells. Numbers, booleans and strings are written as-is.

Question 10

Why is my output empty?

Accepted Answer

Either the JSON parsed to an empty array (no objects to flatten), or the top-level value isn't an array — the error message will tell you which.