INI to JSON Converter (and JSON to INI)

Real-world use cases

• Migrate a legacy INI config into a JSON-based app

  You are moving an old service from a config.ini to a Node or Go app that reads JSON. Paste the whole INI here, turn on type inference so port=8080 becomes a real number and ssl=true a real boolean, and copy the JSON straight into config.json. The [section] structure carries over as nested objects, so you keep the same logical grouping without retyping a single key.

• Inspect a .cfg or .conf file as readable JSON

  Some daemons ship dense .conf files where it is hard to see the shape at a glance. Drop the file in, read it as indented JSON, and the sections and keys line up clearly. Because comments are stripped, you see only the live settings, which makes it obvious what is actually configured versus what is commented out.

• Generate an INI file from a JSON template

  A tool you are integrating wants an old-style INI, but your source of truth is JSON. Switch to JSON to INI, paste your object, and get a ready-to-save settings.ini. Values that look numeric but should stay text get quoted automatically, so a zip code or a version string is not silently turned into a number on the next read.

• Diff two configs by normalizing them to JSON first

  Comparing two INI files directly is noisy because spacing, comment order and key order vary. Convert both to JSON with the same options, paste them side by side in your editor, and a structural diff shows only the real differences in values, not formatting churn.

Common pitfalls

• Expecting deep nesting. INI is flat under each section header and goes only one level deep, so a JSON object whose value is itself an object of objects (a then b then c, three levels down) cannot be expressed and the JSON to INI direction will reject it. Restructure to a single level of sections, or use a properties or YAML tool for deeper trees.

• Leaving type inference on when you need strings. With inference on, a zip code 08055 or a phone-like 123456 becomes a number and may drop leading zeros. If a value must stay text, turn inference off, or wrap that value in double quotes so it is always read as a string.

• Assuming arrays survive. Classic INI has no array syntax, so a JSON list value such as the three numbers one, two, three has nowhere to go and the converter throws rather than guessing a comma-joined string. Flatten the list into separate keys or move that part to a JSON-native config.

Privacy