Legacy Editor deprecation: Key Dates and What to Expect (Dec 2025 Update)

[#1]

As shared in our initial deprecation announcement in June, full deprecation of the Legacy Editor is scheduled for April 2026.

We understand this is a major change. By standardizing on the cloud editor, we aim to provide every team with a single, streamlined editing experience and access to our latest features. We’ve dedicated the past several quarters to making this transition as smooth as possible. While there may be layout or formatting differences in some cases, your underlying content will remain intact.

Below, we’ve outlined the key dates and the impact on your site. For more technical details and FAQs, you’ll find additional resources linked at the end.

Key dates

What is changing and when:

Please note: All dates are Pacific Standard Time (PST)

• Phase 1: On Jan 21, 2026, you will no longer be able to create new pages in the legacy editor.

• Phase 2: From Jan 21, 2026 to Feb 18, 2026, automatic conversion of legacy pages will begin. From this stage onward, viewing or editing a legacy page will open it in the cloud editor. This rollout will occur gradually over several weeks and all sites will have this enabled by Feb 18, 2026.

• Phase 3: On April 1, 2026, the legacy editor will be fully deprecated.

What to expect

Phase 1: January 21, 2026

What will change

You will no longer be able to create new pages in the legacy editor. This includes:

• Creating new Confluence pages in the legacy editor.

• Duplicating legacy pages in a way that preserves the legacy editor.

• Creating new legacy pages from templates that use the legacy editor.

What you’ll see

• Actions that would previously create a legacy editor page (for example, using a legacy template or copying a legacy page) will instead open the cloud editor.

• Templates that used the legacy editor will open in the cloud editor when you edit them, and any new pages created from these templates will also be in the cloud editor.

Phase 2: January 21 – February 18, 2026

What will change
Automatic conversion of legacy pages begins:

• Viewing or editing a legacy page will open it in the cloud editor.

• This rollout will happen over several weeks (January 21, 2026 to February 18, 2026). By February 18, 2026, all sites will have auto-conversion enabled.

Please note: If your organization has multiple sites, phase 2 may be enabled at different times. You can manually enable auto-convert for your sites earlier if you wish.

What you’ll see

• After phase 2 is enabled for your site, users will see a pop-up modal informing them that pages are being auto-converted.

• Legacy pages will open in the cloud editor after phase 2 begins for your site.

• Reverting: During phase 2, you can still revert individual pages back to the legacy editor by clicking on the More actions (•••) menu and selecting Revert to legacy editor. Pages reverted during Phase 2 will remain in the legacy editor until Phase 3 begins.

Recommended action: Use phase 2 as your final window to review and adjust any especially complex or critical content.

Phase 3: April 1, 2026

What will change
The legacy editor is fully deprecated:

• All Confluence pages are viewed and edited in the cloud editor.

• Any pages that were reverted to legacy editor will be automatically converted again.

• The option to revert back to the legacy editor is removed. You will no longer be able to revert pages to the legacy editor.

What you’ll see

• Your content remains viewable and editable in Confluence Cloud using the cloud editor.

• For the small number of pages that remain unsupported, please note that the unsupported portions of these pages will still be viewable (but not editable) after the legacy editor is deprecated.

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, where we share updates such as the high-level feature support overview.

• To provide feedback directly:

  • Vote or comment on feature suggestions in jira.atlassian.com.

  • 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.

• For technical issues, open a support ticket so our team can properly track, troubleshoot, and provide updates on your case, so we can assist you more quickly than through Community discussions.