Markdown Table Validator & Linter
Is your Markdown table not rendering properly on GitHub, GitLab, Obsidian, or Notion? Our 15-point diagnostic matrix parses your table line-by-line, exposing critical blockers like missing preceding blank lines, malformed delimiters, ragged column drift, unescaped pipes, and invisible Unicode bombs — with instant 1-click auto-repair.
How to Use This Tool
Paste or Test Problematic Table
Paste your raw Markdown table or click one of our 1-click test scenarios (Missing Delimiter, Unescaped Pipes, Hidden Unicode, or GitHub Blocker).
Review 15-Point Diagnostics & Health Score
Check the real-time Table Health Score (0–100%) and line-level cards showing exact line numbers, offending code snippets, and platform render predictions.
1-Click Auto-Repair & Copy Clean GFM
Click "1-Click Auto-Repair" to instantly normalize delimiter rows, balance ragged columns, purge zero-width spaces, and copy clean GFM markdown.
Worked Example
| Endpoint | Method | Scope | Limit | | /api/users | GET | read:users | 1,000/hr | | /api/auth | POST | public | | /api/reports | GET | read:reports | 500/hr | CSV | | /api/billing | POST | admin | billing | 100/hr |
| Endpoint | Method | Scope | Limit | Column 5 | | :----------- | :----: | :----------------- | -------: | :------- | | /api/users | GET | read:users | 1,000/hr | | | /api/auth | POST | public | | | | /api/reports | GET | read:reports | 500/hr | CSV | | /api/billing | POST | admin \| billing | 100/hr | |
Syntax Linting, Column Integrity & 1-Click Auto-Repair
The Markdown Table Validator performs static analysis on raw Markdown tables. It checks for missing delimiter rows, uneven column counts per row, missing pipe delimiters, unescaped pipes, and illegal newlines. The built-in auto-repair engine rectifies detected anomalies and outputs a compliant GitHub Flavored Markdown table in one click.
Markdown Table Pro Tips & Best Practices
Validate Before Publishing
QAPaste your markdown table into the validator to confirm it meets strict GFM syntax rules before deploying documentation.
Check for Empty Preceding Line
CommonMark RuleAlways ensure an empty blank line exists before the table in your markdown file to trigger parser table mode.
Auto-Repair Ragged Rows
One-Click FixClick the "Auto-Repair Table" button to automatically balance uneven rows without manual pipe editing.
Catch Unescaped Pipes
Syntax FixLook for warnings about unescaped pipe characters inside text cells and replace them with \|.
Common Pitfalls & How to Fix Them
Warning: Row 3 has fewer columns than header
Cause: A row is missing trailing pipes or cell values.
Error: Missing delimiter line
Cause: The separator row containing hyphens (e.g. |---|---|) is missing or malformed.
Platform & Markdown Flavor Compatibility
| Platform / Specification | Support Status | Compatibility Notes |
|---|---|---|
| GFM Linter Rules | Supported | Identifies common markdown rendering errors. |
| markdownlint-cli | Supported | Enforces MD036 and table alignment standards. |
Frequently Asked Questions
Why does GitHub fail to render my Markdown table as a table?▼
The #1 most common GitHub render blocker is a missing empty blank line directly before the table header. In CommonMark and GitHub Flavored Markdown (GFM), if paragraph text touches the table without an empty line between them, the parser treats the entire table as regular paragraph text. Another common cause is a missing or malformed delimiter row (the second line with hyphens like |---|---|).
How do I escape pipe (|) characters in table cells?▼
Because Markdown tables use pipes to delimit columns, unescaped pipes inside text (e.g. TypeScript union types like string | number) will split the cell into extra phantom columns. Escape the pipe with a backslash (\|) or wrap the expression inside inline backticks (`string | number`).
What is a ragged row and why does it cause rendering errors?▼
A ragged row has fewer or more cells than the header row defines. Parsers like Notion will fail or drop columns, while GitHub GFM may misalign data into the wrong columns. Our validator detects ragged rows and our Auto-Repair engine pads short rows with empty cells automatically.
What are hidden zero-width unicode characters and how do they get into tables?▼
When copying text from Slack, Jira, Notion, or Google Docs, invisible unicode characters such as zero-width spaces (\u200B) and byte-order marks (\uFEFF) often hitch a ride. While invisible to the naked eye, they corrupt string lookups, column alignments, and regex queries. Our linter flags and purges them with 1 click.
Is my data processed privately on my machine?▼
Yes, 100%. All validation, syntax linting, health score calculations, and auto-repair algorithms run entirely in your local browser using client-side Web APIs. Zero table data is ever transmitted to a server or external database.
Why does GitHub fail to render my table?▼
Common reasons include: missing an empty line before the table, omitting the separator line (|---|---|), or unescaped pipe characters inside text.
Can the validator repair my table automatically?▼
Yes! Click the "Auto-Repair" button and the engine will automatically balance column counts, restore missing delimiters, and pad short rows.
Need Whole Document Conversion?
MarkdownTables.com is built exclusively for Markdown tables and tabular data. If you need to convert entire Markdown documents, essays, or notes (with headings, paragraphs, lists, and images) to PDF, Word (DOCX), or PowerPoint, visit our sister platform.
Related Markdown Table Tools & Resources
Markdown Table Formatter
Prettify and align Markdown table column padding once validated.
Table Cleaner & Sanitizer
Remove empty rows, trim whitespace, and purge HTML tags in Markdown tables.
Markdown Table Sorter
Sort Markdown table rows alphabetically, numerically, by date or bytes.
Syntax Hub: Escape Pipes
Learn how to handle pipe characters in Markdown tables.