CKEditor 5 updates and maintenance

This section explains how to keep your CKEditor 5 installation up to date. It covers updating between versions, migrating to the new installation methods or the CDN, moving from CKEditor 4, day-to-day maintenance, and our versioning and release policy. Keep all CKEditor 5 packages on the same version, and update one version at a time to avoid unexpected issues.

Migrate your CKEditor 5 from an NPM-based installation to a CDN-based one (for example Vanilla JS). CDN-based installations can simplify the setup process by providing a bundler-agnostic way to lazy initialization of CKEditor 5 scripts and styles injection. It reduces complexity in the project setup.

This section will explore the new installation methods introduced in CKEditor 5 v42.0.0. These methods make CKEditor 5 much easier to use by reducing the number of possible installation paths and removing most of the limitations of the old methods.

If you want to switch to CKEditor 5 from our previous product, CKEditor 4, please refer to the dedicated Migration from CKEditor 4 guide that will explain all the differences between these two products and help you make the switch.

For general tips on how to take care of your CKEditor 5 installation, please refer to the Maintaining your editor guide for tips on how to provide the daily service and make the editor work efficiently and without interruptions.

Regular code releases bring new features and improvements to CKEditor5. Visit the Versioning policy section to check release practices and versioning strategy.

Visit the Updating CKEditor 5 guide for information on how to update your installation to the newest available stable version of the software. Visit the dedicated update guides for specific CKEditor 5 release versions if you need to catch up with the latest release.