Configuration tools

Convert configuration formats without hand-editing them.

INI to JSON

Convert simple INI sections and string values into explicit JSON locally.

JSON to XML

Create clean XML from a documented JSON mapping for elements, attributes and text.

JSON to YAML

Turn JSON into clean, portable YAML using a documented safe data subset.

TOML to JSON

Convert standard TOML tables and scalar data to formatted JSON locally.

XML formatter

Validate and pretty-print inert XML without loading external entities or resources.

XML to JSON

Map XML elements, attributes and repeated children into explicit JSON locally.

YAML to JSON

Convert a bounded YAML data subset into formatted JSON entirely in your browser.

YAML validator

Check YAML structure, nesting and safe-subset compatibility locally.

Move between INI, TOML, YAML, XML, and JSON with documented, predictable mappings. Each converter reports what it cannot represent instead of guessing, and the XML tools never resolve external entities.

Parsing happens locally, so configuration that contains tokens or internal hostnames stays on your machine.

Converting between formats

Configuration lives in many formats: YAML for Kubernetes, Docker Compose, and CI pipelines, TOML for Rust and Python projects, INI for legacy applications and PHP, XML for Java and .NET tooling, and JSON almost everywhere else. The converters here move data between JSON and each of those formats, and the YAML validator and XML formatter check structure on their own.

Each converter documents its mapping. XML attributes become @-prefixed keys, INI values stay strings, and TOML dates become strings, because JSON has no date type. Features that cannot be converted faithfully, such as YAML anchors or TOML inline tables, are rejected with a clear message instead of being guessed.

Avoiding classic configuration bugs

The most expensive configuration bugs are silent type changes. In YAML, an unquoted NO can become false, 1.10 becomes the number 1.1, and 010 may become 8. The JSON to YAML converter quotes such values so every parser reads them as strings, and the YAML tools report indentation mistakes with line numbers.

Because parsing happens locally, it is safe to paste files that contain internal hostnames, database URLs, or tokens. XML input is parsed without DTDs or external entities, which rules out XXE attacks by design.