Convert XLSX to INI

Why Convert XLSX to INI?

Converting XLSX Excel files to INI format transforms structured spreadsheet data into lightweight configuration files with named sections and key-value pairs. This is particularly valuable when you manage application settings, server configurations, or user preferences in Excel and need to deploy them as INI configuration files that software can read directly.

Each row of your Excel spreadsheet becomes a named section in the INI file, with column headers serving as keys and cell values as their corresponding values. Our converter reads the XLSX workbook, extracts data from the active worksheet, and uses one column (typically the first) as the section name while mapping remaining columns to key-value pairs within each section.

This conversion is especially useful for DevOps engineers and system administrators who maintain configuration data in Excel spreadsheets for easy editing and sharing. Instead of manually creating INI files for each server, service, or application, you can maintain all settings in a single Excel workbook and batch-convert them to INI format whenever configurations change.

The INI format is one of the simplest and most widely supported configuration formats. It is natively supported by Python's configparser module, PHP's parse_ini_file function, Windows system APIs, and countless other tools. This makes XLSX to INI conversion an efficient bridge between spreadsheet-based configuration management and actual software deployment.

Key Benefits of Converting XLSX to INI:

• Config Generation: Generate configuration files directly from Excel spreadsheet data
• Named Sections: Each spreadsheet row becomes a named INI section with key-value pairs
• Formula Support: Calculated Excel values are exported as their computed results
• Header Mapping: Excel column headers automatically become INI keys in each section
• Human-Readable: INI output is easy to read, edit, and verify with any text editor
• Wide Compatibility: INI is supported by Python, PHP, Windows, .NET, and more
• Multi-Sheet Workbooks: Extract configuration data from specific worksheets

Practical Examples

Example 1: Server Configuration from Excel

Input XLSX file (servers.xlsx):

| Server      | Host          | Port | Protocol | MaxConn |
|-------------|---------------|------|----------|---------|
| WebServer   | 192.168.1.10  | 8080 | https    | 500     |
| Database    | 192.168.1.20  | 5432 | tcp      | 100     |
| CacheServer | 192.168.1.30  | 6379 | tcp      | 200     |
| MailServer  | 192.168.1.40  | 587  | smtp     | 50      |

Output INI file (servers.ini):

[WebServer]
Host = 192.168.1.10
Port = 8080
Protocol = https
MaxConn = 500

[Database]
Host = 192.168.1.20
Port = 5432
Protocol = tcp
MaxConn = 100

[CacheServer]
Host = 192.168.1.30
Port = 6379
Protocol = tcp
MaxConn = 200

[MailServer]
Host = 192.168.1.40
Port = 587
Protocol = smtp
MaxConn = 50

Example 2: Application Settings

Input XLSX file (app_settings.xlsx):

| Module    | Theme | Language | FontSize | AutoSave |
|-----------|-------|----------|----------|----------|
| Editor    | dark  | en       | 14       | true     |
| Dashboard | light | fr       | 12       | false    |
| Terminal  | dark  | de       | 16       | true     |

Output INI file (app_settings.ini):

[Editor]
Theme = dark
Language = en
FontSize = 14
AutoSave = true

[Dashboard]
Theme = light
Language = fr
FontSize = 12
AutoSave = false

[Terminal]
Theme = dark
Language = de
FontSize = 16
AutoSave = true

Example 3: Database Connection Profiles

Input XLSX file (db_connections.xlsx):

| Profile     | Driver     | Host            | Database | Timeout |
|-------------|------------|-----------------|----------|---------|
| Production  | postgresql | db.prod.com     | app_db   | 30      |
| Staging     | postgresql | db.staging.com  | app_db   | 60      |
| Development | sqlite     | localhost       | dev.db   | 0       |

Output INI file (db_connections.ini):

[Production]
Driver = postgresql
Host = db.prod.com
Database = app_db
Timeout = 30

[Staging]
Driver = postgresql
Host = db.staging.com
Database = app_db
Timeout = 60

[Development]
Driver = sqlite
Host = localhost
Database = dev.db
Timeout = 0

Frequently Asked Questions (FAQ)

Q: What is XLSX format?

A: XLSX is the default file format for Microsoft Excel since 2007. It is based on the Office Open XML (OOXML) standard (ISO/IEC 29500) and stores spreadsheet data as ZIP-compressed XML files. XLSX supports multiple worksheets, formulas, charts, pivot tables, conditional formatting, and rich cell styling. Each worksheet can hold up to 1,048,576 rows and 16,384 columns.

Q: What is INI format?

A: INI (Initialization) is a simple text-based configuration file format organized into sections and key-value pairs. Each section starts with a name in square brackets (e.g., [SectionName]), followed by lines of key = value pairs. Comments start with semicolons (;) or hash characters (#). The format originated in the MS-DOS era and is still widely used for application configuration in Python (configparser), PHP (php.ini), Windows, Git (.gitconfig), and many other tools.

Q: How are Excel rows mapped to INI sections?

A: Each row of the Excel spreadsheet becomes a separate section in the INI file. The first column is typically used as the section name (in square brackets), and the remaining columns become key-value pairs within that section. The column headers from the Excel file become the INI keys. If the first column values are not unique, the converter appends a number to make each section name unique.

Q: Are Excel formulas preserved in the conversion?

A: Excel formulas are evaluated and their computed results are exported to the INI file. For example, if a cell contains =SUM(A1:A10) and the result is 500, the INI file will contain the value 500. The formula itself is not preserved since INI format does not support calculations. This means you always get the final values from your spreadsheet.

Q: Can I use the INI output with Python's configparser?

A: Yes! The generated INI file is fully compatible with Python's built-in configparser module. You can read it directly with configparser.read('file.ini') and access values using config['SectionName']['KeyName']. The output uses the standard INI syntax that configparser expects, including proper section headers and key = value formatting.

Q: What happens with multiple worksheets in the XLSX file?

A: By default, the converter processes the first (active) worksheet in the XLSX file. If your workbook contains multiple sheets, only the active sheet is converted. Each row from that sheet becomes a section in the INI file. If you need to convert data from a specific sheet, ensure it is set as the active sheet before uploading.

Q: What happens with special characters in Excel data?

A: Values containing special INI characters (like equal signs or semicolons) are properly handled during conversion. The converter ensures that values are written in a way that INI parsers will read correctly. Section names are sanitized to remove characters that are invalid in INI section headers (like square brackets). UTF-8 characters from Excel cells are preserved in the output.

Q: Is there a limit on the number of Excel rows?

A: There is no hard limit on conversion, but INI files are designed for configuration rather than large datasets. Each Excel row becomes a section, so a 1000-row spreadsheet produces a 1000-section INI file, which may not be practical for all use cases. INI works best for dozens to hundreds of entities. For very large Excel datasets, consider JSON or YAML as more suitable target formats.