Markdown to Confluence

Convert Markdown to Confluence Wiki Markup. Handles headings, code blocks, tables, links, lists, and Confluence macros.

Markdown

Confluence Wiki Markup

h1. Project Documentation

Welcome to the *project docs*. Read this _carefully_.

h2. Installation

{code:language=bash}
npm install my-package
npm run build
{code}

h3. Configuration

|| Key || Default || Description ||
| port | 3000 | Server port |
| debug | false | Enable debug mode |

{info}
Note: Restart the server after changing configuration.
{info}

# Install dependencies
# Configure settings
# Start the server

Markdown to Confluence Wiki Markup

Confluence uses Atlassian Wiki Markup — similar to Jira but with additional macro support. Notable differences from Jira: code blocks use {code:language=javascript}, and blockquotes become the {info} macro. Confluence also supports {note}, {warning}, and {tip} macros for callout boxes.

Built and maintained by Meet Shah · Last updated 27 July 2026

What this tool is used for

Moving documentation from a repository into a Confluence space.
Converting release notes for an internal wiki page.
Adapting a README for a Confluence page that mirrors it.
Producing wiki markup from a source maintained in Markdown.
Finding out which Confluence macros a page needs before pasting anything in.

Frequently Asked Questions

Which Confluence syntax does this produce?: Wiki markup — h1. headings, {code} and {info} macros — not the XHTML storage format the API uses. In Confluence Cloud you paste it via the editor's markup insertion rather than typing it into the page, because the editor stores XHTML and only converts markup on the way in.
Why do blockquotes become an info panel?: Because Confluence's own quote styling is barely visible, while {info} renders the recognisable blue callout that most documentation uses for exactly the notes people write as blockquotes. Swap it for {note} or {warning} if the tone calls for it — the macros are interchangeable.
Are code fences preserved with their language?: Yes — a fenced block becomes {code:language} and keeps the hint, so Confluence applies syntax highlighting. Fences without a language become a plain {code} block, which still renders as monospace with the surrounding frame.
Why did bold and italic behave oddly in older versions?: Because the inline conversion emitted bold as *x* and then ran an italic pass over the result, which rewrote every bold into _x_. Inline handling is now shared with the Slack and Jira converters and applies each rule once, so bold stays bold.
What Markdown will not survive?: Anything with no wiki equivalent: HTML blocks, footnotes, task lists and reference-style links. Tables, headings, lists, code, quotes and inline emphasis all convert. Check nested lists in particular — indentation rules differ, and deep nesting is where the two formats diverge most.

Common errors and gotchas

Expecting code fences to convert cleanly, since Confluence uses a macro rather than a fence.
Assuming heading syntax matches, when Confluence uses h1. through h6. notation.
Losing table formatting, where Confluence uses double pipes for header cells.
Overlooking that Confluence's newer editor may not accept wiki markup at all.
Leaving raw HTML in place, which Confluence usually strips or renders as text.