Paste a page’s storage format and get Markdown back — with the code macros, info panels and task lists that normally vanish.
Code macros, panels and task lists are mapped before conversion.
Converted — share it as a page.
Publish this as a live page in one click. No account to start.
Confluence pages are XHTML, but the parts that matter are not: code blocks, info panels, task lists, page links and attached images all live in Confluence’s own ac: and ri: namespaces. A generic HTML to Markdown converter has never heard of any of it and drops the lot, which is why the usual attempt returns a page with its prose intact and every code block missing. This converter normalises those elements first — <ac:structured-macro ac:name="code"> becomes a fenced block with its language, an info panel becomes a block quote, a task list becomes real checkboxes — and only then runs the Markdown conversion. Anything it does not recognise is named in a notice rather than quietly deleted.
In Confluence, open the page and choose ⋯ → Advanced Details → View Storage Format, then copy what you see.
Paste it on the left. Macros are mapped to their Markdown equivalents before conversion.
Copy the Markdown, download the .md, or publish it as a page.
A team is leaving Confluence for a docs-as-code setup and starts with the deploy runbook, which is mostly commands. Their first attempt — select the rendered page, copy, paste into an HTML to Markdown tool — produces something that looks nearly right until someone notices every command block is gone: the shell snippets were code macros, and the converter did not know what those were. The checklist has also become plain sentences with no boxes. Pasting the storage format here instead brings back the commands as fenced blocks tagged bash, the "Deploys are frozen on Fridays" panel as a block quote that still reads as a warning, and the checklist as - [x] / - [ ] items with their completion preserved. The notice tells them the one expand macro had no equivalent and its contents were inlined, so they know to look at that section rather than discover it missing later.
Open the page in Confluence, then ⋯ (top right) → Advanced Details → View Storage Format. That view is the XHTML source the page is stored as, and it is the only version that still contains the macros. Copying the rendered page instead gives you the visual output, where a code block is just a styled box and the converter has nothing structural to work from.
Because the storage format identifies other pages by title — <ri:page ri:content-title="Deploy Guide"/> — and never by URL. The address depends on your site’s base URL and space key, neither of which is in the export. Inventing a link would produce one that looks real and 404s, so the reference is kept as visible bold text for you to point at its new home.
They are named, not embedded. An attached image lives inside Confluence behind your login, so there is no URL a Markdown file could reference. Each one becomes [image: filename.png] so you can see exactly which files to export separately and where they belong.
Code and noformat become fenced code blocks, keeping the language parameter. Info, note, warning, tip and panel become block quotes with their title in bold. Task lists become GitHub-style checkboxes. Any other macro has its readable body kept inline and its name listed in the notice, so nothing disappears without you being told.
Not here — this converts one page at a time from pasted text. For a full space, Confluence’s own Space Export produces an XML or HTML archive, and there are command-line tools built for that bulk case. This page is for the far more common job of moving one runbook or spec out.
免費帳號的連結保留 7 天。升級付費方案後，你建立的每個頁面都會永久上線。
查看方案與價格