The Legacy Editor is being deprecated in Confluence Cloud: Here’s what you need to know

[#1]

We are announcing the deprecation of the legacy editor in Confluence Cloud, with full deprecation planned for April 2026. With the deprecation of the legacy editor, you can expect:

• A Single Editing Experience: All editing will move to the cloud editor, which already powers collaboration for most users and offers advanced features such as Live Docs, AI, Smart Links, and automation.

• Content Preservation: Legacy content will be automatically preserved using the Legacy Content Macro and other native solutions.

Why we're making this change

After placing the legacy editor in maintenance mode for years, we’re now taking the final step to deprecate it. By focusing on the cloud editor, we can deliver a unified, modern editing experience for all Confluence Cloud users, and empower users to:

• Work better together: Real-time collaboration, inline commenting, and Live Docs keep everyone on the same page and make teamwork seamless.

• Get more done, faster: Smart links and embedded content let you create rich, interactive documents, making it easier and more efficient to share information.

• Let AI do the heavy lifting: Built-in automation and AI-powered features help reduce repetitive tasks, enhance content creation, and ensure writing is polished and professional.

Key Deprecation Dates

We’re taking a phased approach to deprecating the legacy editor to ensure a smooth and successful transition for all customers. Our top priorities are to remove blockers from the conversion process—so your content remains intact—and to close key gaps between the Legacy and cloud editors before the deprecation is complete.

• Phase 1 (January 2026): New pages cannot be created in the legacy editor, including copying legacy pages or creating new pages from legacy editor templates.

• Phase 2 (January 2026 - March 2026): Viewing or editing a legacy page will automatically convert it to the cloud editor.

• Phase 3 (April 2026): legacy editor is fully deprecated; all content is viewed and edited in the cloud editor and pages cannot be reverted back to legacy editor.

Preserving Legacy Content

You are not required to take specific action for this deprecation, as our solutions are designed to enable a smooth, automatic conversion. We’re focused on ensuring the transition to the cloud editor is as straightforward and smooth as possible:

• Closing Feature Gaps: We’re focused on addressing the highest priority customer needs so that by the time of deprecation, nearly all pages can be converted seamlessly—minimizing manual effort required. Support for legacy pages with nested macros (through the legacy content macro) and nested tables is already available, along with new features to power better real-time collaboration in the cloud editor.

• Automatic Conversion: You are not required to take action to manually convert legacy pages. Eligible legacy pages will be automatically converted to the cloud editor according to our deprecation timeline. Content will remain viewable and editable after the deprecation, even without manual intervention.

• Legacy Content Macro: For complex or unsupported content (like nested macros), we’ve built the Legacy Content Macro to preserve your content and ensure that it remains editable in the cloud editor. We’re actively expanding support for additional use cases over the next quarter.

• Admin Controls: Site and space admins can enable auto-conversion settings to streamline the process for their teams. This is not required, but can help admins get a proactive head start on the transition. Pages with unsupported content that can’t be converted yet will remain in the legacy editor and won’t be auto-converted until support becomes available.

While no action is required for most customers, if you have especially complex legacy pages, we encourage you to convert eligible pages early and share feedback. Your input helps us refine our solutions and support you better.

Stay Informed and Provide Feedback

If you have questions or want to stay informed during this transition, we’re here to help:

• Start with our Help Center for FAQs and documentation.

• For answers to the most common questions and more details about the deprecation plan, visit our Deprecation Details & FAQ page.

• For ongoing updates, announcements, and discussion, join our Legacy Editor Deprecation community group.

• To provide feedback directly, use the in-product feedback option in Confluence by clicking on ? in the header (next to your profile photo), selecting “Give Feedback,” and choosing “Editor” from the menu.

[Josh]

@Elle Ky thank you for:

1. The clear communication
2. in multiple channels (e-mail and Community post)
3. with ample notice to prepare

Greatly appreciated.

[Eric van Dijken]

Without the legacy editor , confluence lost it. I guess this is goodbye.

[Rodney Estrada]

Time will tell how I end up feeling about this.

[Matt Baillargeon]

This is great news. Really looking forward to having an all in one editor and not having some articles written with new editor and others with the old one.

So far we have converted a few articles to the new editor and have not noticed any data loss, so hoping for the same when all articles created with old editor are moved over.

Extra points for little no work on the admin side besides communicating to end-users. That is a win!

[Rick Westbrock]

I don't think this will negatively impact us as the last gap for us of the new editor not supporting nested tables has been recently resolved.

[Rebekka Heilmann _viadee_]

Pleasently surprised by how early and well this is communicated. I personally don't mind the change at all and hadn't had any users complain about converting pages and losing content in the past couple of months - so I am assuming that it now works seemless.

Thank you @Elle Ky 

[Daniel Howard]

How can we block access to AI FEATURES at the organization level? Thanks!

[Erin Dethlefsen]

Is there a way I can identify legacy content in my company's Confluence instance?

[Kent Chiu]

Thank you for the early warning about the deprecation. That helps us to plan for converting the affected legacy pages.

Is there any way to list all the pages in Confluence Cloud that still use the legacy editor? Is there a bulk conversion tool?

Thanks,

[Shraddha]

Thanks for the updates but would love to see more use cases/videos of the change impacts so that we are prepared in advance. 

[Sami Shaik]

Thank you for sharing these important updates regarding the Legacy Editor deprecation in Confluence Cloud.

While we understand the need to streamline and standardize the editing experience across the platform, I would like to highlight a few concerns from our recent experience. We have already migrated our Jira, Confluence, and JSM instances to the cloud, and as part of that transition, we attempted to convert some of our recently migrated Confluence pages to the new editor.

Unfortunately, we encountered several challenges during this process. Specifically, some of the converted pages did not retain the intended formatting, and certain Confluence native macros are not functioning properly after the conversion. This has impacted both the readability and usability of those pages, especially for critical knowledge base articles and internal documentation.

We fully support the direction towards modernization, but we hope Atlassian can address these gaps to ensure a smoother transition. Is there an updated roadmap or best practices guide to help mitigate such issues during the conversion process? It would also be helpful if more stability improvements for macros compatibility are prioritized.

Appreciate the efforts the Atlassian team is making, and looking forward to further enhancements to ease this transition.

Thank you.

[Laurie Hickey]

@Erin Dethlefsen and @Kent Chiu , I had the same question as you about getting a list of Legacy pages and found this issue you can upvote: CONFCLOUD-77396.  (You can link over to it from the FAQ page noted above.  Of course, since we are on the clock to get pages converted, development of this feature may be too late. :(

[Todd Lewis]

I'm going to miss the ability to color-code fixed-width text. And it's not like the widgets aren't there in the new editor; they are. They just don't do anything. Our carefully color-coded documents are going to become laughably useless when this change hits those pages.

[Arslan Razi]

How can I tell if I am using the Legacy Editor or the new one? 

[Ferry Portier]

What I do experience positively is that there is now early communication about it. Since we purchase services from Atlassian, I do expect support in this.

Since we have multiple spaces and do not know which ones the Legacy editor is still active on, it would be desirable if Atlassian also provided us with some tools that make this clear and with which a bulk conversion can be performed.

[Øyvind Matheson Wergeland]

I hope https://jira.atlassian.com/browse/CONFCLOUD-78762 is on your list of missing features in the new editor. Unless that is fixed, we have some pages that will become very hard to use in the new editor.

[Kevin Gérard]

Thanks for the (timely) Communications! 

It would help a lot if as an admin, i get pull a list of 'legacy' pages. That way i can assess wth the required stakeholders what actions we want to take. 

we've got close to 50K pages in our environment, and i dare say that's not even a lot...

[Thorsten Boedeker]

I hope the automatic page conversion improves in the near future.
Inline graphics, image formatting, tables, too white space to the left etc. need to be optimized, we have many pages in the Legacy editor and would have to edit them manually in order to migrate properly.

[Dan Iveson]

I have been consistently using the Legacy editor because it is better than the new one. If you Atlassian are going to force us to use the new editor then please address all logged issues regardless of what you perceive the priority to be. The new editor is a serious regression of the Legacy editor.

[Danja Karenko]

@Arslan Razi , when viewing an individual page, the text "Legacy editor" is displayed next to the update + viewer info if the page uses it. If you don't see that written in this place, the page uses the new editor. 



The pages also look different both in view and edit mode -- the Legacy editor has smaller font, less white space, and more tell-tale signs. By default, newly created pages use the new editor. You can only get a new page with the old editor by copying an existing page that still uses the Legacy editor. I assume most users are not aware of this.

For a more global report:
- People have pointed to the API (see this comment). I have not tried this myself, so no guarantees.
- This feature request might be of interest: CONFCLOUD-77396

Hope that helps!

[Frank Kulla]

I agree that it's good to get this information so early. In case someone didn't already know - here is the link to the confluence page where you can see the differences between the old legacy editor and the new editor:

https://confluence.atlassian.com/confcloud/converting-pages-to-the-new-editor-993930226.html 

Nevertheless we need Atlassian to put some more effort in preparing for that forced migration. There are macro's which can't be converted, or seem to require some manual actions after migration. A list of any kind where we can see where those macro's are used so we can take actions in advance is a must-have imho. Even if we have to open each space individually to access that list would be far better then left with having nothing.

They already have a feature suggestion for that, so please put in your votes for it:

https://jira.atlassian.com/browse/CONFCLOUD-77396 

[Gabby Williams]

Admins can use a script to export a CSV list containing the conversion eligibility of of all legacy editor pages. Instructions on how to create this list can be found here: https://confluence.atlassian.com/confkb/export-list-of-legacy-pages-and-their-eligibility-status-1587937727.html 

@Kevin Gérard @Ferry Portier @Laurie Hickey @Kent Chiu @Erin Dethlefsen 

[Keith Furnell]

Please fix CONFCLOUD-81426 / CONFCLOUD-81963, or the underlying gaps in macro support, first - otherwise this will effectively result in enforced data loss.

Please also improve on the random white space changes, table column width changes and image alignment changes that can occur upon conversion of "compatible" pages.

[Müller Miroslav]

For Atlassian team - The following conversion issues need to be fixed before this change:

1. Tables which have empty cells get all such cells filled with an additional newline when converted -> This leads to significant unnecessary vertical stretching of tables ⚠️. Manual removal of such individual newlines is labor intensive and time-wasting.
2. Header rows or columns get un-bolded -> Again manual labor needed to bold the text again.
3. At some places, newlines between tables on a page get duplicated. -> Again this leads to unnecessary tall pages and it needs to be deleted manually.

Our older projects have nearly all pages in the old editor and we need them for documentation. Any automatic conversion without manual fixing will lead to visual crippling of such pages⚠️.
We believe you do not want to lose your customers so we hope you will address those issues before forcing conversion. Thank you.

[Rick Westbrock]

Good callout on the table header text being "unbolded" on conversion @Müller Miroslav, that always bugged me as it seems like such a simple thing to fix.