Switch to the Tabs macro

Switch to the Tabs macro

With the arrival of the new editing experience in Confluence Cloud, which does not support nested bodied macros (CONFCLOUD-68323), the Tab Group and Tab macros do not work properly in the new editor.

To continue using your tabs and enjoy future improvements, we recommend converting to the new Tabs macro available in the page editor. It offers an all-new macro tailored to work with the new editing experience in Confluence Cloud, while also providing backward compatibility with the legacy editor.

 

If you recently migrated your pages from Confluence Data Center or Server, all your migrated pages in the Cloud still use the legacy editor. 

You can keep using the Tab and Tab Group macros if you don't plan to convert your pages to the new cloud editor.

The Tab and Tab Group macros are quite different than their server counterpart. Take note of the list of the Incompatible macros when nested within Composition Cloud's Tab and Tab Group macros.

However, if you plan to or have converted to the new cloud editor, consider switching to the Tabs macro because the Tab and Tab Group macros don't work properly in the new cloud editor.

You can convert content from the existing Tab Group and Tab macros to the new Tabs macro automatically or manually.

Convert content automatically

Things to know before doing the conversion:

  • Some macros inside the tab might be lost. For information about the macros support, see Tabs

  • The conversion process creates a new version of the page. 

  • If the content does not render properly after the conversion, you can restore the previous version of the page using the page history.

  • For full features support of the Tabs macro, convert the page to the new cloud editor. This is a separate process that you can perform after the conversion to Tabs macro.

Convert the macros automatically

  1. Find a page that contains the Tab and Tab Group macros.
    You can see the following Legacy macro warning message on the page.

  2. Click Legacy macro to reveal more information and to access the converter tool.

  3. To start the conversion process, click Switch to Tabs. The conversion process might take some time to complete.

    When the process is complete, the Tab and Tab Group macros are converted to the Tabs macro. If you edit the page, you can now see the JSON text format used by the new cloud editor. This is expected behavior because you are still in the legacy editor. While we recommend you convert the page to the new cloud editor (see the steps later), there might be reasons to continue using the legacy editor. For example, the tabs might contain certain third-party macros that are not compatible with the new cloud editor.

  4. If you want to update the content of the tabs, click the macro area, click Edit, update the content, and click Save.

Convert the page to the new cloud editor (recommended)

As long as the page is in the legacy editor, it shows the JSON text format. Follow these steps to convert the page to the new cloud editor.

  1. Open the page in edit mode.

  2. Go to the bottom of the page, locate the option to convert the page to the new editor, and click Preview page.

Note: The legacy-to-new editor converter tool is a part of Confluence Cloud (Atlassian).

  1. Click Preview your page first and click either Preview or Convert page.

    After a few moments, the page converts to the new editor and is published.

  2. To validate the successful conversion, open the page in edit mode again.

    You can see the new Tabs macro and its content.

Convert content manually

  1. Open the page in edit mode.

  2. Copy the content from a Tab macro.

  3. Add a Tabs macro.

  1. In the Tabs editor window, paste the content.

    Note that some formatting might be lost.

  2. Repeat the copy-and-paste steps for all your tabs.

  3. Save the macro and the page. Remove the old Tab Group and Tab macros if necessary.

 

Need support? Create a request with our support team.

Copyright © 2005 - 2025 Appfire | All rights reserved.