Step 1 / source
Choose the source
Drop one file here
Choose the one-level json configuration you want to turn into utf-8 ini file.
Checking publication status...LOCAL CONFIG CONVERTER / JSON TO INI
Write a JSON object as global INI assignments plus one level of named sections with deterministic quoting.
Step 1 / source
Choose the one-level json configuration you want to turn into utf-8 ini file.
Checking publication status...This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
The converter creates a separately named output. It never writes back into the source file.
One UTF-8 .json file up to 2 MB. The root must be a non-empty object containing scalar global values and optional one-level scalar section objects; output is limited to 20 MB.
Plain-language method
Nirmion validates one object, writes scalar root properties as global assignments, writes each one-level object under a [section] header, quotes ambiguous text, and rejects arrays or deeper objects instead of flattening them silently.
Use strings, numbers, booleans, or null at the root and inside one level of section objects. Null becomes an empty INI value.
Alphabetical order creates stable diffs. Preserve order follows the property order stored in the JSON text.
The result ends in _nirmion_tools.ini. JSON types, null distinctions, comments, and nested data cannot be preserved by generic INI.
Useful when
Before converting
Know the boundary
INI consumers differ. This output uses conservative key=value assignments and does not generate interpolation, duplicate keys, arrays, or application-specific directives.
Quick answers
The conversion contract is deliberately explicit.
Exactly one object level becomes INI sections; deeper objects are rejected.
It becomes an empty value because generic INI has no null type.
Yes. Alphabetical mode makes generated files and reviews deterministic.