Super Boring Tools

Search tools

Find a tool by name or what it does.

INI to JSON Converter

Paste an INI or config file and get clean JSON instantly. Sections nest, comments are stripped, and quoted values stay exact.

Converted to JSON live as you type. Nothing leaves your browser.

Options

JSON

Your JSON will appear here.

How to convert INI to JSON online

  1. Paste your INI file

    Drop an INI or config file into the input. The JSON appears live as you type, with sections nested and comments removed.

  2. Choose how values convert

    Toggle type coercion, duplicate-key arrays, and dotted-section nesting next to the output, and the JSON updates instantly.

  3. Copy or download the JSON

    Click Copy JSON to take it to your editor or API client, or download it as a .json file.

Why use this tool

Sections become nested objects

Square-bracket section headers turn into nested JSON objects, and the key and value lines under each one become that object properties.

Comments and whitespace handled

Full-line and inline comments starting with a semicolon or a hash are removed, and whitespace around every key and value is trimmed.

Optional type coercion

Turn bare numbers and true or false into real JSON numbers and booleans, or keep every value as a string. Quoted values always stay strings.

Duplicate keys and dotted sections

Repeated keys can keep their last value or gather into an array, and dotted section names can nest into objects or stay a single literal key.

Quoted values stay intact

Values wrapped in single or double quotes keep their exact contents, so a semicolon or hash inside a quote is never mistaken for a comment.

Runs entirely in your browser

Everything happens on your device. Config files that name internal hosts, tokens, or secrets are never uploaded.

About this tool

This tool converts INI and config files to JSON in your browser. Paste a file and the JSON appears as you type. Section headers in square brackets become nested objects, key and value lines become properties, and comments starting with a semicolon or a hash are stripped. Whitespace around keys and values is trimmed, and quoted values keep their contents exactly, including semicolons and hashes that would otherwise start a comment.

INI files show up as application settings, tool configuration, and desktop profiles, and most tooling around them speaks JSON instead. Three options shape the result. Coercion turns bare numbers and true or false into real JSON numbers and booleans, while any quoted value stays a string. Duplicate keys can keep their last value or collect into an array. Dotted section names like server.http can nest into objects or stay a single literal key. Keys that appear before the first section become top-level properties.

Config files often carry hostnames, tokens, and credentials, which makes them a poor fit for converters that upload your input. Here nothing leaves your browser. Once you have JSON, the JSON formatter can validate or restyle it, while the YAML to JSON converter and CSV to JSON converter handle the other config and data formats you are likely to meet.

Frequently asked questions

How does the converter handle sections?
Each square-bracket section header becomes a JSON object, and the key and value lines beneath it become that object properties. Keys that appear before the first section become top-level properties.
Are comments and quotes supported?
Yes. Lines starting with a semicolon or a hash are dropped, as are inline comments after a value. Values wrapped in quotes keep their exact contents, so a semicolon or a hash inside a quote is preserved.
What does type coercion do?
With coercion on, bare numbers become JSON numbers and true or false become booleans. Everything else stays a string, and any quoted value stays a string even when coercion is on. Turn it off to keep every value as a string.
How are duplicate keys and dotted sections treated?
A repeated key keeps its last value by default, or collects every value into an array when you enable duplicate arrays. A dotted section name like a.b can nest into objects or stay a single literal key, depending on the nesting option.
Is my data uploaded anywhere?
No. Everything runs in your browser. Nothing is sent to a server, which matters for config files that carry credentials or internal hostnames.
What happens with blank or malformed lines?
Blank lines and comment lines are ignored, and any line that is not a section header or a key and value pair is skipped without stopping the conversion. A note shows how many lines were skipped.

Related tools