September Special:  Up to 30% off on all plans for new users
Days
Hours
Minutes
Seconds
x
Skip to content

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!

Select Mode
·
 
Your editor

Test the Collaborative Editing features using this demo. This is a dummy content.
Replace it with your template.

Editor 2 · same document
 

Two editors, one document. Type on either side and watch it appear
on the other.

4.2 out of 5 · 33 reviews on Trustpilot

“I’ve been using Froala for 5 years now and its stable and easy to use. Customer support is excellent (Sandy is amazing)”

1 STEP ONE

Set the name and role of the teammate you are inviting.

2 STEP TWO
Send it to your teammate, or open it in a second browser window to play both sides yourself.
3 STEP THREE

Start editing together

Everyone on the same docid sees cursors, comments, suggestions and version history update instantly.

Four capabilities, one plugin

Enable Collaborative Editing Plugin and you get all four. Each one is scriptable through the plugin’s options, methods and events.

Real-time editing

A CRDT engine merges concurrent edits, so two people typing in the same sentence never overwrite each other. Presence indicators show who is in the document and where their cursor is, over a WebSocket connection

Comments

Highlight any text and attach a threaded comment anchored to that exact content. Teams reply inline, @mention teammates, resolve or reopen threads, and filter the sidebar by status.

Version control

Every snapshot is timestamped and attributed. Browse the history, compare any two versions side by side, restore a prior state in one click, and keep a full audit log for compliance.

Suggestion mode

Reviewers propose insertions, deletions and rewrites without touching the live document. Owners accept or reject each suggestion individually or in bulk
Included

On every Froala plan

∞

Collaborators per doc

Node.js SDK
For backend setup

Add it to your project

Load the plugin script and stylesheet, point the editor at your collaboration server, and pass the document id and the signed-in user. That is the basic client-side integration.
The backend ships in 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.
editor.js 
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
See pricing
Questions

Collaborative editing plugin FAQ

What happens to my content when I close the demo?

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.

Ship collaborative editing this sprint

Collaboration is included in all Froala plans. Add your key and every feature on this page is unlocked. All plans support unlimited users and editor loads.