CKEditor 5

Drupal core's visual editor for text fields, set up per text format, where the toolbar and the allowed HTML tags are configured together.

Drupalを学ぶDrupal用語集 Last updated

CKEditor 5 is the rich text editor built into Drupal core. It gives editors a toolbar for headings, bold text, links, lists and images inside text fields, and Drupal stores what they write as HTML. Each text format decides which editor it uses and which HTML tags survive. In Drupal 11.4, it is the only rich text editor that ships in core.

How it works in Drupal 11

CKEditor 5 is a core module named ckeditor5. It builds on the core Editor module, which keeps one editor configuration for each text format. For CKEditor 5, that configuration lists the toolbar items and the settings of each plugin. In Drupal 11.4.10, the Standard installation profile ships this configuration for Basic HTML and Full HTML; it ships none for Restricted HTML.

You manage it at /admin/config/content/formats. In the admin menu the link sits under Configuration › Content authoring, and the page title is Text formats and editors. The editor form has the sections CKEditor 5 toolbar configuration and CKEditor 5 plugin settings.

Every toolbar button belongs to a plugin. Core defines its plugins in ckeditor5.ckeditor5.yml. A module adds its own in a file named {module_name}.ckeditor5.yml and can change existing definitions with hook_ckeditor5_plugin_info_alter().

The editor and the HTML filter work as a pair. When a format uses the filter named Limit allowed HTML tags and correct faulty HTML, CKEditor 5 fills in its Allowed HTML tags field from the enabled plugins and makes the field read-only. To allow tags that no enabled plugin covers, you use the Source editing plugin and its field Manually editable HTML tags.

Status and history

Checked on 26 October 2026: Drupal 11.4.0 came out on 1 July 2026, and its announcement says text formats using CKEditor can now include a Fullscreen plugin, which expands the editor to the whole browser viewport. The plugin is defined as ckeditor5_fullscreen in the core plugin file.

Example

An editor asks for a distraction-free writing view on long articles. A site builder opens /admin/config/content/formats and configures the Full HTML format. In the toolbar configuration, the builder moves Fullscreen from the available items into the active toolbar and saves. In the Standard profile of Drupal 11.4.10, the Full HTML toolbar does not include this button, so it has to be added.

The same screen answers another request. If a page needs a definition list, the builder enables Source editing and types <dl> <dt> <dd> into Manually editable HTML tags. Editors then paste or type that markup in the Source view.

Common mistakes

  • Listing tags in Source editing that a plugin already covers. Core refuses to save such tags in Manually editable HTML tags and names the plugin to enable instead. Enable the plugin, so editors get a button rather than raw HTML.
  • Giving every role the Full HTML format. Core creates a permission named Use the (format name) text format for each text format and warns that it may have security implications. Grant the permissive formats to trusted roles only.
  • Expecting a CKEditor 4 plugin to keep working. A plugin written for CKEditor 4 does not run in CKEditor 5. Look for a CKEditor 5 release of the module before you plan an upgrade.

For marketing and content teams

The toolbar you see is the toolbar of your WYSIWYG text format, not a fixed feature of Drupal. If a button is missing, the format is configured without it; ask a site builder to add it at /admin/config/content/formats rather than pasting raw HTML. In the Standard profile, the Basic HTML toolbar includes a Source button, so editors with that format can view and edit the HTML directly. A format that uses the filter limiting allowed HTML tags removes other tags when the text is shown, so markup pasted from other tools can disappear.

Sources

Questions about CKEditor 5

The Drupal 11.4.0 release notes (1 July 2026) say CKEditor was updated to CKEditor 5 version 47.6.2. Patch releases can move it: in Drupal 11.4.10, core/core.libraries.yml declares version 47.6.3-drupal.1 for the ckeditor5 library. Look in that file on your own site for the exact number.

With CKEditor 5, the enabled toolbar buttons and plugins decide which tags and attributes are allowed, so Drupal generates the list and locks the field. Core's own help text says that removing tags by hand would break enabled features. To allow more tags, enable the Source editing plugin and list them under Manually editable HTML tags.

Not from core. Drupal.org states that CKEditor 4 was removed from core in Drupal 10 and calls it end-of-life. The contributed CKEditor 4 project page (checked 26 October 2026) marks the module Unsupported and Obsolete and outside the security advisory policy. Drupal.org strongly recommends moving to CKEditor 5.

CKEditor's licensing page says its open-source distribution is licensed under GPL 2 or later, and that it sells commercial plans. The contributed CKEditor 5 Premium Features module adds paid plugins such as real-time collaboration and requires a license key; its project page lists a stable release 1.8.6 from 14 October 2026 for Drupal 10.3 or 11.

Cite this definition

"CKEditor 5." DXPR Drupal glossary, https://dxpr.com/hc/documentation/learn-drupal/drupal-glossary/ckeditor-5. Last updated October 26, 2026.

Related terms

All Drupal terms from A to Z