Hand off a configuration between TOML and JSON

Choose the direction and actual source

Choose TOML → JSON or JSON → TOML.

Paste text or select one UTF-8 file, each up to 2 MiB. The file takes priority over stale pasted text; its name is limited to 512 UTF-8 bytes. Select the direction explicitly; extensions do not determine it.

• Paste the actual configuration or select the original UTF-8 file.
• Convert and review empty objects, number categories and the report counts.
• Download the converted payload, source-original and conversion-report.json, then validate the configuration in its receiving application.

Read all three deliveries

Use the converted payload for handoff and the original for review. The report records provenance, SHA-256, bytes, BOM, integer/float counts and the resource score. Configuration values are not uploaded.

Check the value model before the receiving application

Integers range from −9007199254740991 through 9007199254740991. TOML integers and JSON tokens without a decimal point or exponent are read as BigInt first; unsafe integers reject the whole conversion.

Decimal/exponent tokens use finite IEEE 754 binary64 and retain the float-versus-integer category. Decimal rounding and underflow can occur: 1.234567890123456789 becomes 1.2345678901234567, and 1e-400 becomes float 0.0. Original number spelling and arbitrary decimal precision are not retained.

JSON null, TOML date/time values, non-finite numbers, floating negative zero, raw JSON −0, duplicate keys, malformed grammar or Unicode reject the whole input. Values are never silently deleted, changed to strings or repaired. Date-looking strings remain strings.

{"integer":1,"float":1.0,"arguments":{}}

Understand nesting and serialization budgets

Count every root, object, array and scalar value once, excluding key strings and parser bookkeeping. The root object is level 1; each nested object or array adds a level and scalars do not.

The serialization work score adds 32 bytes per logical value node, the UTF-8 size of each JSON-quoted key and string value with DEL escaped as \u007f, and each nonroot object’s complete quoted key path with dots between parts. Array elements carry the path without indices. Deep repeated keys can amplify the score despite a short source. It is not exact CPU, heap or allocation bytes.

The report has fixed fields, bounded counts, two 64-character SHA-256 strings and one source name up to 512 UTF-8 bytes. Its maximum escaping stays below 16 KiB, so the 64 KiB report guard is dominated by the field bounds rather than a reachable capacity edge.

Handle refusals, cancellation and recovery

Keep the original. Correct duplicate keys, unsupported values, encoding or grammar; split configurations above the limits. After cancelling, rerun with the same file and direction. Clear the file selection to use pasted input.

An atomic refusal produces no partial delivery and does not list every unsupported value. Confirm that the receiving application supports the emitted TOML syntax and binary64 number semantics.