14-day Cloud trial
Start today. For free.

One editor. 50+ features. Zero constraints. After your trial, retain the advanced features.

Try Professional Plan for FREE
PricingContact Us
Log InGet Started Free

Developer Insights

Looking for a rich text editor? See the future in 2023 Rich Text Editor Developer Survey Report

Published Nov 8th, 2023

 9 min read 

Our 2023 Rich Text Editor Developer Survey results gave glimpses of the future: users migrating, new technologies being employed, and an AI takeover is looming. But then again, there's also clear indications that some RTEs are performing better than others and are delivering on their role, really well.

Di Mace

Director, Content and Communications at Tiny


Rich text editors are crucial components in modern, agile tech stacks. They offer almost limitless opportunities for reuse when deployed via APIs and allow businesses to scale faster, with less drain on development resources. But, how those rich text editors perform and how much value they add to an organization's workflow, content management setup, data capture processes and productivity, affects the level of satisfaction felt by its users.

The results show there's two clear leaders – TinyMCE and CKEditor – with a commanding market share. More than half (58%) of the developers surveyed most often used either editor. There’s also clear indications that developers envisage a future for rich text editors that’s heavily impacted by the various forms of Artificial Intelligence (AI) technology.

A must-read section covers the eternal debate of Buy vs Building a key component, and the crucial contribution buying a rich text editor can make to the agility, velocity and productivity of your company.

Read on to glimpse the future of rich text editing, in the 2023 State of Rich Text Editor Developer Survey results.

What paradigm shifts do you see coming? What big game-changing features do you anticipate in the future?

This open text question encouraged participants to envision the future of the rich text editing industry and predict new features, based on the emerging trends and changing needs that they’re observing today.

 The shift that’s expected to most heavily impact rich text editors is the integration of Artificial Intelligence (AI).

  Widespread speculation on how an AI integration could manifest – Generative AI, Machine Learning, Natural Language Processing, and other automation techniques – to assist in in-editor content creation and integration.

Other themes mentioned include automation, collaboration, and voice-to-text technology. These themes are summarized below.

Quote themes:

AI integration: AI will play a crucial role in streamlining content creation and integration.

Automation: Automation will significantly improve efficiency in rich text editors.

Collaboration: Collaborative tools will enhance communication and teamwork.

Voice-to-text: Voice-to-text technology will simplify data entry processes.

What features do you expect to become standard in rich text editors within the next two years?

Another open text question, where participants considered upcoming advancements in technology itself, as well as the rich text editor industry. The top result was once again AI, indicating significant progress is expected across the industry and the integration of AI into general everyday conversation.

Similar themes emerge as the previous question (paradigm shifts), including voice recognition and transcription, collaboration tools, and enhanced integration with other software. However, new themes also emerge, such as clean copy/pasting, industry-wide adoption of top-notch features, optimization for mobile usage, and multi-language support.

Robust AI integration (generative, predictive, spelling/ grammar check, autoformatting, etc.)

Native integration with Artificial Intelligence like ChatGPT and image generators.

AI functions like: generate articles based on a few pasted words or topics.

AI generated document templates. Custom built to purpose document templates created by AI.

AI, predictive writing, chat-bot etc.

Integrated Artificial Intelligence capabilities, providing suggestions for grammar, style, and formatting.

Voice recognition/speech-to-text

AI collaborative writing, speech-to-text.

Dictation, voice functions.

Integrated AI-powered voice dictation and transcription tools.

Text-to-speech and speech-to-text.

Various modes of editing and speech recognition.

Voice recognition.

Seamless copy/pasting regardless of input source

Power’ copy paste function.

A way to add images, tables, and other formatting options without having to copy-and-paste them into the editor.

Accessibility check.

Copy/pasting styles keeping, exporting easily for PDF or similar formats.

Drag and drop images, table tools, compatibility with Office.

Improved formatting retention or stripping when copy/pasting.

Collaboration functionality

Advanced collaboration tools, such as real-time co-editing and commenting.

Collaboration and AI.

I think real-time collaboration may become the standard.

Less code, easier to customize, real time collab.

Revision history and collaboration.

Spell check, collaboration, mentions, AI integration hooks.

Industry-wide adoption of best-in-class features from MS Word and Google Docs

Catch up with MS Word/Google Doc.

Collaborative features, commenting, looking at past versions, auto correct, text suggestions.

Cross compatibility with editors like Google Docs and Microsoft Word with change tracking.

Google Docs sets the bar. The world is going to inch closer and closer to being able to put the Google Docs experience anywhere a rich text editor is needed.

Integrating with Google Docs directly.

Mobile optimization

Advanced support for mobile and tablet devices, including touch screen gestures and handwriting recognition.

I think mobile editing will be the standard within the next two years.

Mobile integration, blogging features, integration of media.

Mobile optimization.

Strengthen the mobile terminal office.

Multi-language support

I hope that in the next two years, the standard of rich text editors includes support for more formats, such as Markdown, LaTex, and HTML, CSS, etc.; support for more plug-ins and custom functions, such as support for text search, support for multi-document synchronization editing, support version control, and support text auto-completion, etc.; support AI-related functions, such as automatic code completion, grammar checking, etc.; and better performance, can process large amounts of data faster, and can support more languages.

Language conversion.

Multiple languages, robust search and replace capabilities.

READ THE FULL SURVEY REPORT

View Report

Which rich text editor do you use most often or centrally in your projects?

TinyMCE and CKEditor, hold a commanding market share between them, with more than half (58%) of the participants using them most often.

  TinyMCE is the most popularly used editor, with 32% of participants centrally using it in their development projects.

 CKEditor is used by 26% of participants.

Custom-built editors: Coming in third place, custom-built editors have a 12% share. This indicates that there is a significant group of developers who prefer to create their own editors, tailored to their specific needs.

Less popular players: The remainder of the market is spread across various other editors that are not as widely used as TinyMCE, CKEditor, or custom-built editors. Although these players may have a smaller market share, it's important to understand that they cater to specific user preferences and needs, and help to deliver a diverse range of choices to users.

Rich Text Editor Used Most Often

What rich text editors have you ever used, or have experience in using?

It seems developers tend to experiment and try out different versions and editors before deciding on a primary rich text editor provider. Although some individuals may try or prefer using open-source editors, the majority ultimately choose one of the two major providers that offer a combination of open-source and premium, paid offerings.

  TinyMCE and CKEditor offer a more comprehensive, fully-featured and extensively supported product that satisfies the needs of most users.

Rich Text Editors Tried or Used

What are the main reasons you chose/used a particular editor for your most recent project?

As an open text question, this allowed participants to share the underlying drivers behind their choice of rich text editor. The results clustered into eight thematic groupings:

  • Easy to use/user friendly
  • Easy to integrate and implement
  • Easy to customize
  • Powerful and highly customizable
  • Many features, richness of features, plug-ins, rich API
  • Reliable
  • Stability
  • Collaboration features

READ THE FULL SURVEY REPORT

View Report

What drives your choice to buy and use a ready-made rich text editor, as opposed to building your own?

Unsurprisingly, the decision between buy or build is heavily influenced by cost considerations. Cost is the determining factor both in the short-term – with development time and resource costs – as well as in the long-term, encompassing ongoing development and maintenance. Notably, these cost drivers have experienced a significant increase in 2023, which may reflect the economic volatility in the previous year.

  In addition to cost, the speed of development and ease of implementation remain crucial factors that drive the decision to purchase a ready-made editor.

The decision to buy is further validated by the knowledge that it takes US$15–28M+ and 115–220 person-years to build the core editor of TinyMCE or CKEditor (excl. Maintenance and extensibility work).


Note: This question allows people to select multiple options.

Drivers to Buy a Ready-made Rich Text Editor

The Great Debate: Buy vs Build a Rich Text Editor

Agile businesses are combining buying, subscribing, or renting, with building, to iteratively reshape and assemble a flexible software stack.

READ THE WHITE PAPER

What drives your choice to build your own rich text editor (RTE) as opposed to using a ready-made editor?

Those who choose to develop their own rich text editor in-house, possess the internal knowledge and resources required to pursue this approach and believe that utilizing these resources is a preferable alternative to investing funds in a solution that may not fully meet their specific needs.

  The key reasons are increased control and flexibility over how the editor interacts with their applications.

This highlights the opportunity for more extensive customization options, enhanced control, and use cases that are best served by a headless rich text editor.


Note: This question allows people to select multiple options.

READ THE FULL SURVEY REPORT

View Report

Drivers to Build Your Own Rich Text Editor

What’s your preferred deployment option for your rich text editor?

Deployment options are an important gauge of the speed of transformation being undertaken across the digital landscape. Despite the continuing race to achieve digital speeds required for large scale digital transformations, ‘Self-hosted’ remains the preferred option (40%). Cloud deployment (38%) continues to slowly grow, while just under 20% seek a hybrid option.

Preferred Deployment

In the next two years, is it likely that you’ll change the way you deploy your rich text editor?

This question delved into the intention to change rich text editors and is indicative of the fluidity of the market. The results reveal that half the users are considering switching editors, indicating:

  Users aren’t completely satisfied and are searching for a better option, with some expressing the need for additional features.

  The rapid pace of innovation across the technology sector is driving organizations to constantly look for the next ‘breakthrough’ in performance, features, or lower cost.

  Notably, in 2023, more users are contemplating switching rich text editors as compared to previous years. This change is likely being driven by digital transformation

In technology, a two-year window is a long time. Therefore, because it’s widely accepted that significant changes are a given, switching essential tech stack components, like a rich text editor, is a given within that time frame.

READ THE FULL SURVEY REPORT

View Report

Likelihood of Changing Deployment Within 2 Years

Frequently asked questions

How can I read the full report?

Did only TinyMCE users take the survey?

No, it was open to all software professionals across various industries, roles, and geographic locations

How can I ask questions or give feedback

Please direct questions or comments about the survey to team@tiny.cloud

I’d like to participate in the next survey. Can I sign up for alerts?

The best way to receive news about the Rich Text Editor Survey is to sign up for our monthly newsletter

author

Di Mace

Director, Content and Communications

Messaging strategist and copywriter whose passion lies in working with brands like Tiny, that have deep-seated values and embrace the power of their story. She gets a kick out of solving problems, loves learning new things and making stuff, every day. When she’s not thinking through clever copy lines or clarifying value propositions, she’s knitting amazing socks for everyone she knows.

Related Articles

  • Developer InsightsJun 3rd, 2024

    TinyMCE Sponsors and Presents at Frontend Nation Online Event

Join 100,000+ developers who get regular tips & updates from the Tiny team.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Tiny logo

Stay Connected

SOC2 compliance badge

Products

TinyMCEDriveMoxieManager
© Copyright 2024 Tiny Technologies Inc.

TinyMCE® and Tiny® are registered trademarks of Tiny Technologies, Inc.