A narrow shape prevents invented conventions
Arbitrary JSON does not define section names, dotted-key flattening, repeated values, or comment placement. Unsupported shapes fail instead of being stringified silently.
Serialize one explicit section-map contract rather than guessing how arbitrary nested JSON should flatten.
Inputs are limited to 1 MiB and stay in this browser tab.
Nothing is placed in a URL, account, or remote log.
Bounded, explicit, and local
The accepted JSON shape is intentionally narrow: top-level members become sections and their scalar members become INI keys. Arrays, deeper objects, and ambiguous names are rejected with paths.
Arbitrary JSON does not define section names, dotted-key flattening, repeated values, or comment placement. Unsupported shapes fail instead of being stringified silently.
The serializer produces Tool Swim's conservative profile. A Python, Git, PHP, Windows, or product parser may apply different rules.