Last updated February 10, 2014. Created on January 10, 2008.
Edited by batigolix, technicalknockout, Sutharsan, LeeHunter. Log in to edit this page.

Note: All editor integration modules are going to be replaced by Wysiwyg API (but some take a bit more time to be converted). Wysiwyg API provides the integration with Drupal and contributed modules for most of the editors listed below. Please understand this page as a comparison of the actual editors and their generated markup/content. I.e.: Most of the module installation issues are obsolete with Wysiwyg API.

Note for future updates: Instead of the Drupal module version that was tested, this document should contain the editor library version that was tested. All editor libraries are improved over time and the Drupal module does not really matter (especially when using Wysiwyg API). has over 100 modules in the "filters and editors" category. Around a dozen of these are editors which modify textareas for easy formatting of posts.

Drupal core does not currently have an editor, and this is often a feature request in the forums. This chart is designed to help you choose which editor would best fit your needs.

Jan 6, 2012



Dependencies File size


Built in
BBCode Formatting Bar version 5.x-1.0 4.7, 5 No Valid Fails BBCode module Unchecked No/No
BUEditor version 7.x-1.3 6, 7 No Valid Fails None 102 KB No/No
CKeditor version 7.x-1.13 6, 7 ? ? ? CKeditor external library ? ?
FCKeditor version 6.x-2.2 5, 6 Yes Valid Passes FCKeditor external library 4.320 KB Yes/Yes
HTMLArea version 5.x-2.1 abandoned No Untested Fails HTMLArea external library Unchecked Yes/No
HTMLBox version 6.x-1.0 5, 6 No Untested Fails None Unchecked No/No
nicEdit version 5.x-1.x-dev Abandoned Yes Failed Passes nicEdit external library Unchecked No/No
openWYSIWYG 6.x-1.0-rc1 5, 6 Yes Untested Untested none 466 KB Yes/Yes
QuickTags version 5.x-3.1-dev 4.7, 5 No Failed Untested None Unchecked No/No
TinyMCE version 6.x-1.1-dev Abandoned Yes Failed Fails TinyMCE external library 1.910 KB Yes / Commercial license
widgEditor version 6.x-1.0 5, 6 No Valid Fails None Unchecked No/No
Whizzywig version 6.x-2.3 5, 6 Yes Valid Passes No 150 KB Yes/Yes
WYMEditor version 5.x-2.0 Abandoned Yes Valid Fails None Unchecked Yes/No
XStandard version 6.x-1.1 5, 6 No Valid Fails XStandard external library 2.200 KB Yes/No
YUI Editor version 6.x-2.33 5, 6 Yes Failed Fails YUI Module Unchecked No/No

BBCode Formatting Bar
Upon installation I tried to create a new page and voilà! There were several buttons above the box, just begging to be tested. There isn't much to this editor. If you have installed the BBCode module, the BBCode inserted by this editor will be produce valid HTML markup. It isn't pretty, and there are no keyboard shortcuts, but it definitely gets the job done. You must be careful of one thing, however. The input format must be set to BBCode (this can be enabled via the BBCode Module) or your text will not display correctly.

This isn't really a WYSIWYG editor. It provides buttons which will automatically insert the HTML into Drupal's default plain text box. Although this does make it easier to create the posts, it is not quite as user friendly as a true WYSIWYG editor. To offset this however, it gives you a quick-preview button. This is a far faster way to preview text than Drupal's preview, and is an acceptable workaround for the lack of seeing what you get as you edit it.

This wasn't the most friendly to use. When installing it like usual, it did not automatically fill in the plain text boxes with the editor. Going into the admin page, I discovered that I had to download and install FCKEditor separately, then it could be used. (Of course, all this was detailed in the readme, but very few people actually read those) Once it was installed, it worked flawlessly - by far one of my favorite editors available. FCKeditor is particularly easy to configure offering administrators the necessary field name and path below every field where it is used. These names can easily be copied to the module's setting's page to change whether the editor appears in that field.

Unfortunately, this editor also required going to a 3rd party site to download the editor. Once I had installed it, the was no visible way to make it work. I went through their readme and install.txt, but neither of them seemed to work. I would definitely not recommend this editor to anyone.
No screenshot available

Based on HtmlBox original code by Remiya Solutions released under MIT license. It's only based on, the code is changed quite a bit. This module fails the coder.module test on a minor error relating to a missing space in one string.

As the only editor which passed the coder.module test, I had high hopes for this editor. Initially they were filled. This editor did not require going to a 3rd party site to download the editor. As soon as the module was enabled, all the plain text boxes were replaced with the WYSIWYG interface. My biggest problem with this was that, unlike FCKEditor, there were no keyboard shortcuts available within the editor.

OpenWYSIWYG installation very easy because this module included all required scripts/libraries. Built in File Browser: file upload, file delete, file resize, file rename, folder create. User define folder format: can use [uid], [username] and [domainname]. Uses Drupal permissions: makes module configuration very easy, i.e: you can allowed/disallowed certain group for File Delete. Support Full Toolbar Icons and Customize Toolbar Icons. Support table, image, clean MS Word format. Font List supports font preview/sample. When upload image file this module will do image resizing before check the image size. So, you don't need to reduce image size before uploading! Supports username as variable; easy to remember: files/andy rather than files/u657.

I had no luck with this editor. Once I enabled the module I went to create a new page. No such luck. Drupal spit out an error inside the module. There was no way I could find around this.
No screenshot available

Like most of the others, TinyMCE required going to their site to get the editor. After doing this, I had to setup a profile to allow myself to use the editor. Going with all the defaults produces an error until you give roles the 'access tinymce' permission. Although other editors had required that users have a certain permission, they had all given me, the admin, permission by default. Even after giving myself permission, it took awhile to notice that TinyMCE (by default at least) doesn't automatically replace the text boxes. It puts a small link underneath it allowing you to enable it. There may be a setting to change this, but by default I would find it much easier to simply replace the text box as expected.

Once the module was installed, there was no need to go to a 3rd party site for the editor. However, I had little hope for the module when I saw it's admin summary. It was left as the default example message for when people make their own module. Going into the settings, I noticed it was definitely easy to configure; the only option was to make it the default editor. I did this, and went to create a new story. In sticking with their obvious 'less is more' strategy, the editor provided for only the most basic of editing. Overall however, I enjoyed the experience with this editor. As long as you are not planning on using the editor for anything complicated at all, I would highly recommend this editor.

I'll never understand why all these modules don't just include a version of the editorWhizzywig now supports Drupal 5, 6 and next version of Drupal. After installing both this and the extension to allow for XHTML, I tried to create a story with the editor. This editor has a slightly different interface than the rest. While most editors use some relatively standard icons to indicate what the buttons will do, Whizzywig uses only text Whizzywig supports both text or icon mode. I have no problem with text, but this makes it so that the toolbars take up more room in the editor.

There are some icons available, but this is not made immediately obvious. Additionally, there <is no way to tell when the different text styles (bold, italic, etc) are activated Whizzywig a WYSIWYG editor, so just SEE the styles on your screen. There was really only one other problem I had with the editor. Once I created a link, <it was nearly impossible to tell it that I only wanted the link to be on one word, not the whole paragraph many bugs fixed on new version.

From author:

This is the FASTEST and SMALLEST but FEATURE RICH editor for Drupal. Very very fast and cross browser support. Also Whizzywig has built in Image Browser and File Manager. This is an independent module, so you don't worry about bug/feature from another modules!

I think people are finally getting the installation right. Yet again, this module did not make me go to their site to get the latest version of the editor. Once I created a new profile for the editor using all the default settings, I headed off to create another story. The editor was beautiful to look at. There was a toolbar on top for the basic text formatting, and the different headings were all in a sidebar. Then I tried to use it. It would not learn that I didn't want to close my tags at the end of every paragraph. It was nearly unusable, which for me at least, was a disappointment. It looked so promising.

Ouch. This editor goes back to the evils of 3rd party sites. To make this pain even worse, it gives you no hint that you need to do so in the administration page. The only time you realize this is when trying to make a story. Even in their message, it doesn't give you a link to the website. (to be fair, all this is detailed in the readme, but as I said with FCKEditor, very few people actually bother to read them) Just in case all this wasn't hurting you enough, their download site requires you to give them your email address. For all this trouble, it had better be one heck of an editor. Once I downloaded it, it comes in an installer. That's a bit odd, but I ran it anyway. It turns out, this is an editor plugin for your computer. Even though it does not take replace the text box by default, XStandard made it very easy to figure out which field IDs needed to be added to use the editor. After adding the needed fields, I fired up the story editor again. After using the editor, I was still left with a bad taste in my mouth. There was nothing particularly special about the editor, certainly nothing worth the pain of installing it.

