Format Converter · URL Query
Pick a conversion type on the left, paste the source and convert, then copy or download the result
JSON format conversion explained
The converter is JSON-centric and supports nine targets: YAML, XML, CSV, TypeScript, Java, Go, JSON Schema, tables and URL query parameters, with reverse conversion for selected formats. Pick a type and options after entering valid JSON, and switching types keeps your input.
For configuration and documentation, YAML is easier to read and suits layered settings; XML fits legacy systems and structures that need attributes; CSV and tables turn arrays into rows for spreadsheets; URL query parameters help build or read request links.
For code generation, TypeScript interfaces, Java classes and Go structs provide a starting point, while JSON Schema describes field types and validation rules that can be reused in contracts and form checks. Review naming and nullability against your project conventions.
Only YAML, XML and CSV can be parsed back to JSON; the other types are one-way output. Options such as indentation, root node name and field naming style apply immediately and trigger a fresh conversion.
Frequently asked questions
- Can the generated code go straight into production?
- It is a starting point. Check type names, nullable fields and project style before committing, because the tool cannot infer business semantics.
- Why do only some formats support reverse conversion?
- Recovering JSON from TypeScript, Java or Go code requires parsing source structure and types with many ambiguities, so only YAML, XML and CSV are reversible here.
- How are arrays handled during conversion?
- Arrays become list nodes in YAML and XML, rows in CSV and tables, and element collections in TypeScript and Go.