Translate YAML configuration into TOML with optional indentation and key sorting.
Translate YAML configuration into TOML with optional indentation and key sorting. Translate YAML configuration into TOML with optional indentation and key sorting.
Both YAML and TOML aim to be human-readable configuration formats. They overlap heavily on the data they can represent (mappings, sequences, scalars), but they differ in syntax and in a few corner cases. YAML supports tags, anchors, and multi-line scalars; TOML distinguishes between inline tables and array-of-tables, and treats dates as a first-class type.
A YAML-to-TOML converter is most useful when migrating a config
file from one tool's preferred format to another's: for example,
moving a Kubernetes manifest into a pyproject.toml snippet, or
re-expressing an Ansible inventory in a Cargo [dependencies]
table.
Mappings (key: value in YAML) become TOML tables or key/value
pairs depending on context. Sequences become inline arrays or
[[array.of.tables]] headers. Scalars are preserved as long as
they map cleanly: strings, integers, floats, booleans, and ISO
dates.
YAML anchors and aliases are flattened during parsing; the
converted TOML contains the concrete value at every alias site,
which is what most consumers want. YAML !!binary tags are not
preserved because TOML has no equivalent. Comments are dropped on
purpose -- neither format guarantees round-trip preservation.
Before committing the converted TOML, run your project's TOML linter (taplo, toml-check, etc.). The converter only translates syntax, not style; the linter catches quoting, indentation, and key-order issues the converter cannot detect.