• Products
  • Documentation
  • Resources

Convert pages to the new editor

When the page conversion functionality is available in your Confluence instance, you can:

  • choose which pages get converted to the new editor functionality and when.

  • preview any page before converting it.

  • restore a page to its previous, legacy editor version.


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

Page conversion

When page conversion is turned on for your site, you'll get a banner notification at the top of the first page you edit, and you’ll see a notification at the lower left of the page.  

Pages that can be converted from the legacy to new editor display a notification.

Convert a page

Before clicking convert, we want to give you a chance to see how the page will look in the new editing experience.

  1. Click Preview page.  More detailed information is presented about the process.

  2. Click Convert page.  Page refreshes, and the content appears in the new editor.

  3. Click Publish… to save the new editor version of the page.

Enable Space-Level Auto-conversion

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. Navigate to Space SettingsManage Space → Convert Pages

  2. Toggle on Convert pages automatically setting


View of auto-convert editor function

Enable Site-Level Auto-conversion

Site admins can enable auto-conversion from legacy to the new editor for all pages containing eligible content within a site.

  1. Navigate to Site SettingsFurther Configuration → Convert pages automatically

  2. Check Enable

auto-covert to new editor in further configuration within settings


If space or site 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 space or site conversion is not enabled, only pages that were published in the new editor will stay in the new editor.

What actually happens when your content is converted?

We want you to trust that we are handling your information properly. This table details all the elements that you can add to a legacy editor page in all their complex combinations. You can easily scan to find out which elements are available in which editor and what happens when a page containing that element is converted to the new editor. Most elements convert completely. However, for those which are modified slightly, you’ll find the details of what happens. If an element can’t be converted, you’ll find information about our short-term or long-term plans as well as Confluence Cloud Support requests if we are already tracking it. Keep in mind that this information will change as we refine the conversion rules and resolve the elements that can't be converted yet.

The following terms are used in the details of this page:

  • Rich body macro is a container in which the page creator/editor can type text or insert page el