YUI Editor
After the pain of XStandard, I was hoping YUI Editor would turn out to be the best editor I'd ever seen. The editor had a beautiful installation. Once I enabled the editor and its dependency, I never had to touch the administration page. Creating a new story was a pleasure. The editor looked, and worked, wonderfully. Everything behaved as expected with one exception. There were no keyboard shortcuts available. This addition would make the YUI editor surpass every editor out there.

* This test was done by creating a post in each editor with the text "This post was made for Drupal using the awesome editor EditorName." and running the resulting page through the HTML Validator

Looking for support? Visit the forums, or join #drupal-support in IRC.


Walt Esquivel’s picture

EXCELLENT comparison of editors!

1. I Googled and found a couple of other surveys, although they're not very current.
Evaluation of WYSIWYG editors (February 2007)
Evaluation of WYSIWYG editors - FULL test results (February 2007)
WYSIWYG Text Editors Reviewed (February 2006)

2. I'd like to let folks know about WYSIWYG over at

3. Here's a helpful poll: Which editor (if any) do you use for your Drupal site(s).

Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing

Arjean’s picture

Even though it is a nice review, and seems to be updated (jan 2009)
I'm not sure how the test has been done.
When simple testing the "test line" in TinyMCE, the gives a nice -Passed.
When I used FCKEditor I stumbled on the image editor. It uses vspace and hspace which are depreciated.
TinyMCE handles this correctly and would pass a validator.
Then again, that goes beyond this simple test.
This test is more about Drupal compatibility, and for that it clearly points out all the main issues.

Chairman13’s picture

This is SO SO SO useful! Thank you so very much for putting this together!

I was wondering two things. :)

1. Would it be possible to update it and include CKeditor, FCKeditors newest release?

2. there any way you would consider going into images and any requirements (modules) to allow for images to work? ...and just how it works in general on a usability level with inputting images?

3. Spellcheck compatibility. Does it have it? Does it require a server side piece?

Thanks so much for your consideration. :)


David Latapie’s picture

This one's easy:

  • Do you want a pseudo-WYSIWYG editor like in Wikipedia, an editor where you can enter your own tags or scripts, or an editor where you don't have to install something else later? Then go for BUEditor.module, which is a one-step process.
  • Do you want a real WYSIWYG editor and don't like CKEditor? Then go for WYSIWIG.module. Notice you will then have to select which editor to install (thus this is a two-step process).
  • Do you want CKEditor (not FCKEditor)? Now you can either choose WYSIWIG.module or CKEditor.module. CKEditor.module is supposed to be a tad more powerful and but the latest version is a bit bigger than WYSIWYG (once uncompressed). This is a two-step process, like WYSIWIG.module, so no difference here.

That's all. No editor work with Drupal 7 (and let's face it, with D7 being at RC3 stage, it won't be future for long, so forget about Drupal 6).

My personal favorite is WYSIWYG.module. As for the editor itself, I decided to use CKEditor after reading the excellent Review of Drupal rich text editors.

Thus: WYSIWYG.module + CKEditor (lowest footprint + best accessibility, respectively). Or BUEditor for those who prefer no-surprise pseudo-HTML.

loyukfai’s picture

May I ask what the WYSIWYG.module actually does...?

I've just dived into this brave new world of WYSIWYG in Drupal after installing the CKEditor module, and am wondering if I should install the WYSIWYG.module as well.

BTW, it seems that I need to press enter twice to have proper spacing between paragraphs. Is it something related to the theme I use (box_grey/cleanslate)...?


P.S. There's a more updated evaluation here:

loyukfai’s picture

OK I got it... Both CKEditor (the Drupal module) and WYSIWYG (the Drupal module) enable one to use CKEditor itself on Drupal.

Either one of the modules will work, and of course there are debates on which is better.

And CKEditor's output doesn't seem to work well with the built-in filters of Drupal 6, that's why the spacing became a mess.


Albana_12’s picture

Hello, i have a problem while using this editor, i am using the accordion which comes together with it, but its causing me problems, for example, almost the last two accordion tabs won't open and if it happens for them to open, they show the wrong content and in the wrong place.

What should i do?

BarisW’s picture

If you have any questions regarding the use of one of the editors, please use the issue queue of that specific editor or use the forum. This is a documentation page, not a support forum.

Baris Wanschers (@BarisW)
Drupal specialist

dzigner’s picture

I installed the OpenWYSIWYG for my local drupal site, and it says, OpenWYSIWYG does not support your browser(Chrome). It works in Firefox though. I want to know which one of the above supports Chrome.