A rich text editor for your CMS
A CMS lives or dies by its body field. Editors paste from Word, drop in images, and expect the published page to look like what they typed. RichTextEditor is the editing field: it produces clean HTML your CMS stores and renders, with uploads going to storage you control.
Where it is used
Articles and blog posts
Headings, lists, tables, images and embedded video, written in a familiar toolbar layout.
Landing and product pages
Start from one of your own content templates, so pages share a structure without a developer for each one.
Admin back offices
The same editor on a textarea in a custom admin, in plain JavaScript, React, Vue, Angular, Svelte, ASP.NET, Blazor or PHP.
Headless content
Convert the content to JSON or Markdown when the front end is not rendering stored HTML.
Features that matter here
All of these are in every license. Each card links to the documentation, so you can check how it works before you commit.
Clean paste from Word
Pasting keeps lists, tables and images and removes Office markup, so stored HTML stays readable.
Paste from Word demo →Images stored as files
Uploads go to your own handler and folder. The guide covers turning base64 embedding off and refusing it on the server.
Store images as files →Your own templates
Writers start a document from a searchable list of templates that you supply.
Templates demo →HTML, JSON and Markdown
Read the content as HTML, or convert it to structured JSON or Markdown, render it and validate it.
Structured content →Accessibility checker
A built-in checker lists problems such as missing alt text before the page is published, with one-click repairs for some rules.
Accessibility checker rules →Load only what you use
The plugin set can be reduced to the features your CMS enables, with measured sizes for each preset.
Bundle size and plugins →What the editor does not do for you
We would rather you find the limits here than during an audit.
- This is the editing field, not a CMS. Content types, workflow, permissions, publishing and search are your application’s job.
- Sanitize on the server. The editor filters content in the browser, but a request can skip the browser, so your CMS must clean the HTML it stores.
- The published page is styled by your site’s CSS. Load the same styles into the editor if writers should see the final look while they type.
- There is no ready-made plugin for a specific CMS product described here. You connect the editor to a field in your own code.
Evaluation checklist
Paste three real Word documents and inspect the HTML that is stored.
Turn base64 images off and confirm uploads land in your storage.
Run a stored-XSS test against your save endpoint, not only the editor.
Load your site’s content CSS into the editor and compare with the published page.
For a full evaluation plan, see the evaluation checklist.
Customer stories
We only publish customer stories that the customer has agreed to, and none from this sector is published yet. If you use RichTextEditor in cms and publishing, tell us how. We will write it up with you and publish it only after you approve it.
Related
How to store rich text · Stored XSS in rich text editors · Pricing · Other sectors: Education, Healthcare, Government, Legal
Try it with your own documents
Perpetual licenses from $129, one-time. Every feature in every license.