Use the free JSON to INI Converter below: your data never leaves your browser — all work happens on your device, and nothing is uploaded to any server.
What this tool does
Configuration files come in many formats, and INI is one of the oldest and simplest. An INI file has sections in square brackets, like [server], and key-value lines inside each section, like host = example.com. Programs, games, and servers have used INI files for decades, because they are easy to read, easy to edit by hand, and easy to explain to a new user. But modern tools often store settings as JSON, and moving settings from JSON to an INI file by hand is slow and error-prone. The JSON to INI Converter does that move for you, in your browser.
The conversion follows a clear rule. Top-level values stay outside any section, at the top of the file. Each nested object becomes a section named after its key, and its values become key-value lines inside that section. Deeper nesting is flattened with underscores, so a value three levels deep still gets a readable key. Lists become comma-separated values on one line. The result is a plain INI file any INI reader can parse.
How to convert your settings
Paste a JSON object into the input box. It must be an object, not an array, because INI files describe named settings, not lists. Press Convert, and the output box shows the INI file, with sections in the order of your JSON keys. Press Copy output to copy it, or Download INI to save it as a config.ini file you can drop into your program’s folder.
Here is a small example. The JSON {“server”: {“host”: “example.com”, “port”: 8080}, “debug”: true} becomes a [server] section with host and port lines, plus a debug = true line outside any section. That is the whole pattern. Once you see one conversion, every other conversion follows the same logic, which makes the output easy to predict and easy to edit by hand afterwards.
When INI is the right format
INI suits settings that humans edit. A game config, a small server config, a desktop app’s preferences, or a tool’s default options are all good INI candidates, because a user can open the file, find the setting, change the value, and save, without learning JSON syntax. INI has no braces, no quotes, and no commas to get wrong, which makes it forgiving for non-technical users.
INI is less suited to deeply nested data or data with many lists. If your settings have five levels of nesting, flattening them into underscore keys still works, but the file becomes harder to read than the JSON was. In that case, keep the JSON, or restructure the settings into fewer levels before converting. INI is best for flat or two-level settings, which covers most real configuration files.
Tips for a clean conversion
First, use clear key names in your JSON. Keys become INI keys verbatim, so “max_connections” reads well and “mc” does not. Second, keep values simple: strings, numbers, true and false, and short lists all convert cleanly. Values that are themselves large objects are better flattened or simplified before converting. Third, check the section order. Sections appear in the order of your JSON keys, so order your JSON keys the way you want the sections to read, with the most important section first.
Fourth, review the output before saving. INI has no standard for types, so every value becomes text. Your program will read “8080” as a number only if it parses it as one, and it will read “true” as a boolean only if it recognises the word. Check how your program interprets INI values, and adjust the values if needed. Fifth, keep a backup of the original JSON. The JSON is the exact record; the INI is the human-friendly copy.
Privacy and limits
Your settings never leave your browser. The conversion runs on your device, and nothing is uploaded. That matters because configuration files often contain hostnames, ports, paths, and sometimes secrets. You should still remove real passwords and keys before converting any config, even locally, because the output file may later be shared. But the conversion itself adds no exposure.
The tool handles everyday configuration objects comfortably. It does not preserve comments, because JSON has no comments to preserve, and it does not preserve key order inside nested objects beyond the order you gave. If your INI file needs comments, add them by hand after converting, with a semicolon or hash at the start of the line, following your program’s convention.
Finally, test the INI file with your program before relying on it. Load it, check that the settings take effect, and confirm that no value was misread. A one-minute test saves a confusing debugging session later, when a setting that looks right silently does nothing.
Related tools
- Convertir JSON a INI Online (Spanish version)
- Query String to JSON Converter
- JSON to Query String Converter