⌘ K
GFM → Confluence wiki · h1. · {code} · [text|url] · {{inline}}

Convert Markdown to Confluence wiki

Reformat Markdown for Atlassian Confluence — h1./h2. headings, {code} macros, [text|url] links, and {{inline}} code mapped automatically.

Markdown → Confluence
Input
220 B
15 lines
Output
240 B
15 lines
Status
ready
live
Ratio
1.09×
out/in
input · markdown
output · confluence wiki
h1. Release notes

_v2.0_ ships with _major_ improvements.

h2. Highlights

* New {{api/v2}} endpoint
* Faster startup time
* See [docs|https://example.com/docs]

{code:language=js}
console.log("hi");
{code}

bq. Watch out: breaking change.
Quick Start

How to convert Markdown for Confluence

Confluence wiki markup uses h1. headings, {code} macros, and [text|url] links. This converter rewrites every difference in one pass.

  1. 01

    Paste Markdown

    From your README, PR, or internal docs.

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

    inputGFMmarkedCommonMarklive
    input · markdownmd · GFM
    # Heading
    loaded · GFMGFM · ready
  2. 02

    Map headings

    # Title → h1. Title; ## → h2. and so on.

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

    headingsoft-breaksoptionsconfiglive
    fix · optionswiki · live
    h1. Heading
    options applied · livelive
  3. 03

    Map inline + macros

    [text](url) → [text|url]; `x` → {{x}}; ``` becomes {code} macro.

    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.

    mappreviewscoped CSSrenderstable
    out · renderedconf · ready
    {{inline}}
    rendered · liverendered
  4. 04

    Paste into Confluence

    Use the wiki markup editor or import via REST.

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

    exportclipboard.md.htmlblob
    OK · exportedconf · done
    shipped
    shipped · 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 toolsJiraNotionSlackHTMLBBCodeEditor
Use Cases

When to convert for Confluence

Sync engineering docs into the company knowledge base.

Engineering docs

Move README content into the engineering Confluence space. 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

Runbooks

Migrate Markdown runbooks to the ops space. 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

RFC import

Publish RFCs from a Git-tracked Markdown source. 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

Onboarding pages

Convert checklists for onboarding spaces. 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

Release notes

Mirror release notes from GitHub to Confluence. 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

Wiki migration

Bulk-convert legacy Markdown wikis to Confluence. 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

This tool emits classic wiki markup, which the Confluence editor accepts via the 'Insert wiki markup' action. Storage format (XHTML) is a different target.
Markdown table syntax is left as-is — Confluence parses Markdown tables in modern editors. For older wiki syntax (||header||) convert by hand.
Use blockquote (> text) which becomes bq.; for {info} / {warning} panels add them manually after conversion.
Yes — [text](url) becomes [text|url], the Confluence link macro.
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!