20 tools
Format source code and move structured data between common developer formats.
Choose a conversion below. Every tool includes an instant result, an example and a short explanation.
A readable representation makes a difference when you inspect an API payload, edit a stylesheet, compare an XML response or document a small SQL query. These tools keep the original data visible beside a transformed result. Formatting changes layout, while conversions change the representation or data model. Choose the operation that matches the material you actually have.
The processors run locally in your browser. Several formats are much larger than any lightweight online editor can implement completely. Each page explains its accepted subset and the cases that require a dedicated parser, compiler or production build tool. In particular, a formatted result is not proof that a script, query or document is safe to execute.
For structured data, check types and field names after conversion. CSV cells are text, XML distinguishes attributes and element content, and YAML supports features beyond the JSON-compatible subset used here. Keep a copy of the source when exchanging data with another system, then test the output in the application that will consume it.
These tools aim to make supported syntax easier to read or more compact, but a formatter is not a compiler or full language parser. Some tools deliberately reject constructs outside their documented subset. Check the output in the destination parser, run your normal tests and review a diff before replacing production code.
Each format has a different data model. CSV is tabular, XML has elements and attributes, and YAML offers syntax beyond the subset supported here. The tools document their mapping and reject some unsupported structures. Convert a representative sample first, compare meaningful values on a round trip, and keep the original file.