JSON to TOML Converter

No. The conversion runs entirely in your browser with JavaScript, so your JSON never touches a server. That makes it safe for config files that contain hostnames, tokens or other private values.

A TOML document is itself a table, which maps to a JSON object. A bare array or scalar at the root has no valid TOML equivalent, so the converter reports an error asking you to wrap it in an object first.

Each nested object becomes a TOML table with a dotted header, such as [owner] or [server.db]. Plain key and value pairs for the current table are written first, then the table sections follow so the output parses cleanly.

An array of primitive values is written inline, like ports = [8001, 8002]. An array where every item is an object becomes an array of tables using the [[name]] syntax, one block per item. A mixed array of objects and primitives is treated as an inline array instead.

TOML has no null type, so any JSON null is written as an empty string to keep the document valid. If you would rather drop those keys entirely, remove them from the JSON before converting.

Yes. Strings use TOML basic-string escaping for quotes, backslashes, tabs, newlines, form feeds and other control characters, and any code point below 0x20 becomes a \uXXXX escape. Keys that are not simple letters, digits, underscores or hyphens are quoted the same way.

JSON itself cannot hold Infinity or NaN, but if such a value reaches the converter it is written using the TOML spellings inf, -inf and nan rather than being dropped.

Yes. Keys are emitted in the same order they appear in the object, with all inline values for a table printed before its nested tables so no key ends up stranded under the wrong header.

This tool only goes from JSON to TOML. For the reverse direction, or to tidy the JSON first, try a JSON formatter or a dedicated TOML to JSON converter.