FAQ: Understanding legacy editor deprecation
Learn about the phased deprecation of the legacy editor and find the answers to frequently asked questions.
The Confluence legacy editor
What was the legacy editor?
The legacy editor was the original editing environment in Confluence Cloud, largely mirroring the Confluence server experience. Our cloud editor is now the default in Confluence Cloud and across Atlassian.
The legacy editor was fully deprecated in April 2026. All Confluence content is now viewed and edited in the cloud editor, and pages can’t be reverted to the legacy editor.
We are improving the conversion path for legacy editor pages, which will allow a smooth process to get all your content into the cloud editor.
Full details are also available on the status of macros that existed only in the legacy editor. In most case, there is a new solution providing similar functionality in the cloud editor.
For details on how to convert content, consult the support topics listed here.
Convert legacy editor pages
Learn how to convert a page from using the legacy editor to using the cloud editor.
Differences using Confluence legacy editor and cloud editor
Dig into the details of how using Confluence Cloud is different from Confluence Data Center and Server for your end users.
Manage legacy pages and templates with space admin tool
Space admins can use a dedicated tool to view a list of legacy pages and templates in their space.
Share and comment on files in the legacy editor
Share files with collaborators, or comment on files other people have shared.
The legacy content macro
Work with legacy editor content in a cloud editor page
Was this helpful?
Still need help?
The Atlassian Community is here for you.