Conversion policy protects exact values
JSON has no native TOML date-time, NaN, or infinity values. Large integers can also exceed JavaScript's exact numeric range, so unsupported values produce explicit diagnostics.
Translate TOML tables, arrays, and compatible scalars into strict JSON while exposing representation gaps instead of silently changing values.
Inputs are limited to 1 MiB and stay in this browser tab.
Nothing is placed in a URL, account, or remote log.
Strict, bounded, local processing
TOML and JSON do not share an identical type system. Date-times, 64-bit integers, infinity, and NaN must remain visible at the conversion boundary.
JSON has no native TOML date-time, NaN, or infinity values. Large integers can also exceed JavaScript's exact numeric range, so unsupported values produce explicit diagnostics.
TOML comments and table presentation do not appear in JSON. Keep the source when annotations matter to maintainers.