The converter parses TOML and writes the result as YAML. Tables and inline tables become nested mappings, arrays of tables become YAML sequences of mappings, and indentation can be adjusted from 2 to 8 spaces.
TOML date-like values are parsed and emitted as YAML scalars by the serializer. Comments, blank lines, and original table layout are not preserved, so review hand-maintained configuration files after conversion.
Common questions and answers about this topic.
TOML uses a flat key-value syntax with explicit sections (tables) and strict typing, while YAML uses indentation-based nesting and is more flexible with data types. TOML is common in Rust/Python configs, YAML in Kubernetes and CI/CD pipelines.
Yes, the YAML output indentation is adjustable from 2 to 8 spaces through the formatting options. For YAML files used in Kubernetes or Docker Compose, 2 spaces is the standard convention.
Yes, the sort keys dropdown offers the option to alphabetically arrange all YAML mapping keys (A to Z) or keep the order from your original TOML tables. This sorting recurses into every nested mapping level.
No, the TOML-to-YAML conversion takes place entirely within your browser. Your TOML data is transformed locally via JavaScript and never leaves your device.