INI to JSON
Parse .ini config files into structured JSON. Sections [name] become nested objects, comments (; and #) are stripped, and values are typed when possible — all locally in your browser.
INI in, JSON out
A small sample to show the shape of the conversion. Pretty-printed output, types preserved where possible.
[db] host=localhost port=5432
{
"db": {
"host": "localhost",
"port": 5432
}
}What you'll use this for
INI to JSON shows up in every backend and ETL stack — feeding APIs, migrating configs, debugging payloads.
API & data imports
Prepare payloads for REST APIs and ingestion endpoints.
Data migration
Move configuration and tabular data between systems and formats.
Debugging
Inspect production data in a sensible, structured form.
ETL pipelines
Stage transformations between formats in your data flow.
How to convert INI to JSON
Paste your INI
Drop your source into the left editor. The sample loads on first visit — replace it with your data.
Click Convert
Or leave Auto-convert on for live updates as you type. Conversion runs locally.
Review the output
The right pane shows pretty-printed JSON with status, byte counts, and line count.
Copy or download
Use the action bar to copy to clipboard or save as a file. Or jump to the reverse converter for round-trip checks.
Frequently asked questions
[section] headers become top-level objects in the JSON. All keys until the next section header are nested inside that object.
Both ; and # are treated as comment starts and stripped (including inline comments).
Yes. Integers, floats, true, and false are coerced automatically. Quoted strings keep their content.
Keys appearing before the first [section] become top-level properties of the JSON output.
Yes — runs entirely client-side. No upload or tracking.
About INI to JSON
INI is one of the oldest config formats — a flat list of key=value pairs grouped into [sections]. It's still common in Windows, Python (via configparser), Git (.gitconfig), and many tools. Converting to JSON gives you something you can pass straight to a JS app or API.
How parsing works
[section]declarations open a new nested object.- Lines starting with
;or#are comments. key=valuelines are parsed inside the current section.- Surrounding quotes on values are stripped.
Use cases
- Read legacy app configs into modern JS toolchains.
- Migrate Git
.gitconfiginto JSON for analysis. - Audit Python
setup.cfgortox.inistructure.