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
JSON to INI
Write a JSON object as global INI assignments plus one level of named sections with deterministic quoting.
Processed in this browserOne 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.
JSON - one-level config object
No file upload
This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
Original stays unchanged
The converter creates a separately named output. It never writes back into the source file.
Bounded work
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
How JSON to INI works
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.
- 01Choose a valid source
Use strings, numbers, booleans, or null at the root and inside one level of section objects. Null becomes an empty INI value.
- 02Review the conversion choices
Alphabetical order creates stable diffs. Preserve order follows the property order stored in the JSON text.
- 03Inspect the separate result
The result ends in _nirmion_tools.ini. JSON types, null distinctions, comments, and nested data cannot be preserved by generic INI.
WORKED EXAMPLE / REVIEW BEFORE RELYING
JSON to INI: a small review pass
Use a short, non-sensitive sample first. This example shows the checkpoints to apply before moving an authorised dataset into the destination workflow.
- JSONSource
Choose sample.json with a header and two representative, non-sensitive records.
- Review the conversion choices
Keep the documented defaults, convert once, and compare the preview or result count with the JSON sample.
- INIResult
Open the separate INI download and verify two records, field names, nulls, encoding, and destination compatibility.
Useful when
Practical jobs this tool handles
- Prepare simple settings for an INI-based application.
- Create deterministic configuration fixtures.
- Move reviewed flat JSON settings into sectioned text.
Before converting
Check the source and destination rules
- Keep the object to one section level.
- Review null and boolean representation.
- Test the result in a non-production instance first.
Know the boundary
Know what the destination format cannot keep
INI consumers differ. This output uses conservative key=value assignments and does not generate interpolation, duplicate keys, arrays, or application-specific directives.
Quick answers
Questions before you convert
The conversion contract is deliberately explicit.
How are nested objects handled?
Exactly one object level becomes INI sections; deeper objects are rejected.
What happens to null?
It becomes an empty value because generic INI has no null type.
Can keys be sorted?
Yes. Alphabetical mode makes generated files and reviews deterministic.