This documentation has moved. For the most recent documentation, check out Please update your bookmarks and links.

Skip to end of metadata
Go to start of metadata

Content Formatting for Confluence is a collection of 37 macros that helps to format content in Confluence easily, and enhance the appearance of content.

You can also view Content Formatting for Confluence on our Adaptavist website.


  • The latest compatible version currently is version 6.3.5  compatible with Confluence versions  6.5.0 - 7.0.1 

  • The add-on is Data Centre compatible
  • Please check the compatibility for other versions of Confluence from the Atlassian Marketplace.

Confluence v5.9 onwards requires Content Formatting for Confluence v4.4 or higher for some macros to function properly. This is because of a stricted macro rendering pipeline introduced by Atlassian in Confluence v5.9 onwards.

Content Formatting for Confluence v4.4 ends compatibility support for wiki markup. Please use v4.3 if wiki markup compatibility is required. Ideally pages should be upgraded as wiki markup has been deprecated since Confluence v4. Please take the note above into consideration when using v4.3 of Content Formatting.


Content Formatting for Confluence is available for installation from the Atlassian Marketplace, using Confluence Server Administration > Universal Plugin Manager (UPM), or via download from the Atlassian Marketplace.

Add-on Licensing 

Content Formatting for Confluence can be licensed via Atlassian through the Atlassian Marketplace.

Add-on Support

We offer add-on related support. Here you can read our SLA for Adaptavist Products and Add-ons.

Frequently Asked Questions

 Is Content Formatting for Confluence free or paid?

Starting from version 5.0.0, Content Formatting for Confluence is a fully paid add-on. This means we can invest in the future development of the add-on and, of course, it becomes fully-supported by Adaptavist’s support SLA.

 Iframes Macro doesn't work on my browser

If your Confluence is running on http then use of http in iframe will be fine. Although if your Confluence is accessed via https then use of http in iFrames won't work - it's a security feature of browsers. 

 PDF get downloaded instead of opening on a page

Atlassian has changed the way Confluence handles attachments since version 4.2. Now you need to do it by creating a page and using some Confluence built in macros to view the file. Please refer to the Confluence documentation to get more information.

 How to use CSS Stylesheet and CSS for macros

To be able to use the class parameter in any of the macros that has that option, you need to use the 'CSS Stylesheet' macro above them. You can follow the below example to see how it works:
1. At the top of the page insert a 'CSS Stylesheet' macro.
2. Inside that macro, you can then create a CSS class that can be used in all the macro's below the 'CSS Stylesheet' macro. Put the following css in there:

{ background-color: red; }

3. Once you've done that, you can now insert another macro, for example a 'Div' macro. Put some random text in the div. Make sure this macro is below the 'CSS Stylesheet' macro.
4. Once inserted, edit your 'Div' macro and, in the 'Class' parameter, enter the following: testClass
5. Now save your page and the div you created will have a red background.

Please note, CSS class names are case sensitive, so in the example above, you need to use a capital 'C'.

For more information on CSS, you can go to:

 Tabs as an Anchor

Please define individual IDs to the Tabs. Once the Tabs macro is inserted you should define its ID, which will act as an anchor tag. You don't need to insert the Anchor macro explicitly to the body content of the Tab page macro.

See the documentation for details.

 Cross Site Scripting (XSS)

As Confluence is a content-management system that allows user-generated content to be posted on the web, precautions have been taken within the Content Formatting Add-On to prevent cross-site scripting attacks:

The Content Formatting html macros specifically prevent the use of unknown HTML attributes, and all parameter values are checked against an allowable range to ensure that they are not being abused.

For example, where an html attribute has an 'enum' set of values, ONLY those values are allowed; where it's a free text attribute, the value is checked for breaking out of the attribute rules. If any 'bad' values are found a macro exception is thrown and the output is not rendered.

Additional Precautions:

  • All of the 'form' html elements are disabled by default and must be manually enabled by an administrator.
  • JavaScript attributes are not allowed and cannot be enabled e.g. 'onclick'.

Known Issues

 Tabs Macro compatibility issues with Team Calendars

 When Team Calendar is used in conjunction with AUI Tabs Macro, the calendar is not shown when it is placed within the 2nd, 3rd or nth tab.

The issue was investigated and confirmed that it was Team Calendar that was the cause. You can vote for this issue fix.

 Page properties report macro does not work
The page properties report macro does not work when the page properties macro is used within a Content Formatting macro. This issue is fixed from version 4.4.5, however it is important that a Search Index rebuild is triggered in Confluence administation section before the fix can take effect.

Export to PDF Issue

This add-on has a known issue when exporting a Confluence page to PDF. See this page for more details

Top of page