76 characters · 17 words · 76 bytes (UTF-8)
Output will appear here
Click in the output to select all text
76 characters · 17 words · 76 bytes (UTF-8)
Output will appear here
Click in the output to select all text
Convert between TOML configuration format and JSON objects.
Bidirectional converter between YAML configuration and JSON data.
Convert JSON data to clean YAML syntax with configurable indentation.
Format, indent, validate, and beautify JSON with custom spacing.
Beautify and format YAML documents with standardized indentation.
Convert CSV rows into an array of JSON objects with type inference.
INI files remain a common configuration format for legacy applications, Windows software, and simple settings files, organized into bracketed sections with key-value pairs. This converter transforms INI configuration into JSON, grouping each section into a nested JSON object, or converts JSON back into properly sectioned INI syntax. It's useful for developers migrating legacy application settings into a modern JSON-based config system, or generating an INI file for software that still expects that format. The converter correctly handles comments, section headers, and basic type inference for values like numbers and booleans. Since conversion happens entirely in your browser, your configuration data is never uploaded to a server, and there's no signup required. Paste your INI or JSON below to convert it instantly.
INI files are simple configuration files organized into bracketed [sections] containing key=value pairs, commonly used by older Windows applications and simple software settings.
Each bracketed section becomes a nested JSON object, with its keys and values as properties inside that object.
Keys without a section are treated as global or top-level properties in the resulting JSON, separate from any nested section objects.
Yes, values that look like numbers or booleans (true/false) are converted to their corresponding JSON types rather than staying as plain strings.
No, the entire conversion runs locally in your browser using client-side JavaScript - nothing is sent to a server.
Yes, it works bidirectionally, converting a nested JSON object back into properly formatted INI sections and key-value pairs.
Comments are not preserved in the JSON representation since JSON has no comment syntax, but the underlying key-value data converts accurately.