HTML Table to Markdown Converter

An HTML Table to Markdown Converter is a free online tool that transforms HTML <table> markup into Markdown-formatted tables. Markdown tables use simple pipe (|) and dash (-) syntax, making them ideal for README files, GitHub/GitLab documentation, static site generators like Jekyll or Hugo, and any Markdown-based writing workflow. This tool preserves table structure, handles colspan and rowspan attributes, and can even convert inline HTML elements like links and bold text into their Markdown equivalents.

Our converter intelligently expands colspan and rowspan attributes into a normalized grid before generating the Markdown table. For colspan, the cell is duplicated across the specified number of columns in the same row. For rowspan, placeholder cells are inserted in subsequent rows at the correct column positions. This ensures the final Markdown table has a consistent number of columns per row, which is required by the Markdown table specification. If the original HTML table has irregular structures, the tool automatically pads rows with empty cells to maintain alignment.

Yes! If your HTML contains multiple <table> elements, the converter processes all of them and outputs each as a separate Markdown table, separated by blank lines. This is useful when converting documentation pages or HTML reports that contain several tables. The tool also displays the total number of tables detected, along with row and column counts for each one.

When the "Convert Inline HTML" option is enabled (default), the tool transforms common inline tags into Markdown syntax:

• <a href="url">text</a> → [text](url)
• <strong>bold</strong> → **bold**
• <em>italic</em> → *italic*
• <code>code</code> → `code`
• <img src="url" alt="desc"> → ![desc](url)
• <br> → preserved as <br> (Markdown-compatible)

Disabling this option preserves the raw HTML inside table cells.

Markdown tables offer several advantages: Readability – they're human-readable in plain text editors; Portability – they work across GitHub, GitLab, Bitbucket, Stack Overflow, and most Markdown renderers; Version control – diffs in Markdown tables are easier to review than HTML; Simplicity – less verbose syntax reduces document size and cognitive load. Markdown has become the de facto standard for developer documentation, making table conversion an essential part of any documentation workflow.

Nested tables (a <table> inside another table's cell) are not fully supported in the Markdown output because standard Markdown does not support nested table structures. If a nested table is detected, its content will be extracted as plain text. For best results, avoid nesting tables and consider restructuring your data into separate, independent tables before conversion.

The tool automatically escapes pipe characters (|) within cell content by prefixing them with a backslash (\|), preventing them from being interpreted as column separators. Other special Markdown characters like asterisks and underscores are preserved as-is since they typically render correctly within table cells. HTML entities (e.g., &, <) are automatically decoded during parsing.

Pretty Print aligns the pipe characters (|) in the output Markdown table so that all columns have consistent widths. This makes the raw Markdown much easier to read and edit. Without Pretty Print, each column is only as wide as its content (plus one space on each side), which can look jagged. With Pretty Print enabled, extra spaces are added to shorter cells so that the table appears neatly aligned in plain text — this is purely cosmetic and doesn't affect how the table renders.

Absolutely. All conversion happens entirely within your browser using client-side JavaScript. No data is ever sent to any server, uploaded, stored, or logged. Your HTML input never leaves your device. You can verify this by disconnecting from the internet — the tool will continue to work perfectly offline. This makes it safe for converting sensitive or proprietary data.

Yes! Since all processing is done client-side, the tool works fully offline once the page is loaded. You can bookmark it, save the page for offline use, or even integrate it into your local development environment. There's no dependency on external APIs or server-side processing — just pure browser-based JavaScript conversion.