XML to INI Converter

Understanding XML and INI

XML (Extensible Markup Language) is a feature-rich markup language capable of expressing arbitrarily complex data structures. With its support for nested elements, attributes, namespaces, DTDs, and XSD schemas, XML can describe virtually any data model. It has been the standard for enterprise data exchange, powering SOAP web services, Java configuration (web.xml, pom.xml), .NET manifests, and Android resources. However, this power comes at the cost of verbosity — XML configuration files are often hundreds of lines long with repetitive opening and closing tags. For a complete overview of XML capabilities and syntax, visit our XML guide.

INI (Initialization File) is one of the oldest and simplest configuration file formats. Originating from early versions of Windows, INI files organize settings into sections (denoted by square brackets) containing key-value pairs separated by equals signs. INI has no formal specification, but its simplicity has made it ubiquitous — PHP uses php.ini, MySQL uses my.cnf (INI syntax), Git uses .gitconfig, and Python's configparser module reads INI natively. The format supports comments (with ; or #) but has no concept of data types, arrays, or nesting beyond one level. For more about INI structure and conventions, see our INI guide.

Converting XML to INI means collapsing a hierarchical, richly typed data structure into a flat, section-based key-value format. This trade-off sacrifices expressiveness for simplicity — the result is a configuration file that virtually any application can parse, at the cost of losing deep nesting and complex data relationships.

Why Convert XML to INI?

Despite INI's limitations, there are many practical scenarios where converting from XML to INI is the right choice:

• Migrating configurations for legacy Windows applications. Many older Windows desktop applications, services, and drivers read their settings exclusively from INI files. If you have configuration data in XML that needs to feed into one of these systems, conversion to INI is required.
• Configuring PHP, MySQL, or Git. Core infrastructure tools like PHP (php.ini), MySQL (my.cnf), and Git (.gitconfig) use INI-style configuration. When application settings are managed in XML but need to be deployed to these tools, XML-to-INI conversion bridges the gap.
• Simplifying configuration for embedded or resource-constrained systems. INI parsers are extremely lightweight — often just a few dozen lines of code. Embedded systems, IoT devices, and microcontrollers that cannot afford XML parsing overhead benefit from INI's minimal footprint.
• Creating human-editable configuration files. INI files are the easiest configuration format for non-technical users to understand and edit. When end users need to manually modify settings, INI's flat structure and lack of special syntax makes it less error-prone than XML.

How the Conversion Works

This is a cross-format conversion that uses JSON as an intermediate representation. The conversion follows a two-stage pipeline:

1. XML to JSON: The XML document is parsed by fast-xml-parser. Elements become JSON object keys, attributes are stored with @_ prefixes, text content goes into #text properties, and repeated sibling elements become JSON arrays.
2. JSON to INI: The JSON structure is walked to produce INI sections and key-value pairs. Top-level objects become INI sections (e.g., [database]), their primitive properties become key-value pairs, and nested objects are flattened with dot-separated section names or key names.

The table below shows how common XML patterns map to INI output:

Before and After Example

Below is an XML configuration file for a web application and its INI equivalent after conversion. Notice how XML element hierarchies are collapsed into flat INI sections with key-value pairs.

<?xml version="1.0" encoding="UTF-8"?>
<config>
  <application>
    <name>MyWebApp</name>
    <version>3.2.1</version>
    <debug>false</debug>
  </application>
  <database>
    <host>db.example.com</host>
    <port>3306</port>
    <username>admin</username>
    <password>secret123</password>
  </database>
  <cache>
    <enabled>true</enabled>
    <ttl>3600</ttl>
    <driver>redis</driver>
  </cache>
</config>

[config.application]
name=MyWebApp
version=3.2.1
debug=false

[config.database]
host=db.example.com
port=3306
username=admin
password=secret123

[config.cache]
enabled=true
ttl=3600
driver=redis

Each second-level XML element (application, database, cache) becomes an INI section using dot notation from the root. The child elements within each section are converted to simple key-value pairs. This flat structure is immediately readable and parsable by any INI-compatible tool.

Tips and Best Practices

Related Tools

Explore other converters and resources that complement XML-to-INI conversion: