Processed in your browser

CSV / INI Converter

Each CSV row becomes a consecutively numbered section and each column becomes a key. Reverse conversion accepts row1, row2, and so on to keep order and missing rows explicit.

Processed in your browser
0 / 1,000,000
Converted output

Tool guide

What is CSV / INI Converter?

CSV and INI Converter represents row order with consecutive row1, row2 sections and uses column names as keys. Reverse conversion requires numbering from row1, making gaps, extra configuration sections, and duplicate keys visible instead of silently reordering the table. Common workflows include the following. Store a small CSV list as INI. Export consecutive INI sections as a table. Detect missing rows and duplicate fields. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.

When to use it

  • Store a small CSV list as INI.
  • Export consecutive INI sections as a table.
  • Detect missing rows and duplicate fields.

How to use it

  1. Choose delimiter and direction.
  2. Confirm headers can be INI keys.
  3. Use consecutive row1 and row2 sections for INI.
  4. Convert and fix duplicates or numbering gaps.
  5. Review string values and spreadsheet safety.
  6. Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.

Runnable examples

The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.

Example 1

id,name,status
51,XML INI,develop
60,CSV Properties,ready

Example 2

[row1]
id=51
name=XML INI
status=develop

[row2]
id=60
name=CSV Properties
status=ready

Input rules

  • CSV headers must be unique and non-empty.
  • INI sections must be numbered consecutively from row1.
  • Every section can contain scalar keys only.
  • Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
  • Only consecutive row1, row2 sections are accepted.

Output rules

  • Each row becomes one numbered section.
  • INI values remain strings in CSV.
  • The union of fields becomes the CSV header.
  • Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
  • All imported INI values remain strings.

Limitations and cautions

  • Only consecutive row1, row2 sections are accepted.
  • All imported INI values remain strings.
  • Nested dotted CSV paths do not fit one-level INI sections.

How your data is handled

All parsing, format conversion, Base64 work, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.

FAQ

Is CSV or INI content uploaded?

No. Parsing, conversion, and output generation remain in the current browser tab.

Is every round trip lossless?

No. Comments, layout, type systems, and binary capabilities differ, so the page lists areas that require review.

Why can valid input still be rejected?

The destination may not have a safe, unambiguous representation. Dangerous keys, unsafe integers, excess depth, and ambiguous mappings are rejected.

Why do sections start at row1?

Consecutive numbering preserves order and exposes gaps or non-table sections.

Is CSV header order retained?

CSV output follows the first row object's key order, which should still be reviewed in the target workflow.

How are blank rows handled?

Rows with no populated fields are ignored.

Updated: 2026-08-09