Which column becomes the section name?

The first column of every data row. It's used only to name that row's [section] and never appears as a key inside the section.

Where do the key names come from?

From the header row: every header column after the first becomes the key name for that row's key=value line, paired with the matching cell value.

What if two rows share the same first-column value?

You get two separate [section] blocks with the same section name in the output; INI itself doesn't forbid duplicate section headers, but most parsers will only keep the last one, so make sure your first column is unique if that matters.

Does this handle nested or multi-level INI sections?

No, it produces a flat list of sections, one per data row; INI itself has no standard nesting syntax, and this tool doesn't invent one.

CSV to INI Converter - Convert Online

Overview

Introduction

Some tools still read plain INI config files, one [section] per logical record. This tool turns a CSV export into exactly that shape, one section per row.

It needs no configuration: the first column names each section, and every other column becomes a key=value line inside it, using the header row as the key names.

What Is CSV to INI Converter?

A CSV-to-INI converter that reads the header row once for key names, then emits one [section] block per data row, using that row's first cell as the section name and its remaining cells as key=value pairs.

It produces plain INI text with no special escaping beyond the raw key=value syntax, matching the format most INI parsers and config loaders expect.

How CSV to INI Converter Works

The header row is split into a section-name column (the first one, used only for naming) and a list of key names (every column after it).

For each data row, a `[section]` line is emitted using that row's first cell, followed by one `key=value` line per remaining column, pairing each key name with that row's corresponding cell value.

When To Use CSV to INI Converter

Use it when you're generating a batch of config sections, one per user, per server, per environment, from a spreadsheet, and need real INI output.

It's also handy for quickly turning a small settings table into a config file format that an existing tool already knows how to read.

Often used alongside INI to CSV Converter, CSV to SQL Converter and CSV to vCard Converter.

Features

Advantages

Requires no extra configuration; the CSV's own header row and first column are all it needs.
Produces one section per row, matching a common pattern for per-item config blocks.
Runs entirely client-side, so the data never leaves your browser.

Limitations

CSV needs at least two columns (one for the section name, one for at least one key), or there's nothing to put inside each section.
No INI comment syntax, nested sections, or type coercion (numbers/booleans) is generated; every value is written as plain text.

Examples

Converting a small CSV into INI sections

Input

server,host,port
web1,10.0.0.1,8080
web2,10.0.0.2,8081

Output

[web1]
host=10.0.0.1
port=8080

[web2]
host=10.0.0.2
port=8081

The 'server' column names each section; 'host' and 'port' become key=value lines inside it.

Best Practices & Notes

Best Practices

Make sure the first column's values are unique, since duplicate section names can be silently merged or overwritten by whatever tool reads the INI file afterward.
Keep values free of raw newlines, since INI's key=value lines are single-line by convention.
Use INI to CSV Converter afterward to confirm a round trip reproduces the same rows.

Developer Notes

The first column is deliberately treated as pure metadata (the section name) and never duplicated as a key inside the section, since most INI-consuming tools expect the section name to be the record's identifier, not one of its data fields.

CSV to INI Converter Use Cases

Generating one config section per server, environment, or user from a spreadsheet
Turning a settings table into an INI file for a tool that reads that format
Bulk-producing config blocks for legacy or embedded systems that use INI files

Common Mistakes

Leaving duplicate values in the first column and being surprised when the resulting INI file's sections collide when reloaded elsewhere.
Expecting numeric or boolean values to be typed in the output; everything is plain, unquoted text after the =.

Tips

If a value needs to contain an = sign or a newline, check your INI-consuming tool's own escaping rules before relying on this straightforward key=value output.
Pair with INI to CSV Converter to verify the round trip preserves every section and key you expect.

CSV to INI Converter