Convert YAML to TOML
Turn YAML into a TOML config file.
About this converter
The usual reason is moving a project between ecosystems: the configuration exists in YAML and the tool that has to read it wants TOML.
The two formats want different things. YAML is comfortable nested arbitrarily deep; TOML is at its best two or three levels in, because each level lengthens the section header above the values. A deeply nested YAML file converts correctly and reads worse than it did.
A YAML document that is a bare list cannot become TOML at all — a TOML file starts with a table. Wrap it in a named key first. Nulls are dropped, because TOML deliberately has no null.
Frequently asked questions
Why will my list not convert?
A TOML document has to begin with a table, and there is no syntax for a file that is only a list. Give it a name — wrap it as items: [ … ] — and it converts into [[items]] blocks.
Where did my null values go?
TOML has no null, by design. Keys with a null value are dropped rather than written as empty strings, since an empty string means something different and guessing between them would be worse than omitting the key.
Does what I paste get sent anywhere?
No. The conversion runs in your browser, on your own machine — which is why the result appears as you type. Nothing is uploaded and nothing is logged. That matters for this kind of tool in particular: config files and API responses are exactly the things that carry keys, hostnames and customer data.