A TOML file groups settings under headings such as [server]. JSON groups the same data with braces { }. TOML to JSON lets you see the values as JSON without guessing where a heading ends.

Read one tiny config

Paste this into TOML:

title = "Demo"
[server]
port = 8080

In JSON, look for "title": "Demo" and a "server" object containing "port": 8080. The number 8080 has no quotes in the result, so it is a number, not text. Use Copy or Download if another program needs the JSON.

Before replacing a config

This tool converts values, not the program’s rules for what settings are allowed. It also cannot keep TOML comments in JSON because standard JSON has no comment syntax. If you get a parsing error, check quotation marks and table headings in the TOML first. Keep the original file when the comments matter.

Where your input goes

Processing runs in your browser. The tool does not upload your input to ilham.dev.

For more background, read Working With Structured Data.

Questions you might have

How are TOML dates represented?
JSON has no built-in date type. If your TOML contains a date or time, inspect the JSON output and confirm the receiving program expects its string form; conversion alone does not tell that program how to interpret it.