INI to JSON Converter

Each [section] header becomes a nested object in the JSON, and every key after it nests inside that object until the next header. Keys that appear before any section land at the top level of the output.

Lines that start with a semicolon or a hash are treated as comments and dropped, and empty lines are ignored. Only real key and value pairs and section headers make it into the JSON.

With 'Parse values' on, the words true and false become booleans and clean numeric strings like 5432 or 3.14 become numbers. Turn the option off to keep every value as a plain string, which is safer for things like zip codes or version tags that must stay text.

Yes. Both the equals sign and the colon work as separators, and the first one that appears on a line is used. That means a value can safely contain the other character, so a URL after an equals sign keeps its own colons intact.

A single matching pair of surrounding double or single quotes is stripped, so driver = "redis" becomes redis. Quotes inside the value are left alone, and this lets you wrap a value that has leading or trailing spaces you want to keep.

For a repeated key the last value wins. A section header that appears more than once is merged into the same object rather than replaced, so later keys are added alongside the earlier ones.

No. INI has only one level of sections, so a header written as [a.b] becomes a single top-level key named a.b rather than an object b inside an object a. If you need deep nesting, restructure the data as JSON or YAML.

A section header missing its closing bracket, a line with no equals or colon, or a line with an empty key raises an error that is shown in red below the input. Fix or remove that line and the JSON reappears.

No. The conversion runs entirely in your browser using client-side JavaScript, so your configuration never leaves your device and nothing is stored on a server.