Free · No signup · Runs in your browser

INI to CSV

Drop an .ini or .conf, get a clean CSV where every section is a row and every key is a column.

To convert INI to CSV, drop or paste an INI file — csvtodashboard parses it into rows and columns in your browser, then emits a clean, RFC-4180 CSV with one header row. Fields are comma-separated with quoting only where a value contains a comma, quote or newline, so the file opens cleanly in Excel, pandas or any CSV reader. Nothing is uploaded; the whole conversion runs on your device.

01 · How it works

Three steps, then done.

Paste your INI text or drop a config file. The converter reads each section and its key=value pairs, unions every key into a single header, and gives you CSV you can open in any spreadsheet. Nothing is uploaded.

1

Add your INI

Paste INI text directly or drag in a .ini, .cfg, or .conf file. Comments starting with ; or # and blank lines are ignored automatically.

2

Get your CSV

Each [section] becomes a row with a 'section' column, plus one column per key. Keys are unioned across all sections in first-seen order, and values get RFC-4180 quoting where needed.

3

Copy or download

Copy the result to your clipboard or download the .csv. Open it in Excel, Google Sheets, or feed it into the next tool — it's standard CSV.

02 · Why ours

Why convert INI to CSVCSV

INI is great for configuration but awkward to review in bulk. CSV turns your sections into a flat table you can sort, diff, and audit.

  • 01

    Flatten sections into rows

    When you have dozens of [section] blocks, a table beats scrolling. One row per section makes it trivial to scan and compare settings side by side.

  • 02

    Spreadsheet-ready

    CSV opens directly in Excel, Numbers, and Google Sheets. Filter by section, sort by a key, or pivot your config without writing a parser.

  • 03

    Union of every key

    Sections rarely share the exact same keys. The converter collects every key across all sections into one header, so nothing gets dropped and gaps stay empty.

  • 04

    Completely private

    Everything runs client-side in your browser. Your config — which often holds hosts, ports, and secrets — never touches a server.

"Every [section] becomes a row, every key becomes a column — your config, finally in a table you can sort and diff."
csvtodashboard.com
Good to know

ini to csv notes.

Format-specific details worth knowing before you convert INI to CSV.

  • Quoting only when needed

    Fields containing a comma, quote or newline are wrapped in double quotes (with internal quotes doubled), per RFC 4180; everything else stays bare.

  • Excel's leading-zero trap

    CSV is plain text, so a code like 007 is preserved in the file — but Excel may strip the zero on open. Import the column as text if that matters.

  • One header, even columns

    The first row is the header and every row carries the same column count, so spreadsheets and parsers never misalign.

03 · FAQ

ini to csv questions.

Does my INI file get uploaded anywhere?
No. The conversion happens entirely in your browser using client-side JavaScript. Your file is never sent to a server, which matters because config files often contain hosts, ports, and credentials.
Each [section] header becomes one row. A 'section' column holds the section name, and every key in that section becomes its own column. Keys are unioned across all sections in first-seen order, so a key that only appears in some sections leaves the others blank.
Yes. Both = and : are accepted as separators. The converter splits on whichever appears first in the line, so values that contain : or = (like URLs) are preserved intact.
Lines starting with ; or # are treated as comments and skipped, as are blank lines. Keys and values are trimmed, and surrounding single or double quotes on a value are stripped before writing the CSV.
Global keys that appear before the first [section] are collected into a row with an empty section name, so nothing is lost.