Markdown Table Merge Cells? What You Can Do

No: standard Markdown table syntax has no way to merge cells across rows or columns. If your Markdown renderer permits HTML tables, you may be able to use the HTML colspan or rowspan attributes; otherwise, use a simpler table layout or another format that supports merged cells.

What a merged table cell means

A merged cell occupies the space of two or more ordinary cells. A horizontal merge across columns is usually called a column span; a vertical merge across rows is a row span. In a report, for example, a heading such as Quarterly totals might span four columns, or one category name might cover several rows of related entries.

Those layouts depend on table structure, not just on how text is displayed. A renderer must know that the spanning cell replaces multiple positions in the grid. Markdown table syntax does not provide that structural instruction, so typing a longer label, leaving a cell blank, or adding extra pipe characters cannot create a genuine merge. At best, those choices produce ordinary cells that happen to look unusual.

Why Markdown tables have no merge syntax

Markdown began as a lightweight way to write formatted text that could be converted into HTML. The original Markdown specification did not define tables at all. Many tools later added pipe-table extensions because they are convenient for simple data, but those extensions generally describe a rectangular grid: a header row, a separator row, and body rows with cells in consistent column positions.

That simple structure is one reason tables are readable in plain-text files and easy to convert between tools. A merge feature would need extra rules for which cells are covered, how rows with different shapes should be interpreted, and how assistive technology should announce the relationships. There is no single merge notation accepted by all Markdown implementations, so a table written with a tool-specific convention may not survive when copied to another website or converted with a different renderer.

It is useful to separate Markdown from its extensions. A Markdown editor may offer a table button, and a publishing platform may display tables, but that does not mean the underlying Markdown standard includes every table feature available in the editor.

What ordinary Markdown tables can do

Pipe tables handle many everyday jobs without merged cells. They can show headers, multiple rows and columns, and basic inline formatting such as links or emphasis, depending on the renderer. In GitHub Flavored Markdown, for instance, a separator row with colons controls alignment. A small example is:

| Item | Cost |
|:-----|-----:|
| Notebook | 4.00 |
| Pen | 1.50 |

This gives the first column left alignment and the second right alignment in renderers that support GitHub-style tables. It does not merge the header cells, even if the header text is intended to describe both columns. A useful workaround is to make the header say something like Item and cost, or add a sentence immediately before the table explaining that both columns belong to the same group.

Pipe tables are best when each row has the same set of fields. If a table has a complicated heading, nested structure, or cells that span several rows, forcing it into a pipe table can make the source harder to understand than the information it contains.

Using HTML colspan or rowspan

HTML tables support merged cells through attributes. Use colspan to make one cell cover multiple columns, and rowspan to make it cover multiple rows. For example, this HTML structure makes the first header span two columns:

&lt;table&gt;
  &lt;thead&gt;
    &lt;tr&gt;&lt;th colspan=&quot;2&quot;&gt;Contact&lt;/th&gt;&lt;/tr&gt;
    &lt;tr&gt;&lt;th&gt;Name&lt;/th&gt;&lt;th&gt;Email&lt;/th&gt;&lt;/tr&gt;
  &lt;/thead&gt;
  &lt;tbody&gt;
    &lt;tr&gt;&lt;td&gt;Ari Lee&lt;/td&gt;&lt;td&gt;ari@example.com&lt;/td&gt;&lt;/tr&gt;
  &lt;/tbody&gt;
&lt;/table&gt;

In an actual Markdown source file, write the HTML tags themselves, rather than the escaped display shown above. The example is escaped here so the tags appear as code instead of being interpreted as a table by this page. The table has two columns in its second header row and body row, while the top header occupies both columns.

For a vertical span, an HTML cell could use rowspan="2" and the following row would omit the position already occupied by that spanning cell. Check the resulting structure carefully: adding a spanning cell without removing the cells it covers can shift later content into the wrong columns.

Will HTML work in every Markdown editor?

No. Markdown is commonly rendered to HTML, but support for raw HTML written inside a Markdown document varies by application, platform, and security settings. Some renderers allow table tags and span attributes. Others strip HTML, escape it so it appears as text, or permit only a restricted set of tags and attributes. A platform can also change its rules over time.

GitHub Flavored Markdown supports pipe tables, and GitHub also allows some raw HTML in Markdown documents, subject to sanitization. That does not make HTML tables a universal Markdown feature or guarantee that every attribute behaves identically in every publishing destination. A documentation generator, chat tool, note-taking app, or learning platform may use a different parser and filtering policy.

