Is Markdown native across every Confluence page?

No. Markdown support depends on the available macro, editor, deployment, permissions, and configuration. Check the site before planning a migration.

Does the Markdown macro convert the whole page?

No. It renders Markdown inside its macro container. Text and components outside that container use Confluence's normal page editor.

Why did my Markdown table or task list render incorrectly?

The macro parser may not support that syntax or extension. Test the feature separately and replace it with native Confluence content when needed.

Should I keep the original Markdown source?

Yes. Keep a separate source copy so you can revise, compare, or move the content if the macro or parser changes.

Use Markdown in Confluence Pages

Confluence can display Markdown through its Markdown macro when that macro is available in your editor and plan. Insert the macro, paste Markdown into its body, and preview or publish the page to check the result. The macro is a page element, not a guarantee that every page area accepts Markdown as native editor content. Markdown features can also render differently from the surrounding Confluence content. Test headings, links, lists, code, tables, images, and unsupported extensions before migrating a complete document. If the macro is unavailable, use Confluence's native editor tools or another approved import path instead of assuming raw Markdown will render.

Understand what the Markdown macro does

The Markdown macro provides a container for Markdown content inside a Confluence page. It is useful when the source already uses Markdown and you want to preserve a readable block without rebuilding every element in the visual editor. The macro does not turn the entire Confluence editor into a Markdown editor. Content outside the macro continues to use Confluence's page model and editor controls. Availability can depend on the Confluence deployment, editor experience, permissions, and administrator configuration. If you cannot find the macro, do not paste raw Markdown into a normal paragraph and expect headings, links, or tables to transform automatically.

Insert and test the macro

Open the target page, place the cursor where the Markdown block should appear, and use the insert control to search for the Markdown macro. Add the source inside the macro body, then inspect the preview before publishing. Start with a small sample that includes one heading, one link, one list, inline code, a fenced code block, and a table if your content needs one. Check whether the parser supports the exact syntax you use. A macro can display content correctly while still producing unexpected spacing, link behavior, or table widths. Keep the original source in version control or a separate document until the Confluence result has passed review.

Plan for unsupported features and maintenance

Markdown extensions do not have one universal behavior. Custom directives, embedded HTML, footnotes, task lists, and application-specific attributes may appear as text or fail to render. Images and links also need attention because relative paths may not work inside Confluence. Use absolute, approved destinations or upload media through the method required by your workspace. Consider native Confluence content when readers need comments, page history, structured navigation, or editing by users who do not know Markdown. A converter can prepare the macro body and normalize common syntax, but it cannot confirm macro availability, permissions, or the long-term maintenance cost of a page built around embedded source.

How do you do it step by step?

1Confirm that your Confluence site offers the Markdown macro and that you can edit the target page.
2Prepare a small Markdown sample with the structures used by the full document.
3Insert the macro, paste the sample, and preview headings, links, lists, code, tables, and images.
4Replace unsupported syntax or choose native Confluence elements where readers need richer page behavior.
5Save the source separately, publish the page, and check the result with the intended reader permissions.

Working example

This sample is suitable for testing a Markdown macro before inserting a larger page.

Input

# Release checklist\n\nRead the [runbook](https://docs.example.com/runbook).\n\n- Confirm the version\n- Review the logs\n\n```bash\n./verify-release.sh\n```

Result

Release checklist\n\nRead the runbook.\n\n• Confirm the version\n• Review the logs\n\n./verify-release.sh

The rendered appearance depends on the macro parser and Confluence editor. Treat this output as a verification target, not a guaranteed visual match.

Frequently asked questions

Is Markdown native across every Confluence page?: No. Markdown support depends on the available macro, editor, deployment, permissions, and configuration. Check the site before planning a migration.
Does the Markdown macro convert the whole page?: No. It renders Markdown inside its macro container. Text and components outside that container use Confluence's normal page editor.
Why did my Markdown table or task list render incorrectly?: The macro parser may not support that syntax or extension. Test the feature separately and replace it with native Confluence content when needed.
Should I keep the original Markdown source?: Yes. Keep a separate source copy so you can revise, compare, or move the content if the macro or parser changes.