My company has hundreds, maybe low thousands of pages, and we extensively use images throughout our documents. The current 'new' editor and method of displaying images is unacceptable. WHY can we not have multiple images inline? If there is no improvement before the forced conversion, we may have to seek alternative hosting. i am bringing this up here in hopes of hearing SOME kind of response so we know if we need to start looking for alternatives sooner rather than later.
This was brought up nearly a year ago. We did not press the issue because we were under the impression that the legacy editor 'would not go away' and that continued to work perfectly well for our needs: https://jira.atlassian.com/browse/CONFCLOUD-68501
There are numerous additional comments with concerns here: https://community.atlassian.com/forums/Confluence-articles/The-Legacy-Editor-is-being-deprecated-in-Confluence-Cloud-Here-s/ba-p/3046832
We have a seemingly very simple request. How do we get this:
To look like this:
...in the 'new' editor?
Precisely. We have just a few more weeks before we will be forced to make a company decision to either cut ties with Confluence, find a better-supported solution, and begin a major transfer or redesign our entire product pipeline and output process to conform to their now more constrained system. Both prospects are going to be costly and labor-intensive.
Hi @Chris
Thank you for sharing your concerns, and I apologize for the frustration and delay. We understand how important images are for your team’s workflow.
We’re aware of a bug affecting the conversion of pages with multiple images in a single line and are prioritizing a fix. You can follow progress and further updates here: CONFCLOUD-69374. Once this is fixed, you will be able to convert your existing legacy pages with this pattern. However, this fix will not support creating new side-by-side images in cloud editor.
The cloud editor currently doesn’t support adding new side-by-side images like the legacy editor. This is still something we need to evaluate further as we continue to gather feedback and assess demand, but can’t commit to a timeline yet.
The fact that the Cloud Editor still can't support something as basic as in-line images is beyond staggering - it's embarrassing.
This isn't some niche power-user demand; this is table-stakes functionality that literally every competent editor on the planet has offered since the early 2000's. Yet here we are, in 2025, watching Atlassian proudly 'modernise' their product by ripping out features like it’s some sort of minimalist art project.
Somehow, Atlassian have managed to send us backwards in time. It's like using a 'modern' platform that's literally less capable than stuff we had in 2005.