Paste CSV — or a block copied straight out of Excel — and get an aligned GitHub-flavored Markdown table back.
Commas, tabs or semicolons — detected automatically. Runs in your browser.
Converted — share it as a page.
Publish this as a live page in one click. No account to start.
Turning a spreadsheet into a Markdown table by hand is the kind of task that is trivial for three rows and unbearable for thirty: every field needs a pipe on each side, the header needs its --- separator, and one missed pipe silently breaks the whole table. Paste the data here and it is done in one step. The parser follows RFC 4180, so a quoted field containing commas, quotes, or line breaks stays one cell instead of shattering into several — the case that defeats most find-and-replace attempts. It also detects the delimiter, which matters more than it sounds: copying cells out of Excel or Google Sheets puts tab-separated text on your clipboard, not commas, and European exports commonly use semicolons. The reverse direction is on the Markdown table to CSV page.
Paste your CSV, or copy a block of cells straight out of a spreadsheet — commas, tabs and semicolons are all detected.
The first row becomes the table header, because a Markdown table requires one, and the --- separator row is written for you.
Copy the table into your README or docs, download it as .md, or publish it as a page.
An analyst has a 30-row export of regional revenue and needs it in the team README so it renders on the repo home page. The export is real CSV, which means the revenue figures are quoted because they contain thousands separators — "1,240,000" — and one notes column contains a quoted comment with a comma in it. A quick find-and-replace of commas for pipes would tear every one of those cells in half. Pasting the file here gives back a table where each quoted field is a single cell, the header row and separator are in place, and the one cell that contained a literal pipe character has been escaped so it cannot break the column layout. They paste it into the README, push, and the table renders on GitHub the way the spreadsheet looked.
Because a copy out of a spreadsheet is not comma-separated at all; it is tab-separated. The converter looks at your input and picks the delimiter that splits every row into a consistent number of columns, which lands on tabs for a spreadsheet copy, commas for a real .csv, and semicolons for exports from locales where the comma is the decimal separator. You never have to tell it which one you have.
They survive. A field wrapped in double quotes is treated as one cell no matter what is inside it, and a doubled quote ("") is read as a literal quote character — that is what the CSV standard specifies and it is exactly what naive comma-splitting gets wrong. A line break inside a quoted cell becomes <br>, since a Markdown table row cannot span lines.
Effectively yes. GitHub-flavored Markdown has no headerless table syntax — every table has a header row followed by the --- separator — so the first row is used as one. If your data has no header, add a row of column names before pasting, or accept that your first data row will be styled as the header.
Short rows are padded with empty cells to match the widest row, so the table stays valid and you can see the gaps. The alternative — truncating to the narrowest row — would silently delete data, which is far worse than showing you a few blank cells.
No. Parsing happens in your browser as you type, and nothing is transmitted unless you press Publish, which hosts the table as a page at its own link. That matters given how often the tables people convert are revenue, headcount, or customer lists.
免費帳號的連結保留 7 天。升級付費方案後，你建立的每個頁面都會永久上線。
查看方案與價格