Config Translator
Convert config files between YAML, JSON, TOML and XML, and find syntax errors with their exact line.
- Never uploaded
- Works offline
- Free, no sign-up
Processed on this device. Nothing is sent to a server.
How to use the Config Translator
- Step 1Paste your fileThe format is detected automatically.
- Step 2Pick the outputJSON, YAML, TOML or XML, with 2- or 4-space indent.
- Step 3Fix errorsProblems are shown with the line and column.
Converting between config formats
JSON, YAML and TOML describe the same kinds of data, so most files convert cleanly. YAML is a superset of JSON and adds comments and less punctuation; TOML is popular for app settings (Cargo, pyproject, Hugo); JSON is what most APIs and tools read.
A few things don’t carry over. Comments are lost in every conversion, because the formats store them differently. TOML has no null, so a null value is reported instead of being dropped silently. XML has attributes and a single root element, so attributes become keys starting with @, and data without a single root is wrapped in <root>.
Choose the same format for input and output to reformat a file with consistent indentation, which also checks that it parses.
Questions
Are my config files uploaded?
No. Parsing and conversion happen in your browser, so files with passwords, tokens or internal hostnames stay on your device.
Why did my comments disappear?
Converting reads the data and writes it in a new format. Comments aren’t part of the data, so no converter can carry them across reliably. Keep the original file if the comments matter.
Why does YAML “yes” or “on” stay a string?
The converter uses YAML 1.2, where only true and false are booleans. YAML 1.1 (used by older tools) also treated yes, no, on and off as booleans, which caused well-known bugs such as the country code NO turning into false.
Is the XML parser safe to use on untrusted files?
Yes. It doesn’t fetch external entities or DTDs, and entity-expansion attacks (“billion laughs”) are not expanded.