Skip to content
yutils
HTML → Markdown
Example

Input (Markdown)

# yutils

**Bold** and *italic*, plus `inline code`.

- item 1
- item 2

Output (HTML)

<h1>yutils</h1>
<p><strong>Bold</strong> and <em>italic</em>, plus <code>inline code</code>.</p>
<ul>
<li>item 1</li>
<li>item 2</li>
</ul>

Note

Full CommonMark + GFM (tables, fenced code, task lists) supported. The HTML is sanitized via DOMPurify — dangerous tags like `<script>` are auto-removed.

Usage / FAQ

When to use

  • Preview a README or blog post before publishing
  • Check how content will render in GitHub / GitLab / Notion (GFM)
  • Validate tables, checkboxes, and fenced code blocks
  • Copy the rendered HTML directly into email or a CMS
  • Learn Markdown by seeing input and output side by side

FAQ

Q.Does this render exactly like GitHub?
A.Base GFM compatibility is the goal. GitHub-specific extensions (auto-linking issue numbers, emoji shortcodes like `:smile:`) are not supported, but core syntax (headings, lists, tables, fenced code) matches.
Q.Is the HTML output safe to paste into a CMS?
A.Yes — output is run through DOMPurify, so `<script>`, `onerror=`, and other XSS-prone patterns are stripped automatically.
Q.Is my Markdown sent anywhere?
A.No. Parsing, rendering, and sanitization all happen in your browser.
Fun facts

  • Markdown was designed in 2004 by John Gruber, with help from Aaron Swartz, and first appeared on Gruber's blog Daring Fireball. The 'plain text that reads naturally and converts cleanly to HTML' philosophy came from frustration with writing conference materials in email.

    Daring Fireball — Markdown

  • The 'Markdown fragmentation' problem — every implementation rendering slightly differently — was finally addressed in 2014 with CommonMark, led by Jeff Atwood (co-founder of Stack Overflow) and John MacFarlane. The original name 'Standard Markdown' was changed after Gruber objected.

    CommonMark

  • GitHub Flavored Markdown (GFM) adds tables, task lists, autolinks, and fenced code blocks as a strict superset of CommonMark. Every GFM document is also valid CommonMark — that's why 'broken only on GitHub' is rarer now.

    GitHub Flavored Markdown Spec

Related tools

See all in this category →