Markdown to CSV Converter
Paste a Markdown pipe table and download a clean CSV with the same columns.
- 100% local — nothing leaves your browser
- No sign-up, no account, always free
- Instant download once converted
Paste a Markdown pipe table and download a clean CSV with the same columns.
Need to go the other way? Convert CSV to Markdown →
Markdown to CSV: Extract Table Data from Documentation
Markdown pipe tables are everywhere in developer documentation — GitHub READMEs, Confluence pages, Notion documents, wikis, and pull request descriptions. If you need to work with the data in one of those tables, converting it from Markdown to CSV lets you open it in Excel, process it programmatically, or import it into a database without retyping every value.
ConvertRow parses standard Markdown pipe tables entirely in your browser. Paste the table (including the header row and the separator row of dashes), click Convert, and download a clean CSV. The separator row is automatically detected and excluded from the output, leaving only the actual data.
The conversion is local and instant. No Markdown is sent to a server — the table is parsed by a small JavaScript function that splits lines on pipe characters and strips the separator row. This works for any GFM-style pipe table regardless of the tool it came from.
For best results, paste the complete table including the header row. Make sure each row starts and ends with a pipe character ( | ) — some Markdown tools omit the leading pipe, which may cause parsing issues. Cells with pipe characters inside them should use the escape sequence \| to avoid column misalignment.
Common use cases for Markdown to CSV conversion:
- Extracting a comparison table from a GitHub README for analysis in Excel
- Converting a test case table from a Confluence wiki page to a CSV for import
- Pulling data from a pull request description table into a spreadsheet
- Processing documentation tables in a data pipeline
- Migrating content from a Markdown-based wiki into a database or CMS
Frequently Asked Questions
The converter supports standard GitHub-Flavored Markdown (GFM) pipe tables — the format with | separators, a header row, and a separator row of dashes and colons. This is the most common format produced by GitHub, GitLab, Obsidian, Typora, and documentation tools.
The converter detects rows that start with a pipe character. If your Markdown table does not use leading pipes, add them before converting or use the "trim" option to handle variations. Most modern Markdown editors produce tables with leading pipes.
If a cell contains a literal pipe escaped as \|, the converter treats it as a regular pipe character in the cell value, not a column separator. Unescaped pipes inside cells would be treated as column boundaries and produce an extra column.
Yes. The separator row (e.g. |:--|--:|:--:|) is automatically identified and skipped — it does not appear in the CSV output. Alignment markers are purely a display instruction for the Markdown renderer and carry no meaning in CSV.
No. The converter splits the pasted text on newlines and processes each row as a string — it handles tables of any number of rows and columns. Very wide tables with many columns produce a CSV with many fields, but there is no enforced row or column limit.