Markdown to Confluence
Convert Markdown to Confluence wiki markup for team wikis.
Convert Markdown to Confluence wiki markup for team wikis. Paste your content and get an instant result.
Paste Markdown and this page returns Confluence wiki markup: bold becomes a starred span, italic becomes an underscored one, code fences become code macros, and a table's header row is marked with doubled pipes.
The output is wiki markup, which is what the Confluence editor's insert-markup dialog and clipboard accept. It is not the XHTML storage format the REST API expects; the two are different languages and this page does not pretend to emit the second.
The conversion runs in the tab. Unknown inline HTML is dropped, because wiki markup has no equivalent and passing the angle brackets through would render them literally on the page.
The spellings that matter
Emphasis is the one people get backwards: in wiki markup an asterisk is bold and an underscore is italic, the reverse of Markdown's convention. The emitter follows the wiki rules, so a Markdown bold span becomes a starred span on purpose.
Code blocks become a code macro rather than a fenced block, and table cells are pipe-separated with the header row written as doubled pipes. These are conventions rather than algorithms, which is why they are written once and reused.
- Bold as stars and italic as underscores, per wiki markup
- Code fences as code macros
- Tables with pipe-separated cells and a doubled-pipe header
What does not translate
Raw HTML has no equivalent and is dropped. A construct the emitter does not recognise is written as its plain text, which is readable even when the formatting is lost.
Because the output targets the editor rather than the API, a page created through the API from this text may need its markup converted first.
How to use the converter input
Paste the Markdown into the input workspace and copy the wiki markup from the output panel: emphasis becomes Confluence spells, an asterisk for bold and an underscore for italic, code fences become code macros, and a table's header row is written with doubled pipes. Clear and Sample reset or demonstrate the mapping.
The output targets the editor's insert-markup dialog, not the REST API's storage format. Raw HTML has no equivalent and is dropped, and an unrecognised construct is written as its plain text, so the output is a readable draft rather than a faithful reproduction.
What to Expect
Best for
- Pasting Markdown into a Confluence page through the editor
- Converting a README into wiki markup for an internal page
- Keeping headings, lists, code and tables through the conversion
Not ideal for
- A REST API import, which wants XHTML storage format
- Round-tripping Confluence content back to Markdown
- Raw HTML, which is dropped rather than passed through
What this tool keeps
- Heading levels, lists and emphasis with wiki spellings
- Code block content inside a code macro
- Table cells and the header-row marker
What may need cleanup
- An HTML block that was dropped
- A macro-specific construct with no wiki equivalent
- Formatting that renders differently in an older Confluence version
Common errors
- Reading the starred bold as a mistake, when wiki markup inverts the convention
- Using the output as an API payload
- Expecting inline HTML to survive
Example use cases
- Moving a GitHub README into Confluence
- Preparing release notes for a wiki page
- Converting a Markdown table into a wiki table
Sample input
Paste Markdown with one heading, a bold span, a bulleted list and a two-column table.
Sample output
Wiki markup with a heading marker, a starred bold span, a bulleted list and a doubled-pipe header row, downloaded as page.txt.
Who this is for
- Teams moving documentation into Confluence
- Technical writers preparing a wiki page
- Anyone pasting Markdown into a wiki editor
Frequently asked questions
Which Markdown constructs become Confluence markup?
Bold becomes a starred span, italic an underscored one, code fences become code macros, and a table's header row is marked with doubled pipes.
Can this produce Confluence storage format for a REST import?
No. The output is wiki markup, and a REST import wants XHTML storage format.
What happens to raw HTML in the source?
Raw HTML is dropped rather than passed through.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.