Align Markdown tables
Pad cells to consistent widths, line up every pipe, and preserve per-column left / centre / right alignment markers. Produces clean raw tables.
| name | qty | price | | ---------- | --: | :---: | | pear | 3 | 1.20 | | banana | 12 | 0.40 | | watermelon | 1 | 8.99 |
How to align a Markdown table
Parses the header, alignment row, and body. Computes each column's width and pads cells. Preserves left / centre / right markers from the separator row.
- 01
Paste a table
Any GFM-style pipe table works.
Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.
inputGFMmarkedCommonMarkliveinput · markdowntable · GFM| a | b |
loaded · GFMGFM · ready - 02
Detect alignment
Reads :--, --:, :--: from the second row.
Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style
<br>insertion.alignsoft-breaksoptionsconfiglivefix · optionsl/c/r · livel c r
options applied · livelive - 03
Pad + align
Pads cells so every pipe lines up vertically.
The preview is scoped under a
.mdeclass so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.padpreviewscoped CSSrenderstableout · renderedmd · ready| a | b |
rendered · liverendered - 04
Copy back
Drop the cleaned table into your docs.
Export covers both raw Markdown and rendered HTML; downloads stream as
text/markdownortext/htmlviaBlob+ object URL.exportclipboard.md.htmlblobOK · exportedmd · doneshipped
shipped · ready to shipsuccess
Author Markdown that renders everywhere
GFM is the safe default
GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.
Soft-break behaviour varies
A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.
Escape inside code fences
Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.
Anchors are slugified
GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.
Tables need a header row
The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.
Front matter is YAML
Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.
When to align tables
Clean raw Markdown for review-friendly diffs.
Code review
Make table diffs reviewable instead of noisy. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.
GFM-compliantREADME polish
Tighten READMEs before publishing. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.
GitHub-perfectAuto-generated tables
Clean up tool-generated tables to one style. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.
diff-friendlyDoc site source
Keep table source readable for contributors. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.
render-stableMigration
Normalize tables across a repo when standards change. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.
cross-platformCross-renderer safety
Avoid edge cases in stricter Markdown renderers. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.
SEO-friendlyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.