Before choosing HTML, preview the document in its final destination. If the content will be published in several places, check each renderer separately. When the destination blocks HTML, there is no pipe-table syntax that can be substituted to produce the same true merged cells.

Practical alternatives to merged cells

Often the clearest solution is to revise the table rather than reproduce the visual merge. Consider these options:

Repeat a shared label. Put the category name in every applicable row. Repeating a value may look less elegant, but it keeps each row understandable when copied, sorted, or read by assistive technology.
Add a group column. Give each row a value such as Region or Quarter instead of placing one label across several rows.
Split the table. Use separate tables under short headings when groups have different structures or need their own explanatory labels.
Explain the grouping in nearby text. A sentence or subheading can communicate that several columns belong to one topic without adding a complex header row.
Use HTML where it is supported. This is suitable when merged cells are genuinely important and the final renderer accepts the markup.
Choose a different output format. If the document needs elaborate tables for print or presentation, a word processor, spreadsheet, or page-layout tool may be a better fit than portable Markdown.

For instance, a table of sales by quarter could use a merged heading spanning January, February, and March. A more portable version can have columns named Quarter, Month, and Sales, with Q1 repeated on each monthly row. That layout is longer but remains clear when converted to plain text, filtered, or imported into another tool.

How to choose the right approach

Start with where the document will be read, not with the syntax that looks best in the editor. If it is a README or a simple documentation page, use pipe tables when the information is naturally rectangular. If the page needs spanning headers and its renderer accepts HTML, an HTML table can provide them. If the table must work across unknown Markdown platforms, avoid relying on raw HTML or a nonstandard extension.

It also helps to ask what the merge is accomplishing. A wide heading may simply be a title and could move above the table. A repeated category label may be clearer as a separate column. A merged cell used only for visual grouping can often be replaced by a heading and two smaller tables. But if a reader needs the exact hierarchy in a complex data table, use a format and publishing path that preserve that structure, then verify the output.

Identify whether you need a horizontal span, a vertical span, or only a visual group label.
Confirm which Markdown renderer will display the document and whether it permits HTML table attributes.
Choose the simplest structure that communicates the relationships, including a non-HTML fallback if portability matters.
Preview the rendered table and check its accessibility and behavior on narrow screens.

Common problems and misconceptions

A common misconception is that alignment markers create merged cells. In pipe tables, colons in the separator row indicate alignment, not spanning. Likewise, using fewer cells in a row, adding blank cells, or putting a label on a separate line does not tell the renderer to merge a region. The output may appear uneven, but the cells remain separate or the row may render incorrectly.

Another trap is mixing Markdown and HTML inside one table. Some parsers do not process Markdown formatting inside raw HTML blocks in the way an author expects. A link or emphasis marker that works in a pipe table might appear literally inside an HTML cell. Use HTML markup for the content inside HTML tables, and test the result on the target platform rather than assuming the two syntaxes combine seamlessly.

Finally, visual appearance is not the only concern. A merged header can make relationships harder to interpret for screen-reader users unless the table has a sensible header structure. Repeating labels or using clear row and column headers can be more accessible and more robust. If accessibility is important, check the rendered page with the platform’s accessibility guidance and avoid using a visual merge as the only way to convey meaning.

Frequently Asked Questions

Can I merge cells in a Markdown table with a special character?

No standard Markdown character or pipe-table notation means merge these cells. Symbols such as a backslash, extra pipes, or an empty cell will not create a span. A particular editor could provide its own extension, but that syntax is not portable unless the destination uses the same extension.

Can I use colspan in a Markdown file?

You can write an HTML table with a colspan attribute in a Markdown file if its renderer permits raw HTML and does not remove that attribute. The attribute belongs to HTML, not to standard Markdown table syntax. Preview the published page to confirm that the platform retains it.

Does GitHub Markdown support merged cells?

GitHub-style pipe tables do not have merged-cell syntax. GitHub supports some raw HTML in Markdown, so an HTML table may be an option, but HTML is subject to sanitization and the result should be checked on GitHub itself. Do not assume the same source will render identically on another service.

Can blank cells make a table look merged?

Blank cells remain separate cells; they do not span the space of neighboring cells. A blank may be acceptable when the meaning is obvious, but readers and software can still treat it as an empty value. Repeat the group label or restructure the table if the relationship needs to be explicit.

What is the best alternative when HTML is blocked?

Use a regular grid with repeated labels, add a grouping column, or divide the content into smaller tables with headings. These approaches are usually more portable than relying on a renderer-specific feature, and they preserve meaning when the Markdown is converted to plain text or another format.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.