INI ⇄ JSON, YAML & TOML Converter
About INI ⇄ JSON / YAML / TOML
INI ⇄ JSON / YAML / TOML converts classic section-and-key configuration into structured data models and serializes structured mappings back to widely compatible INI.
How it works
INI sections become objects
Root assignments become root properties, section names become nested mappings and dotted section names such as server.tls create deeper objects. Duplicate keys and scalar-versus-section collisions are rejected.
Optional type inference
INI values remain strings unless inference is enabled. Conservative rules recognize booleans, null, JSON-style numbers, arrays and objects without turning leading-zero identifiers into numbers.
Structured data back to INI
JSON, YAML or TOML root mappings are flattened into root assignments and nested section headers. Arrays become quoted JSON text because INI has no portable array syntax.
Frequently asked questions
Is there one official INI specification?
No. INI dialects vary. This tool supports the common [section], key=value, key:value, # comment and ; comment conventions.
Are INI comments preserved through conversion?
No. Comments do not map into JSON, YAML or TOML values and are omitted by semantic conversion.
Can INI null convert to TOML?
No. If inference creates null, TOML output reports the incompatible path because TOML has no null value.
Sources & last verified
The behaviour of this tool and the claims on this page were checked against the specifications below on . Everything runs in your browser, so the output you see is exactly what the engine produced.
Found a wrong result or an outdated claim? Report an error and it will be re-verified.