INI ↔ JSON
ClientConvert between INI-style config text and JSON in your tab—paste on either side, format, and copy. A small JSON example is pre-filled so you can try JSON → INI immediately.
Learn more: JSON and INI
Move between flat INI-style config text and JSON when older apps, games, or Windows tooling still expect `.ini` files while APIs and tests use JSON.
What INI is here
Classic INI files use `key=value` lines and `[section]` headers. Nesting is limited compared to JSON; this tool maps nested JSON objects to dotted section names the same way common INI serializers do.
Limits
INI has no standard for every JSON type—arrays repeat keys or use bracket syntax depending on the parser. After conversion, verify numbers and booleans match what your target program expects.
JSON & INI
?
JSON → INI uses JSON.parse then an INI serializer (same algorithm as the common ini package). Root JSON arrays are wrapped under a root key. INI → JSON uses ini.parse then JSON.stringify.
INI values are mostly strings; booleans may round-trip as true/false. Nested JSON maps become dotted sections—spot-check legacy configs after conversion.
72 characters total
Sample JSON is pre-filled—click JSON → INI to fill the right panel. Parsing runs in your browser.
Common use cases
- Migrate legacy `.ini` settings to JSON for APIs or tests, or the reverse for older tooling.
- Compare the same logical config side by side when one system speaks INI and another JSON.
- Normalize minified or hand-edited INI after pasting from a terminal or editor.
- Translate a small Windows-style `.ini` snippet into JSON for documentation or fixtures.
Common mistakes to avoid
Expecting INI to preserve JSON number types
Many INI parsers treat values as strings; after INI → JSON, numbers may arrive as strings unless the parser coerced them.
Assuming section and key rules match every ecosystem
Duplicate keys, nested sections, and escape rules vary. Align with the loader that will read the file in production.
Confusing this with TOML or env files
INI is flatter and less structured than TOML. For hierarchical typed config, compare with the TOML ↔ JSON tool after you know your format.
FAQ
Are files uploaded?
No. Conversion runs in your browser.
Does this expand environment variables or includes?
No. You paste plain INI text—interpolation and `#include`-style features are not applied here.
Can I validate semantics against an app schema?
No. This tool only parses structure. Use your runtime’s config tests or JSON Schema after INI → JSON when you need business rules.
Common search terms
Phrases people search for that match this tool. See the full long-tail keyword index.
- ini to json converter online
- json to ini file converter
- convert ini to json in browser
- config ini to json
More tools
Related utilities you can open in another tab—mostly client-side.
TOML ↔ JSON
ClientTOML to JSON and JSON to TOML online—format, validate, convert locally.
JSON ↔ Properties
ClientJava-style .properties lines ↔ nested JSON—comments skipped, client-side.
.env lines → JSON
ClientParse KEY=value text into nested JSON—dot keys, coercion, local only.
JSON formatter
ClientJSON format online: pretty-print, minify, validate, escape, download .json.