Element Converter
GitHub Flavored Markdown to HTML
Paste GitHub Flavored Markdown to generate HTML instantly. GFM extends standard Markdown with 5 features: tables, task lists, strikethrough, autolinks, and fenced code blocks — all converted to semantic HTML.
GitHub Flavoured Markdown
- Task lists with checkboxes
- Unchecked item
| Feature | Supported |
|---|---|
| Tables | Yes |
| Strikethrough |
Autolink: https://github.com
const gfm = true;
Key facts
- Extends
- CommonMark (the GitHub dialect of Markdown)
- Added features
- Tables, task lists, strikethrough, autolinks, fenced code
- Task list output
- <input type="checkbox" disabled>
- Strikethrough output
- ~~text~~ → <del>
What does GitHub Flavored Markdown add to HTML output?
GitHub Flavored Markdown extends CommonMark with 5 features that standard Markdown lacks: tables, task lists, strikethrough, autolinks, and fenced code blocks. Each converts to dedicated HTML elements during conversion.
GFM is the Markdown dialect used across GitHub, GitLab, and most developer tools. This converter enables GFM, so output matches how GitHub renders the same source. See GitHub Flavored Markdown for the full specification.
How do task lists convert to HTML?
A GFM task list converts to an HTML list of disabled checkbox inputs. The syntax - [x] produces a checked input and - [ ] produces an unchecked input, each wrapped in a list item.
- [x] Done
- [ ] Todo<ul>
<li><input type="checkbox" checked disabled> Done</li>
<li><input type="checkbox" disabled> Todo</li>
</ul>How do strikethrough and autolinks convert to HTML?
Strikethrough wraps text in double tildes and converts to a <del> element. Autolinks turn bare URLs into clickable <a> anchors automatically, without the surrounding angle brackets or link syntax that standard Markdown requires.
~~old~~ and https://example.com<p><del>old</del> and <a href="https://example.com">https://example.com</a></p>Does the converted HTML match how GitHub renders it?
Yes. GFM tables convert to <table> elements (see Markdown Table to HTML) and fenced code blocks convert to highlighted <pre><code> (see Markdown Code Block to HTML), exactly as GitHub renders them. Neither feature exists in the original CommonMark specification.
Frequently Asked Questions
- What is the difference between GFM and standard Markdown?
- GitHub Flavored Markdown adds 5 features absent from CommonMark: tables, task lists, strikethrough, autolinks, and fenced code blocks. Standard Markdown supports headings, emphasis, lists, links, images, and blockquotes only.
- Does this converter support GitHub Flavored Markdown?
- Yes. GFM is enabled, so tables, task lists, strikethrough, autolinks, and fenced code blocks all convert to HTML exactly as GitHub renders them.
- Do task list checkboxes work in the HTML output?
- Task lists convert to disabled checkbox inputs that display the checked or unchecked state. They are read-only by default, matching how GitHub renders task lists in rendered Markdown.
- Will GitHub Flavored Markdown render outside GitHub?
- GFM renders anywhere a GFM-compatible parser is used. This converter produces standards-compliant HTML that displays the same way in any browser, independent of GitHub.