Private TOML to JSON converter
TOML to JSON Converter
jc-rs converts a TOML configuration file to JSON without flattening tables or guessing scalar types. The resulting object is ready for inspection or for tools that already consume JSON.
toml--tomlv1.0.0
Try the real parser
Paste input on the left. The same Rust parser that ships in the binary runs locally in this page and writes its JSON on the right.
{ "enabled": true, "server": { "host": "127.0.0.1", "port": 8080 }, "title": "jc-rs" }
Hover over a JSON value, or focus the JSON pane and use the Left and Right arrow keys, to trace it to the input. Parsing runs inside this tab in WebAssembly. Pasted text and opened files are not uploaded. If site analytics is enabled, it may receive page-level visit data such as the URL, title, and referrer; text in this editor is never included.
Accepted input
One non-empty TOML document whose top level is a table. Standard strings, integers, floats, booleans, datetimes, arrays, inline tables, named tables, and arrays of tables are handled by the TOML parser.
What the JSON contains
- Strings, integers, floats, booleans, arrays, and nested tables retain their corresponding JSON shapes.
- A datetime stored under a table key produces a Unix timestamp plus a sibling key ending in
_iso. - Datetime values inside arrays remain ISO strings, matching jc's established output schema.
- Invalid TOML stops with a parse error instead of returning a partial object.
What you can do here
- Convert a TOML configuration file to JSON
- Inspect nested TOML tables as JSON objects
- Check how TOML datetime values appear in jc-rs output
Use the same parser in a shell
$ cat config.toml | jc-rs --tomlThe browser tool is for inspection. The CLI form is the useful one in scripts, pipes, containers, and repeatable checks.
Continue with the parsed JSON
Fixture coverage
Magic syntax
Source: crates/jc-rs-parsers/src/format/toml.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare