Plate vs Lexical: components included or nothing included
Plate ships copy-in components on top of Slate; Lexical ships an editor state model and no UI. We measured Plate at 150.8 kB gzip against Lexical's 104.9 kB.
TL;DR
- Plate gives you a plugin framework plus components you copy into your repository; Lexical gives you an editor state model and expects the rest from you.
- Measured: Plate 150.8 kB gzip and 13 lines to a working editor, Lexical 104.9 kB and 25 lines.
- Both are React-only in practice, so this comparison is decided by how much of the editor you intend to build and how much upgrade churn you can absorb.
Plate vs Lexical at a glance
Generated from the same dataset as the main table, so this cannot drift out of sync with the rest of the site.
| Fact | Plate | Lexical |
|---|---|---|
| Type | library | library |
| Editor kind | Rich-text editor, Document editor | Rich-text editor |
| Licence | MIT | MIT |
| First release | 2021-07 | 2022-01 |
| Frameworks | React | Any (framework-agnostic) |
| SSR support | partial | partial |
| Bundle (min+gzip) | 150.8 kB gzip | 104.9 kB gzip |
| Price from | Free (open source) | Free (open source) |
| Drag & drop canvas | Partial | Partial |
| Responsive breakpoints | No | No |
| Visual style manager | No | No |
| Custom components | Yes | Yes |
| Data binding | No | No |
| E-commerce blocks | No | No |
| Email HTML export | No | No |
| AI generation | Yes | No |
| Editor i18n | Partial | Partial |
| White label | Yes | Yes |
| Self-hosted | Yes | Yes |
| Real-time collaboration | Via plugin | Via plugin |
| HTML export | Yes | Yes |
| JSON output | Yes | Yes |
| Benchmark | 150.8 kB · 209 ms to editor | 104.9 kB · 159 ms to editor |
| Last verified | 2026-08-19 | 2026-08-20 |
Best fit by requirement
Generated from the dataset: only requirements where both facts are verified and they differ. Neither product is better overall — it depends on which of these you actually need.
- If you need Vue support, Lexical works in Vue as a framework-agnostic engine; Plate does not.
- If you need Angular support, Lexical works in Angular as a framework-agnostic engine; Plate does not.
- If you need AI features, Plate offers AI generation; Lexical does not.
- If you need a smaller JavaScript bundle, Lexical measured 104.9 kB gzip against 150.8 kB for Plate.
Plate vs Lexical: analysis
What each one decides for you
Plate decides a great deal: which plugins exist, what a toolbar looks like, how block menus behave. You can change all of it, because the components live in your repository, but you begin with opinions.
Lexical decides almost nothing beyond the state model. Every visible element is yours, and the framework's position is that this is correct.
Our benchmark measures the consequence: thirteen lines against twenty-five, for editors that render the same thing.
Where Plate fits better
A running start. Components, plugins and patterns for the features document editors need — mentions, tables, slash commands, drag handles.
Design-system fit. If you use shadcn/ui, the editor matches your product immediately.
AI plugins in the maintained set, rather than as a service or a project.
A larger catalogue of ready node types, which shortens the distance to a product rather than a prototype.
Where Lexical fits better
Nearly a third less weight, at 104.9 kB against 150.8 kB before either adds plugins.
A cleaner state model. Immutable and transactional, where Slate's normalisation is subtler and harder to predict at the edges.
Meta's production scale behind the core.
Fewer assumptions to unwind when your editing surface is not a conventional document.
No design-system coupling. Plate's advantage becomes a constraint if you are not on Tailwind and shadcn/ui.
The upgrade question
Both projects move. Plate publishes major versions frequently; Lexical is pre-1.0 and permits API changes by convention.
The practical difference is what breaks. Plate's churn tends to touch components you copied, which is your code and therefore your merge. Lexical's touches framework APIs you called, which is a smaller surface but a harder fix.
Whichever you choose, treat editor upgrades as scheduled work rather than as an occasional inconvenience. Teams that do not end up pinned to an old version with a growing list of unbackported fixes.
Migration between them
Both build structured documents, so content converts with a serialiser you write. Neither's plugin API resembles the other's, so the editor layer is a rewrite.
Realistically this is a decision to make once. Pick on the basis of how much editor you intend to own, not on which API reads better in a tutorial.
Decision checklist
- Are we on Tailwind and shadcn/ui? That alone justifies Plate for many teams.
- How unusual is our editing surface? Unusual favours Lexical.
- What is our JavaScript budget? The gap is 45.9 kB before plugins.
- Who owns editor upgrades, and when?
- Do we need collaboration? Both can; neither hands it to you free.
The number that matters
45.9 kB — the gzip gap in our bundle benchmark, and roughly the weight of the components Plate gives you. That is a fair way to read this comparison: you are paying in kilobytes for the UI you would otherwise build, and the question is whether you would have built the same thing.
Frequently asked questions
- Which is lighter?
- Lexical, at 104.9 kB gzip against Plate's 150.8 kB, both measured with React external and before either project's additional plugins.
- Which ships more UI?
- Plate, decisively — its shadcn/ui components are copied into your codebase, so you start from a toolbar rather than from nothing.
- Which has the more stable API?
- Neither is settled: Plate ships frequent major versions and Lexical is pre-1.0. Plate's churn is more visible because the version numbers are large; Lexical's is implied by the 0.x line.
Alternatives to consider
Related comparisons and categories
Facts about Plate were verified on 2026-08-19 and facts about Lexical on 2026-08-20. Full source lists are on the Plate review and the Lexical review.