INI / Properties to JSON Converter

Configuration files in INI and Java properties format are still everywhere: legacy applications, game servers, desktop software and build tooling all store settings as simple key and value pairs grouped under section headers. JSON, on the other hand, is the format modern APIs, JavaScript applications and cloud services expect. Moving settings between the two by hand is slow and error prone, because a missed bracket or a mistyped key can silently change how a program behaves. This converter reads INI and properties text, understands section headers, comments and typed values, and produces clean nested JSON that you can paste straight into a modern codebase. It runs entirely in your browser, so private configuration values such as internal hostnames never leave your machine.

How to Use the INI / Properties to JSON Converter

1. Paste your configuration text into the input box, including any section headers in square brackets.
2. Check that keys use the equals sign or colon separator, one setting per line, as in normal INI files.
3. Click Convert to JSON to transform sections into nested objects and top level keys into plain fields.
4. Review the JSON output and confirm that numbers and boolean values were typed the way you intended.
5. Copy the JSON result and paste it into your application, API payload or new configuration file.

Key Features

• Section support: headers such as server or database become nested JSON objects automatically.
• Smart typing: numeric values become numbers and true and false become booleans instead of strings.
• Comment handling: semicolon and hash comment lines are ignored rather than breaking the conversion.
• Properties compatibility: plain key value pairs without any section are converted to a flat JSON object.
• Fully local conversion: your configuration is processed in the browser and is never uploaded anywhere.

Best Practices and Tips

• Keep one setting per line. Multi line values are not part of the classic INI format and will be treated as separate keys.
• Use dotted section names such as app.cache when you want a clear hierarchy that survives the move to JSON.
• Quote values that look like numbers but must stay strings, for example version codes and postal codes, before converting.
• Strip secrets such as passwords and tokens from configuration text before pasting it into any online tool, including this one.

Common Mistakes to Avoid

• Forgetting a closing bracket on a section header, which merges its keys into the previous section without any warning.
• Using duplicate keys inside one section, where the later value silently overwrites the earlier one in the output.
• Expecting nested sections from indentation alone. INI has no indentation based nesting, so use explicit section headers instead.

Frequently Asked Questions

What is the difference between INI and properties files?

Both formats store settings as key and value pairs, one per line. INI files add section headers in square brackets to group related settings, while Java properties files are usually flat lists of keys. This converter handles both: sections become nested objects and flat keys stay at the top level of the JSON output.

Why are some values converted to numbers and booleans?

JSON distinguishes strings from numbers and booleans, and most applications expect real typed values rather than text. A port of 8080 is far more useful as the number 8080, and an enabled flag is more useful as a true boolean. If a value must remain text, quote it in your source or convert it back to a string after conversion.

How are comments handled?

Lines starting with a semicolon or a hash are treated as comments and dropped from the output. Inline comments after a value are kept as part of the value, because in many INI dialects there is no standard inline comment rule, so the safe behaviour is to preserve the text.

Can I convert JSON back to INI with this tool?

No, this tool converts in one direction only, from INI or properties text to JSON. Converting JSON back to INI needs different choices, such as how to flatten nested objects, so it is deliberately kept as a separate job rather than a confusing round trip mode.

Related Tools

• .env File Generator – build a clean .env file from key-value pairs
• Dockerfile Generator – build a Dockerfile from base image, ports, copy paths and commands
• package.json Generator – build a valid package.json from name, version and scripts