JSON to INI
Convert a JSON object into INI configuration format. Top-level scalars stay at the top of the file, nested objects become [section] headers, and one level deeper becomes a dotted [parent.child] section — the convention most INI parsers understand.
How to convert JSON to INI
- Paste a JSON object. INI has no way to represent a top-level array, so the input must be an object.
- Choose whether to write
key = valueor the tighterkey=value— both are widely accepted. - Tick Quote values if any of your strings have significant leading or trailing spaces, or contain
;,#or=. - Check the section layout in the output, then copy or download the
.ini.
How nesting is mapped
- Root scalars — emitted first, above any section header, which is where most parsers expect global settings.
- One level of nesting — becomes
[name]. - Two levels — becomes
[parent.child]. Many parsers (Python'sconfigparseramong them) treat that as a flat section name with a dot in it, which is usually what you want. - Arrays — joined with commas. INI has no array type, so this is a convention, not a standard; check what your parser expects.
- null — written as an empty value.
INI is not a standard
There is no specification for INI. Comment characters (; vs #), whether
duplicate keys accumulate into a list, whether values can span lines, and how quoting works all vary by
implementation. If you control both ends, TOML is the better choice — it is a
real spec, has proper types and arrays, and reads almost identically.
Privacy
Nothing is uploaded. The conversion runs in this tab using your own browser's JavaScript engine — no server sees your data, and the page keeps working with the network disconnected.
FAQ
Can I round-trip JSON → INI → JSON?
Not losslessly. INI has no types, so every value comes back as a string unless the reader guesses — INI → JSON does guess, but a string "8080" and a number 8080 are indistinguishable in the file.
What about deeper than two levels?
Levels beyond the second are flattened into the section body with dotted keys. Deeply nested config is a poor fit for INI; use TOML, YAML or JSON.
Does it work offline?
Yes, entirely.