¿Odias los anuncios? Ir Sin publicidad Hoy 

INI to YAML Converter

DatosDesarrollador

ANUNCIO · ¿ELIMINAR?

APORTE

Proceso automático

PROD.

Lado cliente

ANUNCIO · ¿ELIMINAR?

Guía

INI to YAML Converter

Convert INI configuration files into clean, structured YAML — and back again. This tool parses your INI sections, infers real data types (booleans, numbers, and null), and rebuilds the data as properly indented YAML mappings entirely in your browser. A reverse mode turns YAML back into sectioned INI, filling the gap left by tools that only handle JSON.

Cómo Usar

Paste your INI configuration into the input box, or load the built-in example.
Keep the direction on INI to YAML, or switch to YAML to INI to reverse the conversion.
Adjust the options — type inference, comment stripping, and duplicate-key handling — to match your file.
Copy or download the generated output instantly.

Características

Conversión bidireccional – Transform INI to YAML or YAML back into INI.
Inferencia de tipos – Automatically coerce true/false, numbers, and null instead of leaving everything as strings.
Nested sections – Dotted headers like [database.pool] become multi-level YAML mappings.
Claves duplicadas – Choose last-wins or collect repeated keys into an array.
Private and instant – Everything runs client-side; your configuration never leaves the browser.

 Preguntas frecuentes

What is the difference between INI and YAML?

INI is a flat, section-based key/value format with no formal specification, while YAML is a structured data-serialization standard that supports nested maps, lists, and explicit data types. YAML can represent deeper hierarchies than INI, which is limited to single-level sections.
How does type inference work when parsing INI?

INI stores every value as plain text. Type inference inspects each raw string and promotes it to a richer type: tokens like true, false, on, off, yes and no become booleans, numeric strings become integers or floats, and empty or null tokens become null. This mirrors how YAML natively distinguishes scalars.
Why are INI sections converted into nested YAML mappings?

An INI section header such as [database] groups the keys beneath it. In YAML that maps naturally to a nested mapping under a database key. Dotted headers like [database.pool] express an extra level of hierarchy, which becomes a mapping nested inside another mapping.