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

New Migrators: Starting in late July, customers who migrate to Confluence Cloud will have all eligible pages automatically converted to the cloud editor. 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.

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 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: For customers who have migrated to Confluence Cloud, 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 the ? in the header (next to your profile photo), selecting “Give Feedback,” and choosing “Editor” from the menu.

[Stefan Vollmer]

We started the Confluence Cloud migration on 17 July and received a lot of negative feedback about the new editor on migrated pages. Images, panels and tables are displayed so differently that pages have to be redesigned at great expense.
I am very disappointed with the approach and not convinced by the current conversion process.