CSV to Markdown Table

Q: What happens to a pipe character inside a cell?

It gets escaped as a backslash pipe, because an unescaped pipe ends the column. This is the single most common way a generated Markdown table comes out mangled — a cell containing something like "yes | no" silently splits into two columns, shifting everything after it and leaving the row a different width from its neighbours. Any value that might contain a pipe needs escaping, and doing it by hand across a large table is exactly the sort of job worth automating.

Q: Can a cell contain a line break?

Not literally — a Markdown table row must occupy a single line, so a genuine newline inside a cell breaks the table. The conventional workaround is to replace it with a br tag, which most Markdown renderers pass through to HTML and display as a line break. That is what this tool does. It is a compromise rather than a real solution, so if your data has substantial multi-line content a table may be the wrong presentation for it.

Q: Why are the columns padded with spaces?

Because it makes the raw Markdown readable to whoever opens the file next, which is the whole reason to write a table in Markdown rather than HTML. Renderers ignore the padding entirely, so it has no effect on the output — the choice is purely about the source. Padding is on by default and can be turned off, which is worth doing for very wide tables where the alignment costs more bytes than it saves in readability.

Q: How do I control column alignment?

Through the colons in the separator row, which this tool writes for you. A colon on the left aligns left, on the right aligns right, and on both sides centres. Right alignment is worth setting for numeric columns — it lines the digits up so magnitudes are comparable at a glance, which is the main readability gain a table gives you over a list. Alignment is a rendering hint, so a renderer that does not support it simply ignores it.

Q: Which Markdown flavours does this work with?

Tables come from GitHub Flavored Markdown rather than the original specification, so they work anywhere GFM is supported — GitHub, GitLab, most static site generators, Obsidian, Notion and the majority of documentation tools. They do not work in strict CommonMark or original Markdown, where the table will render as literal text. If your target is one of those, you need an HTML table instead.

Q: Does it handle a CSV with quoted fields and embedded commas?

Yes. It uses a proper RFC 4180 parser rather than splitting on commas, so a quoted field containing commas, quotes or newlines is read as the single value it is. The delimiter is also detected automatically, so a semicolon-separated export from a European spreadsheet or a tab-separated paste both work without you having to say which is which.

Turn CSV into a GitHub-flavoured Markdown table, with pipes escaped, newlines handled and columns aligned.

CSV

Delimiter

First row is a header Pad columns for readable source

Markdown table

Conversion happens entirely in your browser. Nothing you paste is uploaded, which makes this safe for data you would not put into an online converter.

What It Does

Paste a CSV and get a Markdown table you can drop straight into a README, a pull request or a documentation page. The conversion looks trivial and mostly is, except for the two details that make hand-written tables come out broken. A pipe character inside a cell ends the column unless it is escaped, so a value like "pass | fail" silently splits the row and shifts every column after it. And a genuine line break inside a cell cannot exist at all, because a table row must occupy one line — so it becomes a br tag instead. Beyond that the tool pads the columns so the raw source is readable, lets you set per-column alignment, and reads the CSV with a real parser so quoted fields containing commas survive intact.

When to Use It

A spreadsheet of configuration options or API parameters needs to go into a README as a table.
You are writing release notes and want a table of changes from data you already have in CSV.
A support ticket needs data presented readably and the system accepts Markdown.
You are documenting a schema and the field list already exists as an export.
A wiki page needs a table and retyping thirty rows by hand is not a reasonable use of an afternoon.

Worked Examples

name,role,active
Jane Doe,Engineer,true
Sam Smith,Designer,false

The straightforward case. Three columns, two rows, padded so the raw Markdown lines up — which is the point of writing it in Markdown rather than HTML.

check,result
login,pass | with warnings
signup,fail

The pipe trap. Without escaping, that cell would end its column early and leave the row one wider than the header, breaking the table. The tool escapes it so the value survives.

id;product;price
1;Widget;9.99
2;Gadget;19.50

Semicolon-separated, as European spreadsheet exports usually are. The delimiter is detected automatically, and the price column can be right-aligned so the decimal points line up.

Features

GitHub Flavored Markdown table output

Pipes inside cells escaped automatically

Line breaks converted to br tags

Per-column alignment including right-aligned numbers

Column padding for readable source

Automatic delimiter detection

Proper RFC 4180 parsing of quoted fields

Optional header row handling

Row and column counts reported

Runs entirely in your browser

How to Use

1. Paste your CSV, or import a file. 2. The Markdown table appears immediately below. 3. Set alignment per column if you want numbers right-aligned. 4. Turn off padding for very wide tables where the source alignment is not worth the bytes. 5. Copy the result into your README or documentation.

Common Mistakes

Forgetting to escape pipes. A single unescaped pipe in a cell shifts every column after it, and the resulting table looks broken in a way that is hard to trace back to one value.
Putting a real line break in a cell. A table row must be one line, so the table simply ends there — use a br tag if the content genuinely needs a break.
Splitting the CSV on commas. Any quoted field containing a comma comes apart, which is why a real parser matters even for a job this simple.
Using a Markdown table where GFM is not supported. Tables are a GitHub extension, so in strict CommonMark the whole thing renders as literal text.
Left-aligning numeric columns. Right alignment lines the digits up, and comparing magnitudes at a glance is most of the value a table provides.

Frequently Asked Questions

What happens to a pipe character inside a cell?

Can a cell contain a line break?

Why are the columns padded with spaces?

How do I control column alignment?

Which Markdown flavours does this work with?

Does it handle a CSV with quoted fields and embedded commas?