Convert TOML Configuration to JSON
Paste TOML content or upload a .toml file and the parser processes it against the full TOML v1.0 spec — tables ([section]), arrays of tables ([[items]]), inline tables ({k = v}), multi-line strings, and all scalar types — then serialises the resulting object tree as valid JSON with proper indentation.
Use this when you need to consume a Cargo.toml, pyproject.toml, or other TOML config from a tool that only speaks JSON; build a programmatic pipeline over a TOML-based config; diff two TOML files in a format that semantic JSON diff tools can read; or quickly inspect the data shape a TOML file produces before writing code to consume it.
Typed values round-trip correctly: integers stay JSON numbers without precision loss for safe ranges, floats keep their fractional form, booleans map directly, and dates and datetimes are serialised as ISO 8601 strings that downstream JavaScript can parse with Date. Dotted keys and nested tables are resolved into proper nested objects rather than flat keys, and syntax errors surface a line-and-column message pointing to the specific problem.
Parsing runs locally in the browser — the TOML document never reaches a server, which matters for configs that contain credentials or hostnames.
About TOML to JSON conversion
Parse TOML configuration files and convert them to JSON. Supports all TOML features including tables, arrays of tables, inline tables, and typed values.
- Full TOML v1.0 support
- Tables and arrays of tables mapped to JSON objects
- Typed values preserved (strings, integers, floats, booleans, dates)
- Clear error messages for invalid TOML syntax
100% client-side. Your inputs never leave your browser. Ads via AdSense (consent required).
Frequently asked questions
How do I convert TOML to JSON?
Paste a TOML document (Cargo.toml, pyproject.toml, Hugo config) and the converter parses it per the TOML 1.0 spec and emits equivalent JSON. Tables become nested objects, array-of-tables ([[section]]) become JSON arrays of objects, and scalar types (strings, numbers, booleans, date-times) convert to their JSON counterparts. Inline tables and inline arrays work identically to their block-form equivalents.
Is the TOML to JSON converter free?
Yes, completely free with no signup or usage cap. JSONCraft is fully free across every tool — formatter, diff, converters, viewer. Use this converter whenever you need to read a TOML config from a JavaScript tool, feed pyproject.toml metadata to a schema validator, or normalize mixed-config repos into a single JSON view.
Does the converter upload my TOML?
No. The TOML parser runs entirely in your browser. Nothing is sent to a server — relevant because TOML configs often contain build settings, deploy targets or registry credentials. You can convert sensitive files safely; there's no history, no account and no logging.
Does it preserve TOML date-time literals?
TOML has native date-time, local date, local time and local date-time types — richer than JSON, which has only strings. The converter emits them as ISO 8601 strings, which is the de facto JSON convention and round-trips cleanly through the JSON to TOML converter. If your downstream needs a JavaScript Date, you'll need to parse the string there, but no information is lost.
What TOML features may not round-trip to JSON?
Comments and original formatting (key order in inline tables, literal versus basic strings) are not preserved — JSON has neither. Array-of-tables versus inline tables distinction collapses in JSON (both become arrays of objects). Numeric precision is preserved for integers up to 2^53 (JSON's safe range); larger TOML integers become strings to avoid silent truncation.