Convert between INI configuration files and JSON. Paste an INI file to get structured JSON,
with an optional toggle to coerce true/false/null and
numbers into native JSON types, or convert JSON into INI for config files. Dotted section
names like [a.b] map to nested objects, and swapping input and output takes one
click. Everything runs locally in your browser. Converting a different config format? Try
YAML ⇄ JSON, TOML ⇄ JSON,
XML ⇄ JSON, or .env ⇄ JSON.
INI ⇄ JSON
Bidirectional conversion between INI and JSON
Output will appear here...Frequently asked questions
Is there an official INI standard this tool follows?
No — INI has never had a formal specification, and different tools disagree on details like comment syntax, quoting, and nested sections. This converter documents its own consistent rules: `;` and `#` start comments (full-line, or inline after a preceding space), values can be wrapped in single or double quotes, and unquoted true/false/null/numbers are coerced to native JSON types when the coercion toggle is on.
How do INI sections map to JSON?
A `[section]` header becomes a nested JSON object, and any keys before the first section land at the root. A dotted section name like `[a.b]` maps to nested objects two levels deep (`{"a":{"b":{...}}}`), which is also how JSON → INI represents an object nested more than one level below the root. If the same section header appears more than once, its keys are merged into one object.
How are arrays handled?
INI has no portable array syntax, so this tool does not invent one. Converting JSON with an array anywhere in it to INI produces a clear error naming the array's location instead of silently guessing at a format (like repeated keys or comma-joined values) that other tools might not agree on.
Does my INI or JSON data leave my browser?
No. Both directions of the conversion run entirely client-side in JavaScript — nothing is uploaded to a server, and there is no signup or account required.
Get weekly dev tools and tips