Convert and check the CSV
- Paste the CSV into the Markdown Table Generator and choose comma input if auto-detection selected the wrong delimiter.
- Keep First row is header selected for a normal spreadsheet export, or clear it to generate neutral column labels.
- Fix any quoted-field or uneven-row error named by the converter.
- Review the plain cell preview, then copy the Markdown and check its final rendering in GitHub.
Example with commas, pipes, quotes, and a line break
Quoted CSV fields can safely contain commas, doubled quotes, and line breaks. A literal pipe needs a backslash in the Markdown output because GitHub uses pipes to separate cells.
Name,Team,Note Ada,"Research, Data","Uses A | B" Grace,QA,"Said ""ready"" and shipped" | Name | Team | Note | | --- | --- | --- | | Ada | Research, Data | Uses A \| B | | Grace | QA | Said "ready"<br>and shipped |
Keep quoted commas and doubled quotes together
A comma inside a CSV value must be wrapped in double quotes so it does not start a new cell. A double quote inside that field is represented by two double quotes.
Comma mode checks these quoting rules before it generates output. An unclosed quote or text after a closing quote stops conversion instead of producing a shifted table.
Escape pipes and preserve line breaks
GitHub uses the pipe character to separate table cells. The converter writes a literal pipe as \| so the value stays in one cell.
When a quoted CSV field contains a line break, the converter writes <br> in the Markdown output. Check the final result in GitHub because the local preview shows plain cell boundaries rather than every Markdown rendering rule.
Fix uneven rows before copying
Every CSV record must contain the same number of cells as the first record. If a row has too many or too few cells, the converter names the row and shows the expected and actual counts.
Check for an unquoted comma, a missing value, or the wrong delimiter. The converter leaves the Markdown output empty until the record widths match.
Check the GitHub table rules
GitHub tables use a header row, a separator row with at least three hyphens per column, and pipe characters between cells. Put a blank line before the table so GitHub renders it correctly.
Alignment markers belong in the separator row: :--- for left, :---: for center, and ---: for right.
When the source is TSV or pipe-delimited
Tab-separated input can be easier when values contain commas. Pipe mode is useful for simple pipe-delimited rows.
CSV quoting rules apply only to comma mode. Tab and pipe modes split physical lines, so use comma mode when a quoted cell contains a line break.
FAQ
How do I align columns in a Markdown table?
Put colons in the separator row: :--- for left, :---: for center, and ---: for right alignment.
How do I put a pipe character inside a Markdown table cell?
Escape the pipe as \| so GitHub treats it as cell text instead of a separator. The Markdown Table Generator does this automatically.
Why did my CSV row create too many Markdown columns?
A comma inside a value may be missing CSV quotes, or a record may contain an extra cell. Use comma mode and fix the row named by the error before copying the output.
Can a CSV cell contain a line break?
Yes, when the CSV field is quoted. The converter preserves that line break as <br> in the generated Markdown.
What if my CSV does not have a header row?
Clear First row is header. The converter creates Column 1, Column 2, and similar labels so your first data row remains in the table body.