Convert TOML config files to JSON. Free, private, runs in your browser.
100% private — your files and text never leave your browser. All processing happens locally on your device.
TOML to JSON parses common TOML config structures such as tables, arrays, inline tables, arrays of tables, booleans, numbers, strings, and date-like values in the browser.
JSON has no TOML date type, so date-like TOML values are preserved as strings. That keeps output portable and avoids pretending the conversion can preserve a richer runtime type.
Phase 4 uses a focused local parser instead of adding a package. It covers common config files, while rare TOML edge cases should be checked against your application parser.
No. TOML is parsed in your browser and converted to JSON locally.
JSON has no date type, so TOML date-like values are preserved as strings.
Common arrays, nested tables, inline tables, and arrays of tables are supported for practical config conversion.
The parser reports the line or value it could not understand so you can edit and retry.
No. Phase 4 uses a small local parser to avoid adding a new package for common conversion cases.