Is my configuration data uploaded?

No. Conversion in both directions runs entirely in your browser. Config files often contain hostnames and credentials, so nothing ever leaves your machine.

How are INI values typed in the JSON output?

Values that read true or false become booleans, purely numeric values become numbers, and everything else stays a string. Surrounding single or double quotes are stripped.

Are comments and nested sections supported?

Lines starting with ; or # are ignored as comments and are not carried into the output. Sections map to one level of nesting only — INI has no deeper hierarchy, so deeply nested JSON cannot round-trip back to INI.

INI ↔ JSON Converter

Overview

A two-way converter between INI — the classic [section] / key=value config format used by PHP, Git, systemd, and countless legacy apps — and JSON. Sections become nested objects; keys before the first section stay at the top level. Useful for migrating old configs into JSON-based tooling or generating an INI file from structured data.

How to use

Pick a direction with the INI → JSON / JSON → INI tabs.
Paste your input into the text area (labeled INI or JSON to match the direction).
Read the converted result from the Output area — it updates as you type.

Examples

[server] + host=localhost + port=8080 → {"server":{"host":"localhost","port":8080}}
{"debug":true,"db":{"name":"app"}} → debug=true followed by [db] / name=app

Notes

Type detection is heuristic: a value like 1.0 becomes the number 1, and a numeric-looking value such as a zip code cannot stay a string. Comments are dropped on conversion, so keep the original file if annotations matter.