Data Format Converter
These formats all describe structured data, but they disagree about shape. JSON, XML and YAML represent hierarchies; CSV and TSV represent a single flat table. Converting between the two groups therefore always involves a decision about what happens to nesting.
FileTools360 makes that decision explicit and predictable rather than silently dropping fields.
Most used data converters
All data conversions
17 supported conversions. Every one is a working converter, not a placeholder.
Data formats explained
JavaScript Object Notation
.json
The default data interchange format for APIs.
Best for: APIs · Configuration · Structured records
Extensible Markup Language
.xml
Verbose but strict hierarchical markup.
Best for: Enterprise integrations · Feeds · Document schemas
YAML Ain't Markup Language
.yaml, .yml
Indentation-based config format that humans actually read.
Best for: CI pipelines · Kubernetes · App configuration
Hierarchical and tabular data
JSON, XML and YAML can nest arbitrarily: an object inside an array inside an object. CSV has rows and columns and nothing else.
Flattening turns nested keys into dotted column names, so an address object becomes address.city and address.zip. It is reversible by eye and predictable, but irregular data produces a sparse table with many empty cells — which is a sign the data probably should not be a table at all.
Choosing between JSON, XML and YAML
JSON is the default for APIs: compact, unambiguous, and natively supported everywhere. Its weaknesses are verbosity for large tables and the absence of comments.
YAML is for configuration a human will edit. It supports comments and reads cleanly, at the cost of indentation sensitivity and some famously surprising type coercion.
XML is heavier but supports schema validation and namespaces, which is why it persists in enterprise integrations and document formats.
FAQ