CSV to Markdown Table Converter

Parse delimited rows into Markdown tables while preserving quoted fields and flagging dialect ambiguity.

CSV Input

Paste CSV, TSV, semicolon-separated, or pipe-separated data. Quoted values and commas inside quotes are supported.

Table choices

Delimiter

Output

Headers

Alignment

Trim leading and trailing whitespace in cells (changes values)Escape pipe characters inside cellsNormalize uneven rowsKeep blank physical lines as empty rows

Auto detection is a best-effort guess across the first records. Pick the delimiter manually when a file uses an unusual dialect or a single column.

Converted Output

Markdown table output will appear here.

Parsing and conversion run in your browser. Pasted rows are not sent to a Yoryantra server by this page.

CSV looks simple until the rows stop being simple

A comma is only a separator when it is outside a quoted field. Quotes inside a quoted field are doubled, and a quoted field may contain a line break. Those details are why splitting a CSV row on every comma breaks as soon as an address, sentence, or exported note contains one.

RFC 4180 documents the widely used comma-separated conventions and thetext/csvmedia type, but it is informational rather than a universal CSV standard. Semicolon, tab, and pipe inputs are treated here as related delimited-text dialects. RFC 4180

Auto-detect is a clue, not a guarantee

Delimiter detection compares comma, semicolon, tab, and pipe counts across several complete records while ignoring separators inside quoted fields. A file with one column, mixed delimiters, or only one short record can still be ambiguous, so the result calls that out instead of pretending the guess is certain.

If an export came from software that already tells you its delimiter, selecting it manually is safer than relying on detection.

Whitespace and uneven rows are data decisions

Leading and trailing spaces are preserved by default because RFC-style CSV treats spaces as part of an unquoted field. Turning on trimming is convenient for messy exports, but it deliberately changes cell values.

Row normalization pads short rows so every Markdown row has the same number of cells. It never discards a longer row: the widest parsed row determines the table width. A line containing separators such as,,is kept as a real record even when all of its cells are empty; the “blank physical lines” option applies only to genuinely blank lines.

Markdown tables have a different set of constraints

Pipe tables are an extension used by GitHub Flavored Markdown rather than part of core CommonMark. GFM expects a header row plus a delimiter row, uses colons for alignment, and treats an unescaped pipe as a cell boundary. GFM table syntax

Embedded CSV line breaks are written as<br>so one CSV record stays on one Markdown table row. That relies on the destination renderer accepting inline HTML. Cell text is otherwise preserved; HTML from the source is not sanitized, so review untrusted content before publishing it in a renderer that permits raw HTML.

A quoted field that should survive intact

CSV

Name,Note
Sneha,"Pune, Maharashtra"
Varoun,"Said ""ship it"" today"

Markdown

| Name | Note |
| :--- | :--- |
| Sneha | Pune, Maharashtra |
| Varoun | Said "ship it" today |

When a table is the wrong shape

Very wide or very long datasets are technically convertible but often make poor documentation tables. The page flags those shapes so you can decide whether a short summary, downloadable data file, or smaller selection communicates the information better.