> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumen.bjanczak.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lumen Editor vs Quill vs TinyMCE: Which Should You Use

> Compare Lumen Editor, Quill, and TinyMCE on bundle size, dependencies, security, sanitization, framework support, and licensing to pick the right editor.

Choosing a rich text editor involves weighing bundle size, runtime dependencies, security model, and licensing. Lumen Editor, Quill, and TinyMCE are three of the most commonly evaluated options — each with a different philosophy and trade-off profile. This page breaks down the key differences so you can make an informed decision for your project.

## Feature Comparison

The table below compares all three editors across the dimensions that matter most in production applications.

|                       | Lumen                                   | Quill                       | TinyMCE                        |
| --------------------- | --------------------------------------- | --------------------------- | ------------------------------ |
| **Source size**       | \~12 KB                                 | \~200 KB min                | \~500 KB+ min                  |
| **Runtime deps**      | 0                                       | 0                           | several                        |
| **Architecture**      | `contenteditable` + allowlist sanitizer | Custom Delta document model | Plugin-rich commercial editor  |
| **Sanitization**      | Built-in, DOM-based, strict             | Partial (Delta format)      | Via plugins                    |
| **XSS protection**    | Built-in, default-on                    | Partial                     | Optional (plugin)              |
| **Framework support** | Any / none                              | Any / none                  | React / Vue / Angular adapters |
| **Build step**        | None required                           | None required               | None required                  |
| **License**           | MIT                                     | BSD-3                       | GPL / commercial               |

## When to Choose Lumen Editor

Lumen Editor is the right choice when your priorities align with the following criteria:

* **Size-sensitive environments** — At \~12 KB with zero runtime dependencies, Lumen adds virtually no weight to your bundle. It is ideal for performance-critical pages, embedded widgets, or projects with strict payload budgets.
* **Security-first requirements** — Lumen's built-in, DOM-based sanitizer and default-on XSS protection mean you get a hardened editor out of the box, without configuring extra plugins.
* **Zero-dependency constraint** — If your project enforces no third-party runtime dependencies, or you want to minimise your supply-chain attack surface, Lumen ships with none.
* **Framework-agnostic codebases** — Lumen works with any framework — or no framework at all. Whether you use React, Vue, Svelte, or plain JavaScript, you can drop it in without an adapter layer.

<Note>
  Lumen Editor is published under the **MIT License**, which permits use in both open-source and commercial projects with no royalty or attribution requirements beyond preserving the license notice.
</Note>

## When to Consider Alternatives

Lumen is deliberately focused and lightweight, so some specialised use cases are better served by other editors.

<CardGroup cols={2}>
  <Card title="Consider Quill" icon="pen-to-square">
    Quill's Delta document model is purpose-built for **operational-transformation-based collaboration**. If you need real-time multi-user editing, conflict resolution, or a rich programmatic document API, Quill's architecture gives you primitives that Lumen's `contenteditable` model does not expose.
  </Card>

  <Card title="Consider TinyMCE" icon="building">
    TinyMCE suits **enterprise teams** that need an extensive plugin ecosystem, accessibility compliance certifications, commercial support contracts, and integrations with CMS platforms. Its larger footprint comes with a far broader out-of-the-box feature set and a dedicated support organisation.
  </Card>
</CardGroup>