Guide
Making Markdown tables from spreadsheet data for READMEs and docs
Markdown tables are simple in theory and tedious in practice: every row needs pipes in the right place, the separator line needs dashes and colons, and one stray pipe in a value breaks the whole table. This tool converts spreadsheet data into a correct, neatly formatted Markdown table you can paste into a README, a wiki page, documentation or a forum post.
Getting the data in
The quickest way is to copy cells in Excel, Google Sheets or Numbers and paste them into the paste box; they arrive tab-separated and are recognized automatically. CSV, TSV and Excel files work too. The first row becomes the table header. If your data has no header row, switch that option off, and generic column names are added, because Markdown tables always need one.
Alignment
Markdown sets alignment per column in the separator line: a colon on the left for left alignment, on the right for right alignment, on both sides for centered. “Numbers right” right-aligns columns that contain only numbers, such as prices and counts, and left-aligns the rest, the usual convention for readable tables. You can also force left, center or right everywhere, or leave alignment unset.
Escaping
A pipe inside a value would end the cell early, so pipes are escaped with a backslash, and existing backslashes are doubled. Markdown table cells cannot contain real line breaks; any line breaks in your data become <br> tags, which GitHub and most renderers display as a new line inside the cell.
Padded source
With padding on, every column is filled with spaces to the width of its longest value, so the Markdown source lines up like a table even before it is rendered. That makes the file easier to read and edit by hand, and code reviews show clean, small diffs when one value changes. Switch padding off for the most compact output.
Preview and export
The rendered preview shows how the table will look. Copy the Markdown with one click or download it as an .md file.
Limits of Markdown tables
There are no merged cells, no row headers, no column widths and no multi-paragraph cells. For complex layouts, an HTML table gives more control; most Markdown renderers accept HTML directly.
Typical uses
Feature comparison tables in READMEs, parameter lists in API documentation, changelogs with version and date columns, benchmark results, and price or schedule tables in wiki pages or blog posts written in Markdown.
Wide tables
Tables with many columns become hard to read on narrow screens, and GitHub shows them with a horizontal scrollbar. Consider dropping columns first with Edit CSV Columns, or splitting a wide table into two focused ones.
Updating tables in documentation
Keep the data in a spreadsheet and regenerate the Markdown when it changes, rather than editing pipes by hand. Padded output keeps the diff readable, so reviewers see which values changed.
Privacy
The data is converted in your browser and never uploaded, so internal figures can be formatted safely.
Related tools
For web pages and emails, CSV to HTML Table produces table markup with optional styling. Write and preview whole documents in the Markdown Editor, or turn them into a PDF with Markdown to PDF.
Checked against the current version of the CSV to Markdown Table on .

