Sarah Chen, SEO Content Strategist
What This Tool Does
This generator converts comma-separated (CSV) or tab-separated (TSV) data into a properly formatted GitHub-Flavored Markdown pipe table. Unlike a one-shot converter, it works live: edit the data on the left and the Markdown table on the right updates as you type, with a toggle between raw Markdown source and a rendered preview so you can verify the result before copying it.
Everything runs client-side. There is no upload step, no queue, and no server round-trip — which means it is fast, private, and works offline once the page has loaded.
How to Use It
- Paste your data into the input box, upload a
.csv/.tsvfile, or paste a range copied directly from Excel or Google Sheets. - Confirm the delimiter. Leave it on auto-detect, or pick comma, semicolon, tab, or pipe explicitly.
- Set the header. Keep "First row is header" on if your data has column titles, or turn it off to auto-generate
Column 1,Column 2headers. - Adjust alignment per column from the output toolbar, then copy the Markdown or download it as a
.mdfile.
Developer Features
- RFC 4180 parsing: correct handling of quoted fields, escaped quotes, embedded delimiters, and multi-line cell values.
- Smart delimiter detection that ignores delimiters inside quotes, so it is not fooled by commas in addresses or descriptions.
- Per-column alignment written as GFM colon syntax in the separator row.
- Pretty-aligned source with monospace-aware padding (including wide CJK characters) for readable raw Markdown, or compact output when you prefer minimal diffs.
- Live HTML preview rendered with a GFM-compliant parser.
- One-click copy and download, plus live row and column counts.
GFM Table Syntax
A GitHub-Flavored Markdown table has three parts: a header row, a separator row, and one or more data rows, all delimited by pipe characters. The separator row controls alignment — :--- for left, :---: for center, and ---: for right. This tool generates all three parts for you and keeps the pipe counts consistent so the table never renders broken.
Common Use Cases
- READMEs and docs: turn a config or parameter spreadsheet into a table for a repository README or docs site.
- Pull requests: paste query results or benchmark numbers into a PR description as a clean table.
- Changelogs: convert a release tracking sheet into a version table that diffs cleanly in Git.
- Issue reports: drop database exports into a GitHub issue without the formatting falling apart.
Tips for Clean Tables
- Keep headers short — long column titles force wide source lines that are hard to read in raw Markdown.
- For very large datasets, consider splitting the data; GFM tables with thousands of rows are valid but unwieldy to edit.
- If a cell legitimately needs a line break, the tool converts it to
<br>, which renders as a line break inside the cell on GitHub. - Save source files as UTF-8 so accented characters and symbols survive the conversion.
