Markdown Table Generator

Overview

Builds a GitHub-Flavored-Markdown table visually: set the number of columns and rows, pick an alignment, type the cells into a spreadsheet-like grid, and copy a pipe-delimited Markdown table whose columns are padded to line up in the raw source as well as in the rendered output.

How It Works

Choose columns (1-10) and rows (1-30) with the number fields, then pick left, center or right alignment. Type into the grid; the first row is the header row and each cell has a placeholder showing its default H-column name. When you change the size, the tool migrates the cells you already typed into the new grid instead of wiping them. The Markdown source appears on the right, regenerated live, with a copy button above it.

Step-by-Step Usage Guide

1. Set Columns and Rows; defaults are a 3x3 grid.
2. Type the header into the first row and fill the body cells in the visual grid.
3. Pick the alignment; the rule row in the output switches between :---, :---: and ---:.
4. Copy the generated Markdown and paste it into your document inside normal paragraph flow.

Technical Specifications & Standards

The generator writes GFM correctly rather than approximately. Column widths are computed as the longest cell in each column including the H-prefixed header, floored at five characters, and every cell is padded with trailing spaces so all pipes line up vertically in the raw text — a nicety many generators skip and that human editors appreciate in diffs. Alignment is expressed with the spec's colon syntax: a leading colon for left, trailing for right, both for center, with the rule row never shorter than three dashes per column. Resizing is handled by re-projecting the old cell array onto the new column count, so widening or shrinking keeps your typed data where it fits. One real limitation: cell text is inserted verbatim, so a pipe character typed inside a cell will break the table's column structure, and a line break inside a cell cannot be represented in Markdown at all — keep cell content to a single line and avoid pipes.

Targeted Use Cases

• Producing comparison tables, API parameter lists and config reference tables for GitHub READMEs and GitLab wikis.
• Keeping a table readable in raw form during code review, since the padded pipes align columns in diffs.
• Converting a spreadsheet row set into Markdown without hand-typing separators.
• Teaching the GFM table syntax, where the alignment colon positions are visible in the generated rule row.

Notes & Gotchas

• Never type a literal pipe character inside a cell; it will be treated as a column separator and corrupt the table.
• Use left alignment for prose columns and right alignment for numbers — it is what readers expect.
• Keep header cells short; they set the minimum width of their column in the padded output.
• Regenerate rather than hand-editing: fixing alignment manually is error-prone, and the tool recomputes widths on every change.

Frequently Asked Questions