Convert TOML to JSON
Convert TOML to JSON free in your browser. No upload, no signup, no watermark. Files stay on your device.
drop a .toml file
or click to browse
related
more toml & json
see all data & code converters →guide
how to convert toml to json
Drop your TOML file
Drag your TOML file into the drop zone above, or click the box to pick a file from your computer or phone. The browser reads the file directly — nothing uploads.
Click Convert
The page runs smol-toml on your device to decode the Tom's Obvious Minimal Language and encode it as JavaScript Object Notation. Most conversions finish in a few seconds; large or codec-heavy files (RAW, video) can take longer.
Download the JSON file
When the conversion finishes, the JSON file is ready to download. Save it anywhere on your device.
FAQ
common questions
Why convert TOML to JSON?
Two main reasons: (a) loading TOML configuration into a program written in a language that doesn't have a built-in TOML parser (most languages have JSON, fewer have TOML); (b) embedding TOML config in a JavaScript / TypeScript build pipeline that imports JSON natively. JSON is the more universal interchange format; TOML is the human-friendly config form.
How does TOML structure map to JSON?
TOML tables (`[section]`) become JSON objects; nested tables (`[a.b.c]`) become nested objects; arrays become JSON arrays; strings, numbers, booleans translate directly. TOML's native date / time types serialise as ISO 8601 strings in JSON since JSON has no date type.
What happens to my TOML comments?
They're dropped. JSON doesn't support comments at all — the standard forbids them. If documentation in your TOML matters, keep TOML as the source of truth and treat JSON as a derived format that gets regenerated when TOML changes.
Will TOML's typed values (dates, times) round-trip cleanly?
Dates and times become ISO 8601 strings in JSON (`'2024-01-15'` or `'2024-01-15T10:30:00Z'`). Parsing them back to native date types requires explicit handling on the consumer side — JSON gives you strings and the consumer interprets. If date / time handling matters, document the expected format or use a schema.
Will the JSON be larger?
Slightly. TOML's section headers are concise; JSON's bracket / comma syntax adds a few extra characters per nested level. For typical config files the difference is minor — most converted files end up within 10–20% of the original TOML size.