Supported Editors Matrix
Drupal 7 will no longer be supported after January 5, 2025. Learn more and find resources for Drupal 7 sites
Wysiwyg offers out of the box support for the following rich text editors: CKEditor, EpicEditor, FCKeditor, jWYSIWYG, markItUp, NicEdit, TinyMCE, Whizzywig and WYMeditor.
All of the rich text editors currently supported by WYSIWYG are unmaintained/obsolete as of 2024-08-28. Contribute to adding support for CKEditor 5 [Issue #3123281] or TinyMCE 6 [Issue #3413569].
Alternatively consider the CKEditor 4 LTS or Editor modules.
Supported Editors
The chart below outlines the current state of editor support as of 2024-08-28:
| Editor | Min Ver. | Max Ver. | Notes |
|---|---|---|---|
| CKEditor | 3.0.0 | 4.23.0 |
CKEditor 5 unsupported. [Issue #3123281] |
| EpicEditor | 0.1.1 | 0.2.2 |
EpicEditor 0.2 supported. Not recommended. End of life March 2020. |
| FCKeditor | 2.6.0 | 2.6.11 | FCKeditor 2 supported. Not recommended. End of life 2010. |
| jWYSIWYG | 0.5 | 0.97 | jWYSIWYG 0.9 supported. Not recommended. End of life 2011. |
| markItUp | 1.1.5 | 1.1.14 | markItUp 1.1 supported. Not recommended. End of life 2018. |
| nicEdit | 0.9 | 0.9 | nicEditor supported. Not recommended. End of life 2015. |
| TinyMCE | 3.3.9.2 | 4.9.11 | TinyMCE 7 unsupported. TinyMCE 6 unsupported. End of life October 2024. [Issue #3413569] TinyMCE 5 unsupported. End of life April 2023. TinyMCE 4 supported. Not recommended. End of life December 2020. |
| Whizzywig | 55 | 63 | Whizzywig supported. Not recommended. End of life May 2011. |
| WYMeditor | 0.5 | 1.1.1 | WYMeditor supported. Not recommended. End of life 2015. |
Editor Information
CKeditor
The successor to FCKeditor, distributed under the same licenses.
Drupal 8+ includes the Editor module (inspired by WYSIWYG) and ships with CKEditor out of the box.
* Note if you are using CKEditor make sure you install the full package as not all plugins work with the standard package. If you prefer to stick to the latest release that has been tested with Wysiwyg, there is a problem that the CKEditor site does not (as far as I can see) offer the full package of an older release. You could try this pattern http://download.cksource.com/CKEditor/CKEditor/CKEditor%20VERSION/ckeditor_VERSION_full.zip (VERSION= e.g. 4.6.1) or the CKEditor GitHub project release page for an archive of older full releases.
FCKeditor
CKEditor's predecessor. Distributed under the GPL, LGPL and MPL open source licenses. No longer developed.
jWYSIWYG
GPL 2 license. This plugin is an inline content editor to allow editing rich HTML content on the fly. It's an alternative to WYMeditor with much less features. With a small file size less than 26Kb total and only 18Kb of code and 7Kb packed, the main concept is to keep it simple, not all users need font coloring or create tables, just the basic. No longer developed.
markItUp
markItUp is a jQuery plugin and the Packed naked engine is only 6.5KB. Licence: MIT/GPL. Supported browsers: IE7, Safari 3.1, Firefox 2, Firefox 3. IE6 and Opera 9+ as-is. No longer developed.
NicEdit
MIT License. No longer developed.
TinyMCE
LGPL. Their file and image management addons cost money. Use Wysiwyg image uploader or IMCE. TinyMCE competes with CKEditor for the most buttons on the toolbar. No longer developed.
WYMeditor
For the XML puritans. No fonts or anything. You define the CSS then your editors use your classes. Development moved to Github, the old website appears to no longer be maintained. No longer developed.
Image Handling
Media
The Media module has a WYSIWYG submodule which offers a plugin for adding a "Media" button and embedding documents/photos into the editor from any of its media sources (upload, library, web link, etc). Currently only known to support CKEditor and TinyMCE.
IMCE Wysiwyg bridge
IMCE can connect to Wysiwyg through IMCE Wysiwyg bridge. IMCE Wysiwyg bridge works only with TinyMCE, FCKeditor, and CKeditor.
Insert
Insert works by leveraging an Image Field. It also offers Image Styles integration.
Help improve this page
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion