❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Current behavior

Currently image upload is working fine and uses data urls for uploading, this is very simple and does the job but the problem is that data URLs are quite large and take up to almost 30% more than the actual image size.
The old Markdown editor used server side image uploading instead, but the data flow is a bit unnecessarily complex.
Image conversion to and from markdown for both types of images is handled in PR #5189

Desired behavior

Find a way to convert image handling logic to use server side uploading in more streamlined way.
This may lead to editing on the custom conversion applied on the content before the to&from markdown image conversion.

Value add

Saves space.

Possible tradeoffs

Just settle with the current implementation for simplicity and bare the extra ~30% memory usage.