Loading JSON to INI Converter...
Please wait a moment

How to Convert JSON to INI - Step by Step Guide

Step 1

Input Your JSON Data

Let's get your JSON data into the converter! Whether you're creating INI configs for legacy systems or need INI format, you have several convenient options:

•
Paste directly: Copy your JSON data and paste it into the input editor
•
Upload a file: Click "Upload" to select a .json or .txt file from your computer
•
Try the sample: Click "Sample" to load example data and see how the converter works
Step 2

Automatic Conversion & Validation

The conversion happens instantly! As soon as you input your JSON data, the converter automatically:

•
Checks the JSON: If something is off, the error names the line and column, and it tells you when you've pasted INI, YAML or XML by mistake
•
Converts to INI: Transforms JSON objects and properties into INI sections and key-value pairs
•
Follows your reader: The Style menu switches between standard INI (Node ini, PHP) and Python configparser rules
Step 3

Review the INI Output

The converter displays your INI output with syntax highlighting! The INI structure mirrors your JSON data:

•
Objects: Each one becomes a [section]; an object inside another gets a dotted name like [app.metadata]
•
Values and lists: Plain values become key = value lines, lists become key[] = value lines (one item per line in the Python style)
•
Notes: Anything INI can't hold exactly, like an empty list or a null in configparser, is explained above the output
Step 4

Export Your INI Configuration

Get your converted INI config ready for use! Multiple export options make it easy to deploy your configurations:

•
Copy to clipboard: One-click copying for quick pasting into your configuration files
•
Download as file: Save as an .ini file for deployment or distribution
•
Real-time conversion: Changes are reflected immediately as you edit the JSON input

Frequently Asked Questions

How do I convert JSON data to INI format?

Paste your JSON into the editor, upload a .json file, or load the sample. The INI version appears on the right a moment later, and you can copy it or download it as converted.ini.

How is nested JSON laid out in the INI file?

Top-level plain values come first, then one [section] per object. An object inside an object gets a dotted section name, so an "app" object holding a "metadata" object becomes [app.metadata]. The Node ini package rebuilds the nesting from those dots when it reads the file; most other readers just see a section with a dot in its name.

How are arrays converted?

INI has no real list type, so there are two conventions. In the Standard style a list becomes repeated key[] = value lines, which the Node ini package and PHP's parse_ini_file read back as arrays. In the Python style each item goes on its own indented line under the key, the way setup.cfg does it. A list of objects becomes numbered sections like [servers.0] and [servers.1]. Empty lists are left out, with a note.

What happens to numbers, booleans, null and special characters?

Numbers are written exactly as you typed them, so a 19-digit ID like 8901240544102066246 or a price like 14.50 doesn't get rounded or reformatted. INI stores everything as text, so your program decides what's a number. true and false are written as they are. In the Standard style null is written as null, and any value with ;, #, =, quotes, line breaks or spaces at the ends goes in double quotes. configparser has no quoting, so the Python style writes values raw, turns null into an empty value and tells you when a value can't come back exactly.

Which style should I pick?

Use Standard if the file will be read by the Node ini package, PHP, or a similar parser that understands quoted values and key[] lists. Use Python configparser if a Python program will read it: every key goes inside a section (top-level values land in [DEFAULT]), lists are one item per line, and % is escaped as %% so the default ConfigParser() doesn't trip over it. Untick that option if you read the file with interpolation=None.

Is the converted INI ready for applications?

For the reader it targets, yes. We check the Standard output with the Node ini package and PHP's parse_ini_string, and the Python output with configparser, and compare what they read back against the JSON. Other INI parsers differ in the details, so if yours treats quotes or lists differently, run one file through it first. You can also format the INI further if needed.

Is the JSON to INI converter free, and is my data private?

Yes, it's free and there's nothing to sign up for. The conversion runs in your browser, so your JSON isn't uploaded anywhere. Nothing you paste is saved in the browser either. Uploaded files can be up to 10 MB.