• Products
  • Documentation
  • Resources

Convert pages to the cloud editor

Are you ready to experience a more efficient and modern way to create content in Confluence Cloud? Do you want to use a robust editing environment that offers many benefits, including real-time collaboration features, an intuitive interface, streamlined workflows, and the benefits of Atlassian platform capabilities? This guide will walk you through converting your content from the legacy editor to the cloud editor and discover how the cloud editor can help you create and share content more quickly and efficiently.

Advantages of using the cloud editor

You can elevate your content creation experience with the cloud editor's powerful features:

  • Enhanced collaboration: Work seamlessly with your team in real-time and witness edits as they happen. Discuss ideas through improved commenting features with mentions and reactions, and manage tasks efficiently with streamlined workflows.

  • Streamlined workflows: Enjoy a user-friendly interface that simplifies content creation and navigation. Easily format your content with various options like tables, headings, and code blocks, and experience faster loading times for a more responsive editing experience.

  • Future-proofed content: Benefit from ongoing updates and regular improvements to the cloud editor, ensuring your content remains compatible with future advancements across Atlassian products. Since the cloud editor is the unified editing experience for all Atlassian apps, you'll gain access to platform features like Atlassian Intelligence and Smart Links. This consistency lets you learn the editor once and seamlessly leverage its capabilities across your Atlassian workflows.

Use the cloud editor to unlock a more collaborative, efficient, and future-proof way to create and manage your content in Confluence Cloud.

You will have the option to continue to create pages in the legacy editor.  However, there are some downsides to continuing to use the legacy editor:

  • No bugs fixed in the legacy editor unless it's a major incident

  • No enhancements made to the legacy editor

Which editor does your page use?

You can see which editor your page uses by looking at the differences in the editor toolbar.

  • The New editor: Includes Publish… or Update and Close buttons in the top menu and the emoji icon

  • The Legacy editor: Has earlier versions of text-color picker and page formatting

New editor
Legacy editor
Image highlights the unique tools that make the toolbar in the legacy editor different than the one in the new editor

Convert your pages

Ready to switch to the cloud editor? Here's a quick guide to get you started:

Pages that can be converted from the legacy to new editor display a notification.
  1. Identify pages: When page conversion is turned on for your instance, you'll get a banner notification at the top of the first page you edit and a notification at the lower left of the page.

  2. Preview page: Use the preview option to see how your page will look in the cloud editor before committing to the conversion.

  3. Convert page: Select the Convert page to begin the conversion process.

  4. Additional resources: Explore our support documentation or knowledge base articles for further guidance and troubleshooting tips.

Note: Most content converts seamlessly, and minimal adjustments are needed. However, refer to the "Understanding Conversion Details" section for specific elements that require attention and further guidance.

Enable auto-conversion in a space

Space admins can enable auto-conversion from legacy to the new editor for all pages with eligible content in a space. To do this:

  1. Go to the space in Confluence Cloud.

  2. Select Space settingsfrom the sidebar.

  3. Select Convert pages from the Manage space card.

  4. Toggle Convert pages automatically to the on position.


View of auto-convert editor function

If auto-conversion is enabled, eligible pages will be previewed in the new editor until published, at which point the new editor is “saved.” This can be reverted to legacy in page history.

If auto-conversion is not enabled, only pages that were published in the new editor will stay in the new editor.

Rolling back

If you find that a page you have migrated to the cloud editor does not work correctly and updating it is not an option, you can roll back a conversion by reverting it to a version that uses the legacy editor in the page history. See here for how to restore an older version of a page.

Understanding conversion details

Most elements convert smoothly to the cloud editor, requiring no additional adjustments on your part. However, a few specific elements might need your attention for optimal presentation or functionality in the new environment.

For guidance on these elements, please refer to our dedicated Knowledge Base article: Understanding legacy editor element conversion in Confluence Cloud. This article provides detailed explanations of elements that require adjustments and alternative approaches and solutions within the cloud editor.

Next steps and support

With the cloud editor, you're now equipped to create and manage content in Confluence Cloud more efficiently and collaboratively than ever before.

Remember, the cloud editor constantly evolves, offering regular updates and improvements. To stay on top of the latest features and functionalities, we encourage you to explore the following resources:

  • Atlassian Community: Connect with other Confluence Cloud users and share your experiences.

  • Support articles: Access more detailed guides and troubleshooting tips for Confluence Cloud.

We encourage you to explore the full potential of the cloud editor and unlock a more collaborative and efficient way to create and manage your content in Confluence Cloud.


Still need help?

The Atlassian Community is here for you.