TOML and YAML serve the same purpose — human-editable config files — but different ecosystems have settled on different defaults. Rust and Python tooling favours TOML; Kubernetes, Ansible, and most CI systems use YAML. Moving between them by hand is tedious and error-prone, especially for files with nested tables, arrays of tables, and datetime values.
This converter parses TOML and re-serializes to YAML entirely in your browser using js-yaml. Config files containing passwords, tokens, or internal service addresses are never sent anywhere.
The TOML input is parsed into a JavaScript object using a TOML v1.0-compliant parser. That object is then serialized to YAML using js-yaml's dump function with block style. TOML tables become YAML mappings, and TOML arrays of tables ([[double brackets]]) become YAML sequences of mappings.
TOML's four datetime types are all output as ISO 8601 strings. TOML dotted keys and inline tables are normalized into nested YAML mappings. Multi-line strings are preserved using YAML's literal block scalar style where possible.