Markdown to Confluence Converter
Paste Markdown and get Confluence wiki markup with real code, panel and expand macros — or rich text that pastes straight into the Confluence Cloud editor.
Free, no signup — converted in your browser, never uploaded.
Data Center, Server or the legacy editor: Insert › Markup › Confluence wiki. The Cloud editor doesn’t read wiki markup — use Rich paste there.Data Center: Insert › Markup. Cloud: use Rich paste.
Changed 3 headings → h1.–h6., 1 table → ||header|| rows, 1 code block → {code}, 1 callout → panel macros, 1 <details> block → {expand}, 2 tasks → ☐ / ☑ Dropped nothing Kept bold, italic, code, lists, links
How to Convert Markdown to Confluence
- Paste your Markdown on the left — a README, a page from a docs repo, meeting notes or an answer from ChatGPT or Claude. You can also open or drop a .md file.
- Pick the output for where the page lives: Rich paste for the Confluence Cloud editor, Wiki markup for Confluence Data Center, Server or a page still in the legacy editor.
- Check the warnings under the output. They list what Confluence can’t show as written — maths, Mermaid diagrams, relative links — and what will need a click after pasting.
- Copy and paste. Rich text goes straight into the page. Wiki markup goes into Insert › Markup with Confluence wiki selected, then Insert.
Wiki Markup or Rich Paste: Which One to Use
Confluence has two editors, and they take different input. The Confluence Cloud editor — the one every new Cloud page uses — has no wiki markup at all: Atlassian’s own help says wiki markup “is only supported in the legacy editor”. It does convert pasted formatted text into its own headings, tables, lists and code blocks, which is what Rich paste copies. Confluence Data Center and Server still read wiki markup through Insert › Markup, and wiki markup is the only way to bring macros such as {code}, {info} and {expand} along.
| Where the page lives | Use | How to paste |
|---|---|---|
| Confluence Cloud | Rich paste | Click into the page and paste (⌘V / Ctrl+V). |
| Confluence Data Center or Server | Wiki markup | Insert › Markup, choose Confluence wiki, paste, Insert. |
| A Cloud page still in the legacy editor | Wiki markup | Insert › Markup, as on Data Center. |
| A Jira issue or comment | Markdown to Jira | Jira’s markup differs slightly; use its own converter. |
What rich paste can’t carry
Pasted text can create headings, lists, tables, links, images and code blocks, but not macros. Code blocks arrive without their language, callouts arrive as quotes headed by an emoji label, and collapsible sections arrive open, with their title in bold. The warnings under the output list each one in your document, so you know what to fix with a click in Confluence.
What Converts to What
The wiki markup column below is produced by this converter with its default settings; the rich paste column describes what lands in the Cloud editor.
| Markdown | Wiki markup | Rich paste |
|---|---|---|
Headings | | Heading 1 and Heading 3 |
Bold, italic, strikethrough, code | | The same formatting |
Link | | A link |
Image | | An image linked from its URL |
Lists | | Bulleted and numbered lists |
Task list | | List items starting with ☑ and ☐ |
Table | | A table with a header row |
Code block | | A code block, without its language |
Code block, no language | | A code block |
Quote | | A quote |
GitHub alert | | A quote headed “ℹ️ Note” |
Collapsible section | | A bold “More” line with the text under it |
Horizontal rule | | A divider |
Emoji shortcode | | 🎉 🚀 |
YAML front matter | | Removed; only “Body” is pasted |
Mermaid diagram | | A code block with the diagram source |
Inline maths such as $E=mc^2$ stays as text, because Confluence has no built-in maths markup, and relative links like ./setup.md are flagged because they won’t resolve inside Confluence. Single line breaks inside a paragraph are joined, as Markdown renders them; switch Line breaks to Keep if you want every line kept.
GitHub Alerts and Callouts Become Confluence Panels
Confluence has four panel macros, each with its own colour. GitHub has five alerts with different names, so the converter matches them by colour rather than by name — which is why GitHub’s yellow WARNING becomes Confluence’s yellow {note}, and its red CAUTION becomes the red {warning}.
| Markdown | Confluence macro | Panel colour |
|---|---|---|
> [!NOTE] | {info:title=Note} | blue |
> [!TIP] | {tip:title=Tip} | green |
> [!IMPORTANT] | {note:title=Important} | yellow |
> [!WARNING] | {note:title=Warning} | yellow |
> [!CAUTION] | {warning:title=Caution} | red |
Obsidian callouts such as > [!tip], > [!bug] or > [!example] follow the same colour logic, and a custom title after the marker becomes the panel’s title. Switch Panel titles off for untitled panels, or Panels off to keep callouts as quotes.
Can You Paste Markdown Into Confluence?
Sometimes. The Cloud editor understands Markdown shortcuts while you type — **bold**, # headings, - lists, three backticks for a code snippet, [] for an action item — and Atlassian has said pasted Markdown is converted too. In practice users often report a paste arriving as a single code block or as plain text, and callouts and collapsible sections have no Markdown that Confluence would turn into a panel or an expand.
On Data Center, Insert › Markup also offers a Markdown option. It handles standard Markdown, but Confluence-only features — panels, expand sections, a table of contents, code block titles and line numbers — need wiki markup, which is what the Wiki markup output writes.
Going the other way
To move a Confluence page into a Git repository or a docs site, copy the page and paste it into Confluence to Markdown: info, tip, note and warning panels come back as GitHub-style callouts.
Frequently Asked Questions
How do I convert Markdown to Confluence?
Paste the Markdown into the left pane. For Confluence Cloud, choose Rich paste, click Copy rich text and paste into your page: headings, lists, tables, links and code blocks arrive as real Confluence content. For Confluence Data Center or Server, choose Wiki markup, click Copy wiki markup, then use Insert › Markup in the editor, pick Confluence wiki and paste.
Why does wiki markup show up as plain text in Confluence Cloud?
Because the current Confluence Cloud editor doesn’t read it. Atlassian’s documentation says wiki markup is only supported in the legacy editor, so pasting h1. or {code} into a Cloud page gives you those characters, not a heading or a code block. Switch the output to Rich paste: it copies the content as formatted text, which the Cloud editor turns into its own blocks.
How do I insert wiki markup in Confluence Data Center?
In the editor, open Insert › Markup, choose Confluence wiki as the format, paste the wiki markup and check the preview, then click Insert. Confluence converts it into normal page content, so you edit the result in the editor rather than as markup afterwards.
Can Confluence read Markdown directly?
Partly. The Cloud editor turns Markdown shortcuts into formatting as you type — **bold**, # headings, - lists, ``` code — and Atlassian has said pasted Markdown is converted too, but users often report it arriving as one code block or as plain text, and tables and callouts don’t come through. Data Center’s Insert › Markup dialog also has a Markdown option, but Markdown has no way to ask for a panel, an expand section or a table of contents. Converting first gives you a predictable result, and on Data Center those macros too.
Do code blocks keep their syntax highlighting?
In wiki markup, yes: a fence such as ```js becomes {code:language=javascript}, common short names are mapped to the names Confluence knows, a title= or filename= in the fence becomes the macro’s title, and you can add line numbers. A fence with no language becomes {noformat}, or a plain {code} block if you prefer. In rich paste the code arrives as a code block without a language, which you pick in Confluence.
What happens to GitHub alerts like > [!NOTE]?
In wiki markup they become Confluence panel macros, matched by colour: NOTE becomes a blue {info}, TIP a green {tip}, IMPORTANT and WARNING a yellow {note}, and CAUTION a red {warning}, each titled with its label. Obsidian callouts are mapped the same way. In rich paste they become a quote that starts with the label, because pasted text can’t create a panel.
Is Confluence wiki markup the same as Jira’s?
Nearly. Both use h1. headings, *bold*, _italic_, {{monospace}}, ||header|| tables and [text|url] links. Confluence adds macros Jira text fields don’t render, such as {info}, {expand} and {toc}. For Jira descriptions and comments, use the Markdown to Jira converter instead.
Is my document uploaded?
No. The conversion runs in your browser and nothing you paste is sent to a server. Your draft is saved only in this browser so it is still there when you come back.