All tools

Markdown Table Column Aligner

Code

Reformat every GitHub-Flavored-Markdown pipe table in a document so each column's pipes line up visually, preserving left/center/right alignment markers and rebuilding the delimiter row to match

Paste a Markdown document containing one or more GitHub-Flavored-Markdown pipe tables and get back the same document with every table's columns realigned: cells padded to the widest content in their column, the delimiter row's dashes rebuilt to match, and each column's left, center, or right alignment marker preserved exactly as declared. Tables inside fenced code blocks are left untouched, since GitHub's own renderer treats those as literal text rather than a real table. A row with a different number of cells than the header gets padded or truncated to match, with a warning so you notice the mismatch instead of silently losing data.

markdowntableformattingdocumentationgfm

How to use Markdown Table Column Aligner

  • 1.Paste a Markdown document with one or more pipe tables, or try the sample table.
  • 2.Review the aligned output and the per-table summary showing column count, row count, and detected alignment.
  • 3.Copy the aligned output back into your document; unrelated text and code blocks are left exactly as they were.

Frequently asked questions

Does this change what the table looks like when rendered?
No. Extra whitespace inside a pipe table cell has no effect on GitHub's or any other CommonMark renderer's output, this only makes the raw Markdown source easier to read and diff in a text editor.
What happens to a row with more or fewer cells than the header?
It's padded with empty cells if it has too few, or truncated if it has too many, so the table stays valid, and a warning is returned naming the affected row so you can check whether that was intentional.
Does it handle a cell containing a literal pipe character?
Yes, as long as the pipe is escaped as \\| in the source, which is how GFM itself requires literal pipes to be written inside a table cell; an unescaped pipe is treated as a column separator, same as any Markdown renderer would.
Will columns line up perfectly for non-English text?
Column width is measured in characters, not rendered pixel width, so a column mixing plain ASCII with wide characters (CJK, emoji) may not line up pixel-perfectly in every font even though the character counts match exactly.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/markdown-table-aligner \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"markdown":"| Name | Age |\n|---|---|\n| Alice | 30 |\n| Bob | 7 |\n"}'

Get an API key from your dashboard · Full API docs →

Related tools

HTML Table GeneratorGenerate HTML and Markdown tables from CSV, TSV, or pipe-delimited dataCodeMarkdown Table of Contents GeneratorScan a Markdown document's ATX headings and build a nested table of contents with GitHub-style anchor slugs, disambiguating duplicate headings automaticallyCodeMarkdown Task List Progress CalculatorParse a Markdown document's checkbox task list and report completion percentage overall and per section, grouped by the nearest preceding headingCode