A deep dive into CKEditor's Image Optimizer, powered by Uploadcare — what it does under the hood, how it slots into an existing CKEditor setup, and where it actually changes the day-to-day for authors and developers.
Released: Thu Oct 09 2025
What the session covered
Have you ever uploaded a 12 MB hero image into a CMS field that absolutely did not need 12 MB? I have. Image handling is one of those quiet bottlenecks — too easy to ignore, too painful to keep ignoring. Slow uploads, oversize assets, unnecessary processing on the client, formats that don't play nicely on mobile. The cumulative cost is real.
The deep dive
- What the CKEditor Image Optimizer (powered by Uploadcare) actually does — under the hood.
- Configuration and plug-in steps: where it slots into an existing CKEditor setup.
- Trade-offs and gotchas — there's always one.
- What changes for authors and what changes on the CDN bill.
Who it was for
Developers handling rich media in CKEditor, content engineers who own the upload pipeline, and anyone tired of asking authors to please just compress the JPEG. Voila — a workflow that does it for them.