DevForge

Markdown table to CSV

Markdown tables are convenient to write and awkward to compute with. Paste one and this parses the header, alignment and body rows into a grid you can edit, then exports CSV that opens cleanly in a spreadsheet.

markdown
csv
options
format
grid

Technical Guide & Mechanics

Bridging Documentation and Data Processing

Markdown tables are widely used in READMEs, GitHub issues, and technical documentation due to their human-readable ASCII layout. However, when you need to run mathematical computations, filter data, or import records into databases, raw Markdown tables become a bottleneck. Converting them to RFC 4180-compliant CSV enables seamless ingestion into Excel, Google Sheets, Pandas, and database ETL pipelines.

Our parser handles Markdown table nuances gracefully: it recognizes header separation lines, respects column alignment colons, and accurately parses inline formatting. In standard Markdown, pipe characters (|) delimit columns; when pipes occur inside inline code spans, our lenient tokenizer protects them from prematurely breaking table structure.

The interactive spreadsheet grid allows you to review and modify table cells before exporting. Once satisfied, you can copy the raw CSV string or trigger an instant browser-generated download without any network round-trip.

how to use it

  1. 01Paste Markdown containing one or more tables.
  2. 02Pick a table if the input has several, and edit any cells.
  3. 03Download the CSV or copy it.

questions

What happens to pipes inside code spans?
Strictly, GitHub-flavored Markdown does not let backticks protect a pipe. Because generated tables often assume otherwise, a lenient mode treats those pipes as literal text.
Are leading zeros preserved?
In CSV the value is written as-is; whether a spreadsheet keeps 00123 as text depends on its import settings. The Excel export types every cell as a string instead.
Does it escape quotes and commas properly?
Yes. Fields containing commas, line breaks, or double quotes are wrapped in quotes, with internal quotes doubled in accordance with RFC 4180.
Can it handle tables with missing trailing pipes?
Yes. The parser supports both strict piped syntax and loose Markdown tables where outer pipes are omitted.

related