Build markdown tables in a spreadsheet-style editor. Paste from Excel or Sheets. Live preview.
Build properly-formatted Markdown tables by editing cells directly — add rows, add columns, set column alignment, paste in CSV or TSV data, and copy the resulting Markdown source. Useful for documentation, GitHub READMEs, blog posts, and any place Markdown tables render. Everything runs locally in your browser; nothing is uploaded.
Markdown tables are a non-standard but near-universal extension to the Markdown spec. They use pipes (|) to separate columns and dashes (-) to mark the header divider:
| Name | Role | Status |
| --- | --- | --- |
| Alice | Designer | Active |
| Bob | Developer | Active |Every major Markdown renderer (GitHub, GitLab, Bitbucket, Discord, Slack, Notion, Obsidian, MkDocs, Jekyll, Hugo) supports this syntax. The original Markdown spec by John Gruber doesn't include tables, so technically Markdown tables are an extension called "GFM tables" (GitHub Flavored Markdown), but the syntax is so widespread it's effectively standard.
Hand-writing Markdown tables is tedious because the column widths matter for readability of the source. A table with 3-character cells next to 30-character cells looks ugly when the pipes don't line up — even though renderers don't care. The Markdown Table Generator handles the formatting automatically, producing source that renders correctly and reads cleanly.
Documenting API parameters. Almost every README and API doc has a parameter table: name, type, description, default value. The generator builds these in seconds.
Comparison tables in blog posts. "Tool X vs Tool Y" comparisons render as tables. Markdown tables work in Substack, Medium (with effort), Ghost, Hashnode, and dev.to.
Pricing tables in product documentation. Plan name, monthly cost, annual cost, included features. Tables organize this much better than prose.
Configuration reference tables. Setting name, type, default, description. Standard format for tools, libraries, and frameworks.
Status reports and project overviews. Task, owner, status, due date. Tables make scannable status documents.
Test result summaries. Test name, expected, actual, pass/fail. Markdown tables in test reports get rendered nicely by most CI/CD systems.
Feature comparison matrices. Feature, free tier, pro tier, enterprise tier. Tables are the only sensible format for this.
Schema documentation for databases or APIs. Field name, type, nullable, description. Long tables work fine — Markdown tables don't have a maximum size.
The generator accepts pasted CSV (comma-separated) and TSV (tab-separated) data. When you copy a range from Excel, Google Sheets, or Numbers, the clipboard contains TSV by default. Paste into the generator and the rows and columns are parsed automatically.
This makes the typical workflow extremely fast: build a table in your spreadsheet (where editing many cells is comfortable), copy, paste into the generator, copy the Markdown output, paste into your document. Three pastes total.
For CSV with quoted fields, the generator handles standard CSV escaping — quoted fields, escaped quotes inside quotes, embedded commas inside quoted fields. Edge cases (literal newlines inside quoted fields, BOM at file start) may need cleanup before paste.
Markdown tables support three alignment options through the syntax of the header divider row.
Left-aligned (default): | --- | — equivalent to plain dashes. Most renderers treat this as left.
Center-aligned: | :---: | — colons on both sides of the dashes signal center alignment.
Right-aligned: | ---: | — colon on the right of the dashes signals right alignment. Useful for numeric columns.
Alignment in the rendered output depends on the renderer. GitHub, GitLab, Hashnode, and most modern Markdown processors honor alignment markers. Older or simpler processors (some legacy CMSes) may ignore them and use default left alignment everywhere.
For numeric columns, right alignment makes the values line up at the decimal point and is much easier to scan. For column headers, center alignment looks balanced. For everything else, default left alignment is fine.
Pipes inside cell content. A literal pipe character inside a cell breaks the table syntax — the renderer thinks it's a column separator. Escape it as \| or use the HTML entity |. The generator handles this on output.
Newlines inside cells. Markdown tables don't support multi-line cell content directly. To include a line break inside a cell, use the HTML <br> tag. The generator's cell editor accepts <br> and preserves it in output.
Empty header row. Markdown tables require a header row even if all your data is body. If you don't have meaningful headers, use single-letter or empty headers. The header row is structural; rendering ignores its content if you leave it blank.
Mismatched column counts. Every row needs the same number of pipe-separated cells. The generator enforces this. Hand-written tables sometimes have rows with different column counts, which most renderers reject silently.
HTML inside cells. Most Markdown renderers allow basic HTML inside cells — <strong>, <em>, <a>, <br>, sometimes <code>. Some CMSes strip HTML for security; check what your target renderer supports.
Markdown formatting inside cells. Inline Markdown formatting works in most renderers: **bold**, *italic*, `code`, [link](url). Block-level Markdown (headings, lists, blockquotes) does not work inside cells.
Markdown tables — best for documentation, blog posts, and anywhere Markdown is the source format. Lightweight syntax, version-control-friendly, renders consistently.
HTML tables — necessary when you need cell merging (colspan, rowspan), nested elements, or styling. More verbose but more flexible. Use HTML tables in Markdown documents when Markdown table syntax isn't expressive enough.
Spreadsheet exports (CSV, TSV) — best for data interchange, automation, and analysis. Don't render directly in most contexts; need to be converted before display.
For documentation, Markdown tables are usually the right answer. Reach for HTML tables when you need merging or styling.
The generator presents an editable grid where you fill in cells, add rows and columns, and set column alignment. As you edit, the Markdown source updates live. Click "Copy Markdown" to copy the source to clipboard.
Pasted CSV or TSV is parsed by detecting the delimiter (tab if present, comma otherwise) and splitting rows on newlines. Quoted fields are handled per RFC 4180 conventions. Tabs inside quoted fields are preserved as literal tabs in the cell content.
The output is properly formatted Markdown — column widths normalized for readability of the source, alignment markers included, special characters escaped. The result renders identically in all major Markdown processors.
Build in a spreadsheet, format in the generator. Editing tables is much faster in a spreadsheet's grid view than in a Markdown editor. Build there, paste, format, copy, paste into your document.
Right-align numeric columns. Default left alignment makes numeric data harder to scan. The two-second cost of setting alignment pays off in readability.
Keep tables narrow when possible. A table that's wider than the rendered page width gets horizontal scrollbars or text wrapping that breaks the visual structure. For wide data, consider whether a list or several smaller tables would communicate better.
Use code formatting for code in cells. Wrap code samples in backticks so they render in monospace. Otherwise the renderer applies its body font and code looks like prose.
Some Markdown processors don't support tables (older versions, very minimal implementations). Check whether your CMS uses GitHub Flavored Markdown (which includes tables) or another flavor. If it doesn't, you may need HTML tables instead.
Use the HTML <br> tag inside the cell. Markdown tables don't natively support multi-line cells, but <br> works in most renderers.
Escape it as \| or use the HTML entity |. The generator handles this automatically when you type a pipe in a cell.
Paste the Markdown source into the input area; the generator parses it back into the editable grid. From there you can modify cells, add rows or columns, change alignment, and re-export.
No — Markdown table syntax doesn't support merging. For tables with merged cells, switch to HTML table syntax.
Yes, in most renderers. Bold, italic, inline code, and links all work inside cells. Block-level Markdown (headings, lists, blockquotes) does not.