What happens to nested objects?

With flatten enabled (the default), nested objects are expanded using dot-notation keys. For example, {address: {city: 'London'}} becomes a column named 'address.city'. With flatten disabled, the nested object is JSON-stringified and placed in a single cell.

What if my CSV values contain commas or newlines?

The converter follows RFC 4180: values containing the delimiter, double quotes, or newlines are enclosed in double quotes, and any double quotes within the value are escaped as two consecutive double quotes. The CSV-to-JSON parser handles this correctly.

How does the tool split compound words like 'innerHTML' or 'XMLParser'?

camelCase splitting uses two regex passes: first it inserts a space before any lowercase-to-uppercase transition (innerHTML → inner Html), then before any sequence of uppercase letters followed by an uppercase-then-lowercase transition (XMLParser → XML Parser). Both passes together correctly split 'XMLParser' into ['xml', 'parser'] and 'innerHTML' into ['inner', 'html'].

Does the tool preserve acronyms like 'URL' or 'HTTP'?

Acronyms are lowercased as part of tokenisation and then recased according to the target convention. In camelCase, 'parseURL' becomes 'parseUrl'; in PascalCase it becomes 'ParseUrl'. If your codebase uses a style guide that keeps acronyms uppercase (e.g. 'parseURL'), apply the conversion and then manually restore the acronym casing.

Tool comparison

JSON to CSV Converter vs Text Case Converter

JSON to CSV Converter (formatting) and Text Case Converter (text) come from different categories but appear together in developer workflows. This guide explains what each does and when to reach for one over the other.

Bottom line

JSON to CSV converts a JSON array of objects into rows and columns for spreadsheet import. Text Case Converter changes capitalisation style of plain-text strings. Use JSON to CSV when exporting structured data; use Text Case Converter when normalising field names or labels before the export.

What each tool does

JSON to CSV Converter

JSON (JavaScript Object Notation) and CSV (Comma-Separated Values) are the two most common formats for exchanging tabular data. JSON is the native format for REST APIs, NoSQL databases, and JavaScript applications. CSV is the native format for spreadsheet tools like Excel and Google Sheets, SQL import utilities, data pipelines, and business reporting tools. Converting between them is one of the most frequent data engineering tasks: you might export an API response to a spreadsheet for analysis, import a CSV upload into a database, or transform a data warehouse export into JSON for an API. This tool converts a JSON array of objects to a CSV with a header row derived from the object keys, or parses a CSV back to a JSON array. Nested objects are optionally flattened using dot-notation keys (address.city) so the entire structure fits into a flat table.

Open JSON to CSV Converter →

Text Case Converter

Naming conventions define how words are combined into identifiers in code, configuration files, APIs, and databases. camelCase (myVariable) is the standard in JavaScript and Java. snake_case (my_variable) is the norm in Python, Ruby, and SQL. kebab-case (my-variable) is used in CSS, HTML attributes, and URL slugs. PascalCase (MyVariable) is used for class names and React components across most languages. SCREAMING_SNAKE_CASE (MY_VARIABLE) marks constants. Different tools, frameworks, and languages enforce different conventions, so converting between them is a constant need when writing glue code, generating API clients, or adapting data from one system to another. This tool splits any identifier or phrase into its component words — intelligently handling camelCase boundaries, underscores, hyphens, and dots — then reassembles them in the target convention.

Open Text Case Converter →

Side-by-side comparison

Feature	JSON to CSV Converter	Text Case Converter
Category	formatting	text
Primary purpose	Convert a JSON array of objects to CSV, or parse CSV back to JSON.	Convert text between camelCase, snake_case, kebab-case, PascalCase, and 7 other naming conventions.
Inputs	input, mode, delimiter, flatten	input, to
Outputs	output, row_count, column_count, columns, mode, error	output, tokens, from_detected

When to use each

Use JSON to CSV Converter when…

How to convert a JSON API response to a CSV spreadsheet

Export API data to a CSV file for analysis in Excel or Google Sheets.

How to convert a CSV file to JSON

Parse a CSV export from a database or spreadsheet into a JSON array for use in code.

Use Text Case Converter when…

How to convert camelCase to snake_case

Convert JavaScript variable names to Python or SQL naming conventions.

How to convert snake_case to camelCase

Convert Python or database identifiers to JavaScript naming conventions.

Frequently asked questions

What happens to nested objects?: With flatten enabled (the default), nested objects are expanded using dot-notation keys. For example, {address: {city: 'London'}} becomes a column named 'address.city'. With flatten disabled, the nested object is JSON-stringified and placed in a single cell.
What if my CSV values contain commas or newlines?: The converter follows RFC 4180: values containing the delimiter, double quotes, or newlines are enclosed in double quotes, and any double quotes within the value are escaped as two consecutive double quotes. The CSV-to-JSON parser handles this correctly.
How does the tool split compound words like 'innerHTML' or 'XMLParser'?: camelCase splitting uses two regex passes: first it inserts a space before any lowercase-to-uppercase transition (innerHTML → inner Html), then before any sequence of uppercase letters followed by an uppercase-then-lowercase transition (XMLParser → XML Parser). Both passes together correctly split 'XMLParser' into ['xml', 'parser'] and 'innerHTML' into ['inner', 'html'].
Does the tool preserve acronyms like 'URL' or 'HTTP'?: Acronyms are lowercased as part of tokenisation and then recased according to the target convention. In camelCase, 'parseURL' becomes 'parseUrl'; in PascalCase it becomes 'ParseUrl'. If your codebase uses a style guide that keeps acronyms uppercase (e.g. 'parseURL'), apply the conversion and then manually restore the acronym casing.