This page documents known limitations and issues in the current release. Workarounds are provided where available.
Some Confluence macro types do not have a direct Markdown equivalent and are handled with best-effort conversion.
| Element | Behavior |
|---|---|
| Jira issue macros | Rendered as plain text with the issue key (e.g. PROJ-123) |
| Confluence macros (expand, status, etc.) | Inner content is preserved; macro wrapper is stripped |
| Inline comments | Not included in the export |
| Task lists (action items) | Converted to - [ ] checkbox format where detectable |
| Page properties / metadata macros | Not included |
| Confluence whiteboards | Not supported — whiteboards have no page content to export |
| Emoticons / Confluence emoji | Replaced with the nearest Unicode equivalent or stripped |
Exporting a space root with hundreds of pages may cause the initial tree load to take several seconds. The tree loads all descendants in a single recursive fetch — this is a known performance limitation for very large spaces.
Workaround: Open the exporter from a specific section page rather than the space root to reduce the number of pages loaded.
Attachment downloading is done in parallel batches with rate limiting. On instances with strict API rate limits or very large attachments, downloads may be slow or occasionally fail.
Workaround: If attachment downloading fails, re-run the export with Include attachments unchecked and download attachments manually.
In single-file mode, YAML front matter from individual pages is included inline between --- dividers. Some tools that parse front matter (e.g. Jekyll, Hugo) only recognize front matter at the very top of a file. The per-page blocks in the middle of a single-file export will not be parsed as front matter by those tools.
Workaround: Use ZIP export if you need front matter to be recognized by static site generators.
The exporter only exports pages the authenticated user has permission to view. Pages the user cannot access are silently excluded from the export — they will not appear in the page tree and will not trigger an error.
If a page is missing from the tree, verify you have view access in Confluence.
If you encounter a bug not listed here, please report it through the Atlassian Marketplace support portal.
