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
Customers 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: Customers 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: 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.
What App Developers Should Know
Some third party macros may not be fully compatible with the cloud editor, which could result in content that is viewable but not configurable after conversion. We recommend that developers test their apps in the cloud editor and prepare a support plan for customers during the transition if needed.
Overview of legacy content solutions
We’re closing key compatibility gaps by adding native support for common nesting scenarios, like nested tables, to make converting content to the cloud editor as smooth as possible.
For Nested Bodied Macros and certain other unsupported nesting combinations that won’t receive native support, we will provide support through a Legacy Content Macro. This macro automatically wraps around unsupported content, allowing users to continue editing legacy content within the cloud editor.
For example, if a legacy page has a nested macro scenario - e.g. macro C inside macro B inside macro A ( Macro A > Macro B > Macro C) - it will be converted to Macro A > Legacy Content Macro > Macro B > Macro C. Users can edit the content within the Legacy Content Macro and add more content or nesting as needed.
We’ll continue to expand its capabilities over the next two quarters to support additional use cases and ensure a conversion path for all legacy pages. For example, in the coming months, we’re focused on: adding support for more nesting scenarios (such as nesting tasks) through the Legacy Content Macro, improving performance to better handle large or complex legacy pages, and addressing the conversion of legacy templates.
Before - Nested macros in legacy editor
After - Nested macros in cloud editor with Legacy Content Macro
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 customers in 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.
Thank you for your ongoing collaboration as we work to improve the Confluence Cloud experience!