Paste a TOML configuration to format its supported structures. Review the output: comments are removed and the simplified parser does not preserve every TOML type.
Runs locally in your browserPaste a TOML configuration, press Format, and the tool rewrites it as one key per line with [section] table headers, shows the same structure as JSON, and reports anything it could not read.
Parsing happens in the page: nothing is uploaded, and a format, copy and clear cycle issues no network requests at all, so the same input can be formatted again offline.
Verified against the page: basic tables, dotted keys, arrays that span several lines, arrays of tables ([[products]]), inline tables — also inside arrays — basic and literal strings, integers in decimal, hex, octal or binary form with underscore separators, floats, booleans, and dates or timestamps.
The JSON view mirrors the same structure: TOML numbers become JSON numbers, booleans stay booleans and tables become nested objects, so the formatted text and the JSON panel can be compared line by line.
Multi-line strings ("""), inf and nan, and time-only values such as 07:32:00 are rejected with an error instead of being guessed at. Comments are dropped from the formatted output, because a comment cannot be rebuilt from the parsed structure.
Timestamps come back as quoted strings — JSON has no date type — and an array of tables is rewritten as an inline-table array such as products = [{ name = "a" }, { name = "b" }], which is valid TOML for the same value.
A missing value, an unreadable value or a [table] header defined twice stops the run with a message that names the line, and the output panels are cleared so an older result is never left looking current. The messages follow the page language.
Everything runs in the browser, and pressing Format with an empty box shows a warning instead of a success status. Large configuration files are handled the same way, since the work is plain text parsing with no request to wait for.