INI to JSON — sections and keys to a JSON object
Paste INI-style [section] blocks and key=value lines to get nested JSON. Lines starting with ; or # are treated as comments and skipped.
INIJSON
Converts as you type — paste or drop a file.
Input(INI)
Output(JSON)
Runs in your browser — nothing is uploaded to our servers.
Older apps, installers, and game settings still ship INI. Converting a sanitized sample to JSON makes it easier to drop into modern tools without rewriting the file by hand.
Each [section] becomes a nested object; bare keys above the first section land on the root. Comments with ; or # are ignored so documentation lines do not become fake keys.
For environment-style KEY=VALUE files, dotenv to JSON is usually a better fit than INI sections.
How to use
- Paste INI text
- Convert
- Copy the nested JSON
Why this converter
- Nests sections the way most INI files are read
- Skips ; and # comment lines
- Runs only in your browser — nothing is uploaded
Good for
- Legacy app configs
- Game settings exports
- Docs and demos
Tips
- All values stay strings — cast types in your own code if needed.
- Duplicate keys in the same section keep the last value.
Examples
| Input | Output | Note |
|---|---|---|
| [app] name=demo | { "app": { "name": "demo" } } | — |
| theme=dark [window] width=1280 | { "theme": "dark", "window": { "width": "1280" } } | Keys above the first section sit on the root |
INI FAQ
- Keys without a section?
- They stay on the JSON root. Values are kept as strings.
- Need YAML or TOML instead?
- See YAML to JSON or TOML to JSON.
- Are numbers typed?
- No — everything stays a string so odd game-config values are not guessed wrong.