The Collaborative Rich Text Editor
Real-time cursors, comments, suggestions and version history, built into the Froala rich text editor. It's free with every license - start typing!
Test the Collaborative Editing features using this demo. This is a dummy content. Replace it with your template.
Two editors, one document. Type on either side and watch it appear on the other.
One editor, full toolbar. Share the invite link so someone else can join and edit with you.
“I’ve been using Froala for 5 years now and its stable and easy to use. Customer support is excellent (Sandy is amazing)”
This demo runs on our own server. Both tabs sync through a Froala-hosted deployment of the very backend on this site, so what you are testing is the same Node app you would run yourself. Your documents live on your own deployment, and the backend quickstart takes about ten minutes.
1
STEP ONE
Customize the room link
name and role of the teammate you are inviting. 2
STEP TWO
Share the link
3
STEP THREE
Start editing together
On every Froala plan
Collaborators per doc
Four capabilities, one plugin
Real-time editing
Comments
Version control
Suggestion mode
Add it to your project
wysiwyg-editor-node-sdk: a WebSocket relay, REST endpoints for comments and suggestions, a version store and an async save endpoint. All four can share one HTTP server and one SQLite file. new FroalaEditor('.selector', { collabConfig: { user: { id: 'user-id', name: 'user-name', role: 'suggester', }, docId: 'my-doc', commentsUrl: 'http://your-app.com/collab/my-doc/comments', suggestionsUrl: 'http://your-app.com/collab/my-doc/suggection', realTime: { syncUrl: 'ws://your-app.com' }, versionControl: { url: 'http://your-app.com/collab/my-doc/versions' } } });
Included on every plan
Froala includes all four collaboration capabilities on every plan. No collaboration SKU, no per-seat fee, no upgrade path to unlock what you just tried. Add your key and it works.
And because you run the backend yourself, your documents, comments, and version history stay on your infrastructure, not in a vendor’s cloud, not subject to their retention policy, not a question your security review has to answer.
Froala | TinyMCE | CKEditor | |
|---|---|---|---|
Real-time co-editing | Included | Not offered | Premium tier |
Comments | Included | Premium tier | Premium tier |
Suggestions | Included | Separate add-on | Premium tier |
Version history | Included | Separate add-on | Premium tier |
Where documents live | Your infrastructure | Vendor cloud | Vendor cloud |
Collaborative editing plugin FAQ
This demo runs entirely in browser memory using an ephemeral WebSocket relay. Content, comments, suggestions, and version history exist only while at least one collaborator is connected. The moment the last editor closes their tab, all data is discarded. There is no fallback recovery even if you rejoin with the same docId.
This is by design: the demo showcases the collaborative editing experience without persisting sensitive test data. For production deployments, you control the persistence layer entirely.
For real-time editing, yes. Peers sync through a WebSocket relay, so something has to run it. Comments, suggestions, and version history use REST endpoints and a database. With no sync URL configured, the editor runs in async save mode against a single content endpoint.
Conflict resolution happens in the browser using Yjs, a CRDT library. The server relays updates verbatim to the other peers in the same docId, and each client merges them deterministically.
Every Froala plan includes unlimited users and unlimited editor loads, so collaborators stay unmetered. The practical ceiling is your backend. The reference SQLite setup is single-instance and single-writer, which comfortably handles typical document teams.
