⌘ K
upgrades GFM callouts and ==highlight== to Pandoc

Convert Markdown to Pandoc Markdown

Upgrade GitHub-flavored Markdown to Pandoc's extended dialect — callouts become fenced divs, ==highlight== becomes the .mark span.

Markdown → Pandoc
Input
154 B
14 lines
Output
160 B
15 lines
Status
ready
live
Ratio
1.04×
out/in
input · markdown
output · pandoc
# Project Notes

::: note
This is an important callout.
:::

Text with [highlight]{.mark} and ~~strikethrough~~.

- One
- Two
- Three

```python
print("hi")
```
Quick Start

How to convert to Pandoc Markdown

Pandoc accepts almost all standard Markdown — this pass upgrades GitHub-specific syntax into canonical Pandoc forms (fenced divs and inline spans).

  1. 01

    Paste GFM source

    Markdown with callouts, highlights, or footnotes.

    Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.

    inputGFMmarkedCommonMarklive
    input · markdowngfm · GFM
    > [!NOTE]
> note
    loaded · GFMGFM · ready
  2. 02

    Convert callouts

    GFM callouts become ::: divs.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    calloutsoft-breaksoptionsconfiglive
    fix · options::: · live
    ::: note
note
:::
    options applied · livelive
  3. 03

    Convert highlight

    ==text== becomes [text]{.mark}.

    The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.

    markpreviewscoped CSSrenderstable
    out · renderedpd · ready
    [txt]{.mark}
    rendered · liverendered
  4. 04

    Run pandoc

    Feed the output to pandoc -f markdown for any target format.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    exportclipboard.md.htmlblob
    ✓ · exportedpd · done
    ✓ ready
    exported · ready to shipsuccess
Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Related toolsAsciiDocreSTLaTeXOrg ModeTypstEditor
Use Cases

When to convert to Pandoc

When Pandoc is your output toolchain.

Pandoc-driven sites

Sites built with pandoc + lua filters. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

Academic papers

Convert GFM drafts to Pandoc → LaTeX / PDF. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

EPUB authoring

Pandoc is the standard MD→EPUB pipeline. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Multi-format export

Pandoc emits 30+ formats from one source. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Doc archive

Long-term-stable source format. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Cross-tool docs

Same source for Hugo, Quarto, and books. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly
FAQ

Frequently asked questions

GFM-style callouts (> [!NOTE]) become Pandoc fenced divs (::: note). ==highlight== becomes [text]{.mark}. Other GFM syntax is already compatible.
No — plain CommonMark passes through unchanged. The tool only re-writes syntax that needs upgrading.
GFM and Pandoc both use [^id] footnote syntax — no transform needed.
Pandoc's --smart flag handles those at conversion time, so we leave punctuation alone.
No. Conversion runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!