What happens to a cell containing a comma?

Nothing, as long as the CSV quoted it properly. The parser respects quoted fields, so a quoted cell containing commas stays intact as one cell.

Can a cell contain a line break?

Not in a Markdown table — the format is strictly one row per line. Line breaks inside a cell are replaced with a space, or with a break tag if your renderer accepts inline HTML.

Does the padding affect how it renders?

No. It exists so the Markdown source is readable to the next person who opens the file. The rendered output is identical either way.

My export uses semicolons rather than commas.

Set the delimiter accordingly. Semicolon-separated files are standard in locales where the comma is the decimal separator, which covers most of Europe.

CSV to Markdown Table

Paste a CSV, get a formatted Markdown table.

Everything runs inside your browser. Your files never leave your device.

Input

Result

The result appears here as you type.

Ask about CSV to Markdown Table

Questions about what this tool does, which option to pick, or what it can and cannot handle.

The question you type here is sent to an AI provider to be answered — your files and whatever you put in the tool above are not, and the assistant cannot see them. Answers are generated and can be wrong. The tool itself is not guessing: it runs deterministic code on your device.

About the CSV to Markdown Table

Pasting tabular data into a README, a pull request description, an issue or a wiki page means converting it to a Markdown table, and doing that by hand means counting pipes.

This takes CSV — from a spreadsheet export, a database query, or a copied selection — and produces the table syntax, aligned so the source is readable as well as the rendered result.

Column alignment is set with colons in the separator row, and the tool writes them for you: left by default, or right for numeric columns, which is how a column of figures becomes readable. Aligning numbers on their right edge lines up the digits, and a column of prices or counts is genuinely hard to scan without it.

Two details in the escaping matter. A pipe character inside a cell would end the cell early, so it is escaped. And a cell containing a newline cannot be represented at all — Markdown tables are strictly one row per line — so line breaks within a cell are replaced with a space or an HTML break tag depending on what your renderer supports.

The alignment padding in the output is cosmetic and worth keeping anyway. It makes no difference to how the table renders, but it makes the Markdown source legible to whoever opens the file next, which is the whole reason to write a table in Markdown rather than in HTML.

Delimiters other than commas are handled, since exports from European locales frequently use semicolons — a consequence of the comma being the decimal separator there.

How to use it

1Paste your CSV, including the header row.
2Check the delimiter if the data came from a European export, where semicolons are common.
3Set numeric columns to right alignment so the digits line up.
4Copy the table into your Markdown file. The padding is cosmetic but keeps the source readable.

Questions

What happens to a cell containing a comma?: Nothing, as long as the CSV quoted it properly. The parser respects quoted fields, so a quoted cell containing commas stays intact as one cell.
Can a cell contain a line break?: Not in a Markdown table — the format is strictly one row per line. Line breaks inside a cell are replaced with a space, or with a break tag if your renderer accepts inline HTML.
Does the padding affect how it renders?: No. It exists so the Markdown source is readable to the next person who opens the file. The rendered output is identical either way.
My export uses semicolons rather than commas.: Set the delimiter accordingly. Semicolon-separated files are standard in locales where the comma is the decimal separator, which covers most of Europe.