Processed in your browser

CSV / TOML Converter

CSV headers and rows map to TOML [[rows]] array tables. Reverse conversion accepts only one rows array rather than guessing how arbitrary configuration should become a table.

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

Tool guide

What is CSV / TOML Converter?

CSV and TOML Converter uses a fixed rows array of tables for small tabular data in configuration and review exports. Each CSV row becomes one [[rows]] item, and reverse conversion accepts only one rows array. This avoids guessing how arbitrary TOML tables or nested configuration should map to columns. Common workflows include the following. Store a CSV table in TOML configuration. Export TOML rows for review. Check field counts and string typing. 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 CSV table in TOML configuration.
  • Export TOML rows for review.
  • Check field counts and string typing.

How to use it

  1. Choose delimiter and direction.
  2. Confirm CSV headers are unique and non-empty.
  3. Provide one rows array for TOML input.
  4. Convert and verify field counts.
  5. Review string typing 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

[[rows]]
id = "51"
name = "XML INI"
status = "develop"

[[rows]]
id = "60"
name = "CSV Properties"
status = "ready"

Input rules

  • CSV headers must be unique and non-empty.
  • TOML to CSV accepts one rows array only.
  • The delimiter must match the input.
  • 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.
  • TOML to CSV accepts one rows array only.

Output rules

  • CSV rows become TOML array tables.
  • Imported CSV values remain strings.
  • Spreadsheet-safe mode protects formula prefixes.
  • Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
  • Imported CSV values remain strings.

Limitations and cautions

  • TOML to CSV accepts one rows array only.
  • Imported CSV values remain strings.
  • TOML dates, comments, and source layout are not retained.

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 TOML 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 must TOML use rows?

A fixed array of tables maps each item to one row without guessing arbitrary configuration.

Do CSV numbers become TOML numbers?

No. CSV has no reliable type information, so imported values remain strings.

Are semicolon and Tab supported?

Yes. Select the delimiter in the workspace.

Updated: 2026-08-09