When a Markdown table does not render, start with the smallest valid example instead of adding more spaces or pipes at random.
| Name | Status |
| --- | --- |
| API | Ready |
Paste this into the Markdown viewer. If it renders, the original table contains a structural problem. If it does not, the destination renderer may not support GFM tables.
Troubleshooting order
- Add a blank line before and after the table.
- Confirm that the second row contains dashes for every column.
- Count the logical cells in each row.
- Remove multiline content and complex inline markup.
- Add rows back individually until the problem returns.
This method identifies the exact row that introduces the failure.
Escaping literal pipe characters
A pipe inside cell content may be interpreted as a new column. Escape it when the renderer supports that form:
| Operator | Meaning |
| --- | --- |
| `A \| B` | Either A or B |
Code and escaping behavior can vary, so test the final destination rather than assuming every parser behaves identically.
Avoid unsupported table designs
GFM tables do not provide merged cells, multiple header rows, or nested tables. Simplify the data, split one complex table into two, or use HTML when those structures are essential.
Once the source renders correctly, preview the document at mobile width and before exporting through Markdown to PDF or Markdown to Word.
Key takeaways
- Verify the required header separator row
- Add blank lines around the table
- Test with a GFM-capable renderer
Try the main MD Opener workflow
If this guide matches what you were searching for, the fastest next step is to use the MD Opener homepage to open your file immediately. The homepage is built for instant Markdown previews, clear formatting, and a low-friction browser experience.
You can also continue through the Beginner Guides cluster to explore more articles with similar search intent.
Frequently asked questions
Is the separator row required in a Markdown table?
Yes. GFM tables require a separator row containing dashes beneath the header.
Do I need pipes at the start and end of every row?
Outer pipes are commonly used for readability, although many GFM parsers do not require them. Consistent use makes errors easier to spot.
Why does the same table render differently across apps?
Markdown applications can support different extensions and parsing rules. Confirm that the destination renderer supports GFM tables.