What does converting JSON to CSV actually do?
JSON is the default interchange format of the modern web. It represents data as nested objects and arrays of strings, numbers, booleans and null, and every mainstream language ships a parser for it. Its grammar is deliberately tiny — no comments, no dates, no trailing commas — which makes it fast to parse but strict about syntax. CSV is the lowest common denominator for tabular data: every spreadsheet, database and analytics tool can import it. It has no official type system — everything is text until something interprets it — and no way to express nesting, so hierarchical data has to be flattened before export. Converting JSON to CSV therefore re-encodes the same content under a different set of rules — the parsed structure is walked and re-serialised in the target syntax. Nothing is uploaded: the decode-and-re-encode cycle happens on your own machine.