Framework
ueberdosis/tiptap avatar
ueberdosis/tiptap

Tiptap and the paid layer sitting on top of an MIT editor

GitHub describes it as The headless rich text editor framework for web artisans.. The repository metadata lists TypeScript as its primary language. The metadata lists the MIT license. This article stays within the project description and details documented in the GitHub repository README.

39,051 stars3,206 forksTypeScriptMIT

At a glance

What is it?
Tiptap is a headless, framework-agnostic rich text editor built on ProseMirror, published under MIT as a monorepo of packages, while collaboration, comments, versioning, conversion and AI sit in a subscription tier. This is what the split means for an evaluator.
Who is it for?
Tiptap fits a team that wants to own its own editor interface and can live inside the ProseMirror model, and it fits anyone willing to run Hocuspocus for collaboration. It may need more integration work if you want a ready-made UI.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • ueberdosis/tiptap39,051 ★ · +1,049
Star history
Repository2026-08-132026-11-15
ueberdosis/tiptap38k39.1k

1,049 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Headless means the interface is your project, not theirs

The editor ships without a user interface, and the README is direct about why: it means full design freedom, and no need for class overrides or code hacks. The same passage says the editor is designed to work across frontend frameworks, naming Vue, React, and plain JavaScript as equally supported, which is the framework-agnostic claim in its plainest form.

So adopting Tiptap means adopting two projects: the editor engine, and the toolbar, menus, and empty states you have to build on top of it. The proof is in what the project publishes instead of a component library. There is a React notion-like block editor template at templates.tiptap.dev, a basic editor CodeSandbox, a collaboration-ready CodeSandbox, and a root serve script that builds the demos and exposes them over http-server on port 3000. The demos are the reference implementation. The cost of headless is simply that the visible half of the work does not arrive with the package.

The paid tier is named in the README, feature by feature

The licensing split is not subtle. LICENSE.md is the MIT License, and the root package.json is private, which is normal for a monorepo that publishes its packages rather than itself. Above that sit the Pro Extensions, described as additional features that integrate into the base editor, and they need a valid subscription. Paid offerings include features such as commenting, version history, document conversion and AI tools; check the current product terms for the specific capability you need.

The About section states the arrangement plainly: Tiptap is a collection of developer components based on open source technology, forming the basis of the advanced, paid features, and it names the open source editor component, collaboration features, Content AI, and Tiptap Cloud. The official collaboration guide documents the open-source Collaboration extension, Yjs and a self-hosted Hocuspocus backend. Hosted collaboration and advanced features have their own pricing and terms; confirm those separately.

Collaboration is a second service built on Yjs, not a flag

Hocuspocus is described as a collaboration backend built around the CRDT power of Yjs, and the editor plus Hocuspocus together form what the project calls the Tiptap Suite, with Hocuspocus serving as its backbone. A collaboration-ready CodeSandbox exists so you can see the wiring, and the examples index collects the rest.

Collaborative editing needs a Yjs provider to exchange updates. The official guide describes both a WebRTC provider and a WebSocket option using the open-source Hocuspocus backend. A self-hosted backend requires deployment and operational planning, including authentication, persistence and scaling. The README hands you the CRDT choice and the sandbox; the deployment questions are left to the documentation and the community. A reader who only needs a single-user rich text field should skip the whole second service, and a reader who needs multi-user editing should price the hosting as a line item rather than assume the editor covers it.

Three patch releases in two days, and a changelog to read them in

The recent tag dates are worth reading closely: v3.31.3 landed on 2026-09-04, v3.31.4 on 2026-09-30 and v3.32.0 on 2026-10-13, and the last push to main is dated 2026-11-02. This is a project under active development, which is exactly what you want in a dependency that ends up inside your product.

The same fact cuts the other way. Frequent patch releases mean patch-level churn, and a floating version in your package.json hands that decision to whoever published last. The tag dates alone tell you nothing about what changed, so the diff you actually need lives in CHANGELOG.md at the repository root, and reading it is part of upgrading rather than an optional courtesy. If you pin, you get stability and the obligation to track those notes yourself. If you float, the lockfile is the only record of what you tested.

Releases run through changesets with npm publish provenance

The publishing setup is unusually explicit for a library. The root manifest is private with publishConfig.provenance true, and the release path is short:

json
"test": "vp run -r build && vp run test:unit",
"test:e2e:all": "playwright test",
"publish": "vp run build && vp exec changeset publish"

A .changeset/ directory at the root holds the pending version notes, a check:package-exports script runs node scripts/check-package-exports.mjs against the workspace, and a clean:packs script removes the ./packages/*/*.tgz files, which tells you the packages are built as tarballs before they go out. Provenance means the publish is attested rather than anonymous, and the exports check means a package cannot quietly ship a broken entry point. What it does not mean is that the @tiptap/... packages move in lockstep, so a mixed-version node_modules is a state your own tests have to rule out.

Half the contribution rules are machine readable files

The tree carries the usual human files, CONTRIBUTING.md, SECURITY.md, CHANGELOG.md, and commitlint.config.mjs, and then a set that exists to be read by tools: AGENTS.md, CLAUDE.md, a .codex/ directory, .coderabbit.yaml, .zed/, .vscode/, and .vite-hooks/. There is also a .fallowrc.json with fallow audit and fallow health --score --targets scripts.

The consequence for a contributor is that the documented rules and the enforced rules are not the same document. A human reading CONTRIBUTING.md sees a subset of what the hooks and agent instructions apply, and a pull request can be shaped by configuration the README never mentions. The health script with a score target suggests the project tracks some internal measure of repository health, and nothing in the README explains what that score covers or what happens when it drops. Read the config files in the tree alongside the contributing guide rather than instead of it.

The sponsor list is a map of who benefits from the paid tier

The funding section is unusually concrete. Seven companies appear as sponsors with logos and links: Complish, Storyblok, PostHog, Reflect, Ziff Media, Basewell, and Poggio. A second line adds iFixit, ApostropheCMS, Novadiscovery, Omics Data Automation, Flow Mobile, DocIQ, and then hundreds of individuals through GitHub Sponsors.

The About section says the open source products also shape the paid features, so read the sponsor list alongside the Pro extension list. Support runs through GitHub Discussions, chosen deliberately for being searchable, and the project is tracked by the Linux Foundation insights page as well.

Editorial conclusion

Tiptap fits a team that wants to own its own editor interface and can live inside the ProseMirror model, and it fits anyone willing to run Hocuspocus for collaboration. It may need more integration work if you want a ready-made UI. Basic collaborative editing can use the open-source Collaboration extension, Yjs and a self-hosted Hocuspocus backend; evaluate hosting costs and the terms of any paid features you need. Before you commit, price the Pro extension list, run the open collaboration backend yourself if you can, and read CHANGELOG.md at the tag you pin, since recent releases include v3.31.3 on 2026-09-04, v3.31.4 on 2026-09-30 and v3.32.0 on 2026-10-13.

Frequently asked questions

What is Tiptap used for?

It is a headless, framework-agnostic rich text editor built on ProseMirror, extended through extensions rather than a bundled interface, and the documentation points to more than a hundred of them. Collaboration is handled by a separate open source backend, Hocuspocus, built around the CRDT power of Yjs.

how to install tiptap

The repository contains no install command of its own and sends you to the documentation at tiptap.dev/docs/editor/installation. To see it working before installing anything, the project publishes runnable examples at tiptap.dev/examples plus two CodeSandboxes, one a basic editor and one already wired for collaboration.

How much does Tiptap cost?

The editor core is MIT licensed. Basic collaborative editing can use the open-source Collaboration extension with Yjs and self-hosted Hocuspocus. Tiptap also sells paid features and hosted services; check the current pricing and terms for the specific features and usage you need.

how to use tiptap in react

The editor is described as framework-agnostic, working across Vue, React, and plain JavaScript. For React there is a notion-like block editor template at templates.tiptap.dev, and in the repository the root dev command starts the demos workspace where the integration is shown in code.

Is Tiptap legit?

It is an MIT licensed project with a visible corporate sponsor list including Storyblok, PostHog, Reflect, Ziff Media and Basewell, and a public issue and discussion process. It ships on a fast patch cadence, with v3.31.3 on 2026-09-04, v3.31.4 on 2026-09-30 and v3.32.0 on 2026-10-13, and the last push to main dated 2026-11-02.

What does "tiptap" mean?

The repository does not explain where the name comes from. What it states is the role the project plays: a headless, framework-agnostic rich text editor built on the ProseMirror library, complemented by the Hocuspocus collaboration backend, and together forming the Tiptap Suite.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
  4. Release notes
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/ueberdosis-tiptap.svg)](https://hysenlabs.com/projects/ueberdosis-tiptap)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/ueberdosis-tiptap.svg)](https://hysenlabs.com/projects/ueberdosis-tiptap)

Was this useful?