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

[Darren Johnston]

we can no longer edit legacy pages?

select edit  > Time to convert your pages 
Select Not now goes to content cannot be found error?

 This issue is not mentioned in the update notes?

[Alejandro Fernandez]

I am very concerned about this.
I am programmatically generating html content for confluence and different email recipients.

With this change, I think I won't be able to produce the same html for both cases...

[Stuart Kinnear]

Nothing wrong with the Legacy Editor and nothing wrong with RI - Real intelligence. Just saying. Glad I am retiring and I am sick and tired of this ever sliding carpet called progress to stupidity.

[Brendhan Melanson]

Welp, they finally did it. As of today when duplicating pages from the Legacy editor they now automatically convert to the Cloud Editor.

RIP to the era of intuitive documentation. 

Currently in discussions to find a new intranet vendor. 

It was a fun 10 years while it lasted. Good job Atlassian.

[Michael Chan]

Hello Atlassian @Elle Ky ,


I am creating pages using the new api, but it is still creating them in the legacy editor (as of 1/22/2026). I know this is related to an old bug where larger pages would force to the old editor regardless of the api version used. Just double checking to make sure 1/21/2026 was the cut off date for any kind of legacy editor creation. Thank you

[Troy Dick]

This is sad news as the new editor made confluence no longer fit for purpose for what we use it for sad looks like i need to get a replacement from your competitor now thanks Atlassian