Markdown Table to CSV / TSV Converter | Paste a pipe table, get a spreadsheet-ready file

Convert Markdown pipe tables into CSV or TSV with RFC 4180 auto-quoting. Cells containing commas, quotes, or newlines are escaped correctly so you can paste straight into Excel, Google Sheets, or load with pandas.

💡 About this tool

A Markdown pipe table is great for prose, but when you drop it into a spreadsheet it lands as a single column of text. This tool detects the | --- | separator row, splits each remaining row on unescaped pipes, and emits a proper CSV or TSV stream that spreadsheet apps and data libraries will parse as rows and columns.

Cells with commas, double quotes, or embedded newlines are wrapped in double quotes following RFC 4180, with internal quotes doubled (" → ""). This means a cell like Smith, John survives the round-trip without splitting into two columns. The output panel shows row and column counts so you can sanity-check the shape before pasting downstream.

🧐 Frequently Asked Questions

Q. Does the separator row (| --- |) have to be present? A. Yes — the separator row is how the tool tells "this block is a table" apart from prose lines that happen to contain pipes. Alignment indicators like | :---: | or | ---: | are also recognized and stripped from the output.

Q. How do I include a literal | in a cell? A. Escape it as \| per the Markdown spec. The parser replaces escaped pipes with an internal placeholder before splitting columns, then restores them, so \| survives as | in the final CSV cell.

Q. CSV vs TSV — which one should I pick? A. Use TSV when pasting into Excel or any locale-sensitive spreadsheet, because tab delimiters are unambiguous. Use CSV when feeding pandas.read_csv, BigQuery, or any tool that expects RFC 4180. TSV also avoids the "regional CSV" headache where some Excel locales expect ; as the delimiter.

Q. Does it handle tables I copied out of GitHub or Notion? A. Yes. Both render pipe-delimited tables, and the parser ignores any non-pipe surrounding prose, so you can paste a region that includes paragraphs and the tool will only extract the table rows.

Q. What happens with multi-line cells (newlines inside a cell)? A. Markdown tables technically don't support raw newlines in cells (you have to use <br>), but if your input does contain \n inside a cell the tool will still quote-escape it per RFC 4180. The resulting CSV opens correctly in Excel and pandas, both of which honor quoted newlines.

Q. Will leading or trailing pipes confuse the converter? A. No. Rows are trimmed of empty leading/trailing cells caused by the outer |, which is the convention most Markdown writers use. Tables written without outer pipes (just inner separators) work too.

📚 Fun Facts

CSV predates almost every modern file format people complain about — it was already in use in IBM Fortran in 1972, decades before any formal spec existed. RFC 4180, the 2005 document that defines CSV's quoting and line-ending rules, is famously short (eight pages) yet still leaves enough ambiguity that "every CSV parser disagrees about edge cases" is a running joke in data engineering.

TSV is older still as a convention and shows up surprisingly often in bioinformatics, where tab-delimited is the default for reference data files (BED, GTF, VCF — all tab-separated). If you're handing converted data to a bioinformatician, picking TSV here usually saves a round of "can you re-export this?".