LOCAL CONFIG CONVERTER / INI TO JSON

INI to JSON

Convert global INI assignments and named sections into a JSON object without evaluating interpolation or application-specific directives.

Processed in this browserOne UTF-8 .ini, .cfg, or .conf file up to 2 MB and 100,000 physical lines. Keys must be unique; multiline values are not accepted.

Step 1 / source

Choose the source

INI - 2 MB

Drop one file here

Choose the ini configuration file you want to turn into json configuration object.

Browse filesChecking publication status...

No file upload

This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.

Original stays unchanged

The converter creates a separately named output. It never writes back into the source file.

Bounded work

One UTF-8 .ini, .cfg, or .conf file up to 2 MB and 100,000 physical lines. Keys must be unique; multiline values are not accepted.

Plain-language method

How INI to JSON works

The parser ignores blank and full-line comment rows, reads unique key=value or key:value assignments, keeps global keys at the JSON root, turns each [section] into a one-level object, and does not expand variables or execute directives.

01
Choose a valid source
Use explicit section headers and one assignment per physical line. Duplicate keys and a global key colliding with a section are rejected.
02
Review the conversion choices
JSON indentation changes whitespace only. INI values remain strings because INI has no universal type standard.
03
Inspect the separate result
The result ends in _nirmion_tools.json. Comments, delimiter style, quote style, and original blank lines are not retained.

Useful when

Practical jobs this tool handles

Inspect application settings with JSON tooling.
Prepare a simple configuration migration.
Create deterministic fixtures from an INI file.

Before converting

Check the source and destination rules

Check duplicate keys and repeated sections.
Review quoted and inline-comment values.
Convert types explicitly in the receiving application.

Know the boundary

Know what the destination format cannot keep

INI is not one universal standard. Interpolation, repeated keys, multiline syntax, typed values, and application-specific directives are deliberately not interpreted.

Quick answers

Questions before you convert

The conversion contract is deliberately explicit.

Are values converted to booleans or numbers?

No. Every INI value remains a JSON string.

Where do global keys go?

They stay at the top level beside section objects.

Are inline comments removed?

No. Only full-line ; and # comments are ignored because inline rules vary.