How configuration files are converted
YAML and TOML preserve nested structures and types, while flat formats use paths. Properties and INI use dots and indexes for nesting, and .env uses double underscores.
What happens to value types
Java Properties, INI, and .env have no shared way to store value types. A number such as 8080 and true therefore remain strings after conversion back from those formats. TOML also cannot represent null.
Local processing
Every configuration is converted in your browser and never sent to the DevToolbox server. This matters for files that may contain service addresses or other sensitive settings.
Frequently asked questions
Which formats and directions are supported?
YAML, TOML, Java Properties, INI, and .env are available. Choose any two different formats for a total of 20 directions.
How is nesting represented in .env?
Path segments use double underscores: application.server.port becomes application__server__port. Key casing is preserved, and array indexes are separate numeric segments.
Why do Properties, INI, and .env values become strings?
These formats do not define reliable shared value typing. The converter avoids guessing so strings such as 001, true, or null do not change unexpectedly.
Can I safely paste secrets?
Processing is local, but check the security of your device, browser, and installed extensions before pasting secrets.