Convert JSON to TypeScript, Markdown, and other developer formats — processed privately in your browser.
Your favourites
Recently used
- JSON to TypeScript ConverterTurn a JSON example into TypeScript interfaces — nested objects become named interfaces, arrays of objects merge with optional keys, and mixed types become unions.
- JSON to Markdown Table ConverterConvert a JSON array of objects into a Markdown table — one row per element, columns from the union of keys, pipes and line breaks escaped.
- JSON to YAML ConverterConvert JSON to clean YAML — for Kubernetes manifests, CI pipelines, docker-compose and config files.
- YAML to JSON ConverterConvert YAML to JSON with a safe parser — anchors and merge keys expanded, no code execution, errors reported with line and column.
- JSON to XML ConverterConvert JSON to XML — objects become elements, arrays repeat a singularized child element, and special characters are escaped.
- XML to JSON ConverterConvert XML to JSON — attributes become "@" keys, repeated elements become arrays, and numeric or boolean text optionally becomes real types.
- JSON to CSV ConverterConvert a JSON array of objects to CSV for Excel and Google Sheets — RFC 4180 quoting, nested objects flattened into dotted columns, comma/semicolon/tab delimiters.
- JSON to JavaScript Object ConverterConvert JSON into a JavaScript object literal — identifier keys unquoted, your choice of quote style, optional trailing commas and declaration prefix.
- JSON to PHP Array ConverterConvert JSON into a PHP array literal — short [] or array() syntax, single-quoted escaped strings, the exact structure json_decode($json, true) would produce.
- JSON to Python Dictionary ConverterConvert JSON into a Python dict literal — true/false/null become True/False/None, strings are escaped for Python, and the result is valid Python 3 as-is.
- JSON to Java Class ConverterGenerate Java classes from a JSON example — POJOs with getters/setters, Java 16+ records, or Lombok style.
- JSON to C# Class ConverterGenerate C# classes or records from a JSON example — PascalCase properties with [JsonPropertyName] attributes for System.Text.Json, nullable types for partially-present fields.
- JSON to SQL Insert ConverterConvert a JSON array of objects into SQL INSERT statements — MySQL, PostgreSQL/ANSI or SQL Server quoting, multi-row or per-row, nested objects flattened into columns.
- JSON to HTML Table ConverterConvert a JSON array of objects into a semantic HTML table — thead/tbody, scoped headers, optional caption and CSS class, with every value HTML-escaped for safety.
- JSON to URL Parameters ConverterConvert a JSON object into a URL query string — percent-encoded, with nested keys in bracket (PHP/Rails) or dot style, and null handling you control.
Frequently asked questions
Which conversions are supported?
JSON to and from CSV, YAML and XML, plus one-way conversion to SQL inserts, TypeScript, class definitions and Markdown tables. The direction matters: some conversions cannot be reversed without losing information.
Why can JSON not always become CSV?
CSV is a flat grid; JSON is a tree. A nested object or an array inside a record has no column to live in, so it must be flattened into dotted column names or dropped. The converter flattens and tells you what it did rather than silently discarding.
Does converting lose data?
It can, and the tools say when. YAML and JSON map cleanly onto each other. XML has attributes and comments with no JSON equivalent. CSV has no types at all, so numbers and booleans come back as strings unless you convert them yourself.
How are dates handled?
As whatever they were in the source. JSON has no date type, so dates are strings by convention — usually ISO 8601. Converters preserve the string rather than reinterpreting it, because guessing a date format is how days and months get swapped.
What happens to a CSV with inconsistent rows?
Rows with more or fewer fields than the header are reported rather than quietly padded, since a shifted column is the kind of error that survives all the way into a database. You decide whether to fix the source or accept the mapping.
Can I convert a large file?
Everything runs in your browser, so the limit is your device rather than an upload cap. Files of a few megabytes convert in well under a second; much larger ones are warned about before they can make the tab unresponsive.
Is my data uploaded?
No. Conversion happens locally and nothing you paste is transmitted, which is the practical reason to use these rather than a service that processes your export on its own servers.
The same data, the shape you need
Data rarely stays in one format. The response you fetched as JSON needs to become TypeScript interfaces in your codebase, a table in your README, a class in your backend language. Converters here do those translations mechanically and honestly: what the input proves is converted; what it cannot prove (like optionality from a single sample) is flagged instead of guessed.
Growing set
TypeScript and Markdown tables are live now; YAML, XML, CSV and per-language class generators are planned next in this cluster. Each converter documents its edge cases — escaping rules, precision limits, naming conventions — on its own page, so you know exactly what you will get before you paste.
