CSV to Markdown Table

What the CSV to Markdown Table Does

Paste comma-separated data and the tool emits a Markdown table you can copy or download as table.md. It opens on a small example and updates as you type.

It's the fast way to drop tabular data into a README, an issue, a pull request or a doc, where a pipe table renders as a real, formatted table instead of a wall of commas.

How It Works

It parses the CSV with the RFC 4180 rules — so quoted fields with commas inside are handled — takes the first row as the header, writes a separator row of hyphens beneath it, and lays out each remaining row between pipe characters.

The result is GitHub-Flavored Markdown (GFM) table syntax: pipes separating the columns and hyphens marking the header. Most Markdown renderers understand it, even though core Markdown and CommonMark define no table syntax at all.

Data source & conversion logic

No external data. The CSV is read per RFC 4180 and rewritten as a GitHub-Flavored Markdown (GFM) table — pipes with a hyphen separator row — all in your browser.

1. Step 1. Parse the CSV per RFC 4180, handling quoted fields.
2. Step 2. Take the first row as the table header.
3. Step 3. Write a separator row of hyphens, one cell per column.
4. Step 4. Write each remaining row as a pipe-delimited table row.
5. Step 5. Copy the Markdown or download table.md.

Privacy

The CSV you paste is converted in your browser; nothing is uploaded.

Nothing is stored — it's gone when you close the tab.

Technical Details

Standards & references

• GitHub Flavored Markdown (GFM) tables — the pipe-and-hyphen table syntax this produces. Tables are a GFM extension popularised by GitHub, not part of core Markdown.
• RFC 4180 — the CSV reading rules — comma delimiter with double-quoting for fields that contain commas.
• CommonMark — the core Markdown spec, which defines no table syntax — which is why pipe tables come from GFM rather than CommonMark.

Accuracy & Limitations

It produces GFM table syntax, which isn't part of core Markdown or CommonMark. So it renders on GitHub, GitLab and most modern Markdown engines, but a strict CommonMark-only renderer will show the raw pipes instead of a table.

A cell that itself contains a pipe character will break the table, because the pipe is the column delimiter. Remove or escape pipes in your data first.

It doesn't add column alignment — GFM's optional colons in the separator row — so every column uses the renderer's default alignment.

The first row is always treated as the header; there's no header-less table option.

Real-World Use Cases

When to use it — and when not to

Target renders only strict CommonMark? Keep the data as HTML or CSV. Need column alignment or piped data handled? Add the alignment colons and escape the pipes by hand after converting.

Frequently Asked Questions

References

• Organizing information with tables (GitHub Docs)
• GitHub Flavored Markdown spec (tables extension)
• RFC 4180 — Common Format for CSV Files (RFC Editor)

Related Tools