Macros that are unavailable or have limited availability in the Cloud editor
In the history of Confluence, we've occasionally made it far easier to do something without removing the more complex way of doing that thing. There was a time when you had to open the macro browser and find the strikethrough macro just to add a line through your text. We later added a strikethrough button to the toolbar (much faster!) but still kept that strikethrough macro around.
Below, you’ll find a list of all of the Macros that are unavailable or have limited availability in the Cloud editor. You can use the Macro Usage feature in Confluence Administration to better understand how they are used in your site.
No action is required on any existing pages using these macros. They will continue to work on existing pages and migrate from legacy to Cloud editor where applicable, without any loss of data. To learn more about how each of these macros migrates to the Cloud editor, see the tables below.
Macros that can be inserted in the legacy editor, cannot be inserted in the Cloud editor, and automatically migrate to the Cloud editor
With suitable alternatives for new instances in the Cloud editor:
| Macro | Macro Key | Status in legacy editor & Cloud editor | How this macro converts from the legacy editor to the Cloud editor | Alternative method in Cloud editor |
|---|---|---|---|---|---|
1 | Align | align | Can be inserted in the legacy editor Cannot be inserted in Cloud editor | When converted to the Cloud editor, Align macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Align macro cannot be inserted in the Cloud editor, we recommend aligning your content with the native align options in your toolbar. |
2 | Background color | bgcolor | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Background color macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Background color macro cannot be inserted in the Cloud editor, we recommend using a panel element.
|
3 | Center | center | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Center macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Center macro cannot be inserted in the Cloud editor, we recommend using the center align feature in the toolbar.
|
4 | Cheese | cheese | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Cheese macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Cheese macro cannot be inserted in the Cloud editor, just type "I like cheese!" |
5 | Code Block | codeBlock | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Code Block macros automatically convert to native Code snippet elements. However, new instances cannot be inserted. | Since new instances of the Code Block macro cannot be inserted in the Cloud editor, we recommend using the Code snippet element available from the menu or from the slash command ( / ). |
6 | Content by user | content-by-user | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Content by user macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Content by user macro cannot be inserted in the Cloud editor, we recommend using Confluence’s search feature and filtering by a user, then copy pasting the link into your content. |
7 | Copyright | copyright | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Copyright macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Copyright macro cannot be inserted in the Cloud editor, we recommend using your operating system’s symbol shortcut for ©:
|
8 | Create space button | create-space-button | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Create space button macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Create space button macro cannot be inserted in the Cloud editor, we recommend clicking “+ Create” in the top navigation and choosing “Space” |
9 | Fancy bullets | fancy-bullets | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Fancy bullets macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Fancy bullets macro cannot be inserted in the Cloud editor, we recommend adding them in manually, and indenting your list (although your bullets won't be outside of the indent). Alternatively, if you're planning on printing a page with bullets, you can export that page to PDF and use Confluence's PDF stylesheet function to style your bullets however you'd like. |
10 | Global reports | global-reports | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Global reports macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Global reports macro cannot be inserted in the Cloud editor, we recommend getting this information through space tools. |
11 | Highlight | highlight | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Highlight macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Highlight macro cannot be inserted in the Cloud editor, we recommend using the simpler highlighting feature in the editor toolbar.
|
12 | Loremipsum | loremipsum | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Loremipsum macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Loremipsum macro cannot be inserted in the Cloud editor, we recommend using Rovo to generate text for you or copy pasting from one of the many online tools to generate placeholder text. |
13 | Multimedia | multimedia | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Multimedia macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Multimedia macro cannot be inserted in the Cloud editor, we recommend inserting media directly into the page without needing to use a macro. |
14 | Navigation map | navmap | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Navigation map macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Navigation map macro cannot be inserted in the Cloud editor, we recommend using the child items macro. |
15 | Noformat | noformat | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Noformat macros automatically become native Code snippet elements. However, new instances cannot be inserted. | Since new instances of the Noformat macro cannot be inserted in the Cloud editor, we recommend using the native /Code snippet element. |
16 | Panel | info tip note warning panel | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Panel macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Panel macro cannot be inserted in the Cloud editor, we recommend using a panel element. |
17 | Privacy mark | privacy-mark | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Privacy mark macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Privacy mark macro cannot be inserted in the Cloud editor, we recommend inserting the lock and key icon from emoji picker in the toolbar.
|
18 | Privacy policy | privacy-policy | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Privacy policy macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Privacy policy macro cannot be inserted in the Cloud editor, we recommend directly inserting a link to your privacy policy. |
19 | Recently used labels | recently-used-labels | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Recently used labels macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Recently used labels macro cannot be inserted in the Cloud editor, we recommend using the more functional Related labels or Content by label macro. |
20 | Registered Trademark | reg-tm | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Registered Trademark macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Registered Trademark macro cannot be inserted in the Cloud editor, we recommend using your operating system’s symbol shortcut for ®:
|
21 | Search results | search | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Search results macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Search results macro cannot be inserted in the Cloud editor, we recommend directly inserting a link to Confluence search results. |
22 | Service Mark | sm | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Service Mark macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Service Mark macro cannot be inserted in the Cloud editor, we recommend typing “SM”, and apply the superscript formatting from the toolbar. |
23 | Space attachments | space-attachments | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Space attachments macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Space attachments macro cannot be inserted in the Cloud editor, we recommend adding a label to all the pages with attachments, then use a content by label macro. |
24 | Space details | space-details | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Space details macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Space details macro cannot be inserted in the Cloud editor, we recommend copy/pasting your space details from space tools. |
25 | Strikethrough | strike | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Strikethrough macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Strikethrough macro cannot be inserted in the Cloud editor, we recommend adding strikethrough formatting to your text using the strikethrough option in your toolbar. |
26 | Trademark | tm | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Trademark macros are still visible and editable. However, new instances cannot be inserted. | Since new instances of the Trademark macro cannot be inserted in the Cloud editor, we recommend using your operating system’s symbol shortcut for ™:
|
With no suitable alternatives for new instances in the Cloud editor (existing instances still migrate over):
| Macro | Macro Key | Status in legacy editor & Cloud editor | How this macro converts from the legacy editor to the Cloud editor | Alternative method in Cloud editor |
|---|---|---|---|---|---|
1 | Div | div | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Div macros are still visible and editable. Although, their content does not render as HTML. However, new instances cannot be inserted. | No alternative at this time. |
2 | Favorite Pages | favpages | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Favorite Pages macros are still visible and editable. However, new instances cannot be inserted. | No alternative at this time. |
3 | HTML comment | htmlcomment | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, HTML comment macros are still visible and editable However, new instances cannot be inserted. | No alternative at this time. |
4 | Style | style | Can be inserted in the legacy editor Cannot be inserted in the Cloud editor | When converted to the Cloud editor, Style macros are still visible and editable. However, new instances cannot be inserted. | No alternative at this time. |
Macros that can no longer be inserted in the Cloud editor OR the legacy editor, but are still visible in Confluence
| Macro | Macro Key | Status in legacy editor & Cloud editor | How this macro converts from the legacy editor to the Cloud editor | Alternative method in Cloud editor |
|---|---|---|---|---|---|
1 | Chart | chart | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Chart macro remains visible, but still cannot be edited. New instances cannot be inserted. | Since new instances of the Chart macro cannot be inserted in the Cloud editor, we recommend creating a table then using the “Insert chart” option for a better experience. |
2 | Contributors Summary | contributors-summary | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Contributors Summary macro remains visible, but still cannot be edited. New instances cannot be inserted. | Since new Contributors Summary macros cannot be inserted in the Cloud editor, we recommend using the Contributors macro. Note that you will not be able to get the same exact information with the Contributors macro. |
3 | Gallery | gallery | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Gallery macro remains visible, but still cannot be edited. New instances cannot be inserted. | Since new Gallery macros cannot be inserted in the Cloud editor, we recommend using layouts or tables, or the cards macro (only available on Premium or above). |
4 | Page Index | index | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Page Index macro remains visible, but still cannot be edited. New instances cannot be inserted. | Since new Page Index macros cannot be inserted in the Cloud editor, we recommend using a macro like Insert Confluence list, Child pages or Content Report Table. |
5 | Powerpoint | viewppt | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Powerpoint macro remains visible, but still cannot be edited. New instances cannot be inserted. | Since new Powerpoint macros cannot be inserted in the Cloud editor, we recommend uploading the file directly to Confluence content or paste a OneDrive smart link to embed files in Confluence. |
6 | Recently Updated Dashboard | recently-updated-dashboard | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Recently Updated Dashboard macro remains visible, but still cannot be edited. New instances cannot be inserted. | Since new Recently Updated Dashboard macros cannot be inserted in the Cloud editor, we recommend using the Recent updates macro. |
7 | Related Labels | related-labels | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Related Labels macro remains visible, but still cannot be edited. New instances cannot be inserted. | Since new Related Labels macros cannot be inserted in the Cloud editor, we recommend clicking on a page label to see a list of related labels. |
8 | Spaces List | spaces | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Spaces List macro remains visible, but still cannot be edited. New instances cannot be inserted. | Since new Spaces List macros cannot be inserted in the Cloud editor, we recommend using advanced search and filter by “Type: Spaces.” Then, copy and paste the link in your URL bar into Confluence content. Note that this does not support the same filters as Spaces List. You can also visit the space directory. |
9 | Word | viewdoc | Can no longer be inserted in the Cloud editor or the legacy editor Existing instances will remain visible, but cannot be edited. New instances cannot be inserted. | When converted to the Cloud editor, the Word macro remains visible, but still cannot be edited. New instances can not be inserted | Since new Word macros cannot be inserted in the Cloud editor, we recommend uploading the file directly to Confluence content or pasting a OneDrive smart link to embed files in Confluence. |
Macros that no longer exist in the Cloud editor or the legacy editor
| Macro | Macro Key | Status | How this macro converts from the legacy editor to the Cloud editor | Alternative method in Cloud editor |
|---|---|---|---|---|---|
1 | Confluence news gadget | N/A | Was never available in the Cloud editor. No longer visible, editable, or insertable in the cloud editor or legacy editor. | N/A | Link to the Atlassian cloud blog |
2 | Google Drive (Legacy Editor only) | google-drive-docs google-drive-sheets google-drive-slides | Was never available in the Cloud editor. No longer viewable, insertable, or editable in the legacy editor. Instead, they are replaced by a placeholder that recommends you convert to the Cloud editor. | When converted to the Cloud editor, the placeholders for the Google Drive (Legacy Editor only) macro will automatically convert to an embedded smart link. | Paste a link to a Google Drive file and it will automatically become a smart link that you can display as an embed. |
3 | IM presence | im | Was never available in the Cloud editor. No longer visible, editable, or insertable in the cloud editor or legacy editor. | N/A | Check your preferred instant messaging service. |
4 | JUnit Report | junitreport | Was never available in the Cloud editor. No longer visible, editable, or insertable in the cloud editor or legacy editor. | N/A | No alternative at this time. |
5 | Microsoft OneDrive for Business | N/A | Was never available in the Cloud editor. No longer viewable, insertable, or editable in the legacy editor. Instead, they are replaced by a placeholder that recommends you convert to the Cloud editor. | When converted to the Cloud editor, the placeholders for the Microsoft OneDrive for Business macro will automatically convert to an embedded smart link. | Paste a link to a OneDrive file and it will automatically become a smart link that you can display as an embed. |
6 | Rollover | rolloverwithoudbody | Was never available in the Cloud editor. No longer visible, editable, or insertable in the cloud editor or legacy editor. | N/A | No alternative at this time. |
7 | Span | span | Was never available in the Cloud editor. No longer visible, editable, or insertable in the cloud editor or legacy editor. | N/A | No alternative at this time. |
Was this helpful?