About AG Format
A conversion hub for moving between four data formats on a single screen
AG Format is an online tool for converting between the four data formats JSON, YAML, XML, and CSV. Just choose a source format and a target format, and it handles all 12 conversion directions in real time. It lets you finish, on a single screen, the familiar chore of "reworking data because the formats don't match" that so often comes up in development and data work.
Key features: source/target format selection (switchboard), a two-panel side-by-side real-time conversion, source ↔ target swapping (round-trip), line-level error reporting, indentation and key-sorting options, CSV delimiter and header options, copying and downloading the result, and filling in a sample. It automatically handles the fine-grained rules of YAML, CSV, and XML (quote escaping, repeated elements, attributes).
Every conversion runs entirely inside the visitor's browser. The data you enter is never sent to or stored on any server, so you can safely handle sensitive content such as configuration files, API responses, and business data. No sign-up or installation is required.
Because tabular formats like CSV cannot express hierarchical structure, when you convert deeply nested JSON to CSV the nested values are stored inside cells as JSON strings. XML↔JSON conversion uses a convention that maps attributes to @name, text to #text, and repeated elements to arrays. These conversion rules are explained in detail in each format guide.
Frequently Asked Questions
Is the data I enter sent to a server?
No. Every conversion runs entirely inside the visitor's browser, and what you enter is never sent to or stored on any server.
Which formats are supported?
Four formats are supported — JSON, YAML, XML, and CSV — and all 12 conversion directions between them are handled.
What happens when I convert nested JSON to CSV?
CSV is tabular, so it cannot hold a hierarchical structure. Nested object and array values are saved inside cells as JSON strings to prevent data loss.
What are the XML conversion rules?
Attributes map to @name keys, an element's text maps to a #text key, and repeated elements with the same name map to arrays. For JSON→XML, if the top level has a single key, that key is used as the root element.
If a conversion error occurs, can I tell what went wrong?
Yes. If parsing the input fails, the input panel shows which line failed and why.