CSV to Markdown Table

Paste a CSV and get a Markdown table ready for a README, a pull request or documentation. Columns are padded to a common width so the source is readable where you will actually edit it, and pipes inside cells are escaped — that last one is the failure most converters miss, because an unescaped pipe ends the cell and silently splits your value into two columns. Alignment is set per table with left, center or right, written as the colons in the separator row. The input is parsed as real CSV, so a quoted field containing a comma stays one cell rather than becoming two. Drop a folder of files and get them all back as a ZIP; nothing is uploaded.

What the separator row means

SeparatorAlignment
---Left — Markdown's default
:---Left, stated explicitly
:---:Center
---:Right

When to use it

  1. Turn a spreadsheet export into a table for a README.
  2. Paste data into a GitHub issue or pull request as a table.
  3. Build a comparison table for documentation from a CSV.
  4. Convert query results into Markdown for a write-up.
  5. Produce a table for a static-site post from exported data.

How to Use

  1. Paste your CSV, or drop files in.
  2. Choose the column alignment.
  3. Copy the Markdown, or download the batch as a ZIP.

Features

  1. Pipes inside cells escaped automatically
  2. Left, center or right alignment
  3. Columns padded so the source stays readable
  4. Separator row always valid, never under three dashes
  5. Quoted CSV fields parsed correctly
  6. Bulk folders with ZIP download, all client-side

FAQs

What happens to a pipe inside my data?

It is escaped as \|. Left alone, a pipe ends the cell, so a value like 'yes | no' becomes two columns and knocks the rest of the row out of alignment. This is the most common way a generated Markdown table breaks.

Why are the columns padded with spaces?

No parser needs it, but a person editing the source does. An unpadded table is unreadable in raw Markdown, and raw Markdown is where it gets edited.

How do I set column alignment?

Pick left, center or right, and the colons are written into the separator row. Left is Markdown's own default, which is why a plain --- separator behaves as left-aligned.

What if a cell contains a line break?

It becomes a space. Markdown tables have no multi-line cell, and a raw line break would end the row early. If you need a visible break, HTML's <br> works in most renderers.

Is my data uploaded?

No. Conversion happens in your browser.

Technical Details

Two details separate a Markdown table that works from one that looks right in the box and breaks when rendered. The first is the pipe: a pipe inside a cell ends that cell, so a value like 'yes | no' silently becomes two columns and pushes the rest of the row out of alignment. Every pipe is escaped on the way out. The second is the separator row, where colons set the alignment. Carving the colons out of a fixed-width run of dashes can leave only two, and several parsers reject a two-dash separator outright, so the colons are added to at least three dashes rather than taken from them. Cells are padded to a common column width, which no parser requires and every human editing the source does. A newline inside a cell is flattened to a space, because Markdown tables have no row-spanning cell and a raw line break would end the row. Input is parsed as full RFC 4180 rather than split on commas, so a quoted field containing a comma stays one cell. Everything runs in your browser.

Data & CSV Tools

Data & CSV Tools

  • CSV to JSON
  • JSON to CSV
  • YAML to JSON
  • CSV Graph Plotter
  • YAML Formatter & Validator
  • XML to JSON
  • Query String to JSON
  • Config to JSON