Magento swapped TinyMCE for HugeRTE in late 2025, and the transition is now complete across 2.4.9. If you haven't audited your CMS content and custom widgets yet, here's the checklist.

If you've logged into the Magento admin recently and your CMS editor looks a little different, you're not imagining it. We first flagged Magento's move away from TinyMCE in our October 2025 patch round-up, and with 2.4.9 now generally available, the transition to HugeRTE is complete across the platform. If you upgraded straight from an older release and skipped the October 2025 patches, this is the first time you'll be meeting HugeRTE properly, so it's worth a proper content and extension audit rather than assuming it "just works" because the toolbar looks familiar.
The move wasn't optional, even if the timing felt sudden to some merchants. TinyMCE 5 and 6 (the versions Magento had relied on for years) reached their own end of life, and TinyMCE 7's licensing terms weren't compatible with Magento's open-source distribution model. HugeRTE, an MIT-licensed, community-maintained fork of TinyMCE, was the practical replacement: open licensing, active maintenance, and close API compatibility with what it replaced.
The honest answer depends entirely on how deeply something integrates with the editor:
Work through this before you consider the migration finished, not just before you upgrade:
For content that renders incorrectly after the switch, the fix is usually re-saving the content through the new editor rather than anything more invasive: HugeRTE will often clean up minor formatting inconsistencies the moment the content passes through it again. For an extension that's genuinely broken, check for a vendor update first; if none exists and the extension is business-critical, that's a conversation worth having with whoever maintains your custom code before you're relying on a visibly broken WYSIWYG field in production.
This is a small, slightly annoying piece of migration admin rather than a serious technical risk. It's exactly the kind of low-severity, high-annoyance issue that generates a string of support tickets in the weeks after an upgrade if nobody does the audit up front. Twenty minutes with this checklist in staging saves considerably more than twenty minutes of "why does this page look wrong" tickets in production.
If you'd rather we run this audit as part of your 2.4.9 upgrade testing, get in touch with Deploy: it's a standard part of how we validate a Magento upgrade before it goes live.
Sources: mgt-commerce's Magento 2.4.9 feature breakdown, Firebear Studio's compatibility notes on the 2.4.9 upgrade.
Last updated 21 May 2026.