Q: Why are there so few macros compared to Content Formatting Macros for Confluence Server?

A: Our initial offering brings some of our most widely used Confluence Server macros to Cloud. We are planning on bringing as many macros to Cloud as possible, however, some simply won’t be practical given the current limitations imposed by the Cloud editor. If you want to learn more about how these limitations impact feature development, please see this blog from Atlassian.

Is there a macro that you would like to see supported in Cloud? Do you have an idea for a new macro? We want to hear from you! Please forward your requests and ideas via our customer support portal or our app feature feedback page.


Q: Why do some macros appear as Unknown Macro during or after a migration from Server to Cloud?

A:  Not all macros on Content Formatting Macros for Confluence Server are available in Content Formatting Macros for Confluence Cloud. Any macros that cannot be migrated, render with the Unknown Macro message. For more detailed information about what macros are available on what platform, check out table in the middle of the Support for Migrated Content page.

Please note, the content of any macros that cannot be migrated are still kept in the storage format of the page, so you can manually extract this content if needed.


Q: When I migrate Content Formatting Macros content from Server to Cloud will supported macros automatically render correctly or will I need to do anything?

A: Migrated content is rendered in Confluence's legacy editor. It will closely resemble your Server version with slight variations. You can edit your pages in the legacy editor before converting to the new Cloud editor. This is illustrated on our Converting Content to the New Cloud Editor page.


Q: Why don’t some Atlassian, Content Formatting, and other third-party macros work together?

A: Nesting - due to a limitation with Confluence?s current Cloud editor, rich text macros that allow customized formatting cannot be nested in other rich text macros. This means that you cannot include rich text macros in the body of other rich text macros as content. Additionally, each macro is contained in an iframe which is treated as a separate unit from the Confluence page. These are rendered individually, not as part of the page unit. The limitation has been imposed to prevent performance issues for users.

You can add bodiless or plain text macros such as a Button or Code Block macro to a rich text macro. These either have no additional text content area or allow only plain text without formatting such as color, special fonts, or attributes such as italics. Because we therefore can’t guarantee compatibility with every macro, we would like your feedback. Which macros do you want to see prioritized in our road map? Send us your requests via our customer support portal or our app feature feedback page.


Q: Why can’t I add more than one set of tabs or progress bars on the same page?

A: This is tied to the nesting issue above. The Tabs and Progress Bar macros in Server work as pairs; each with a container macro in which to nest the tabs pages or progress bar steps. We cannot offer containers in our Cloud macros. Instead, we treat each tabs page or progress bar step added to a page as part of a unit. Currently, you cannot assign a tab page or progress bar step to a particular unit but we endeavor to provide a more flexible solution where possible.


Q: Why can’t I export some macro content to PDF?

A: Due to a Confluence limitation, the Export to PDF functionality does not work with macros that require JavaScript to render on the Confluence page, e.g. LaTex macro. If you want to preserve your content in PDF format, we recommend that you use your browser’s built-in functionality to print to PDF.


If you have any further questions or require assistance with our app, simply submit a request through our customer portal. Our Support team will be happy to help.