Real-Time Co-Editing
Also known as: collaborative editing, live editing, simultaneous editing, multiplayer documents
Real-time co-editing (also called collaborative editing or simultaneous editing) is the ability for multiple users to work on the same document, spreadsheet, design, or code file at the same time, with each person's changes instantly visible to all other participants.
This capability is fundamental to tools like Google Docs, Google Sheets, Figma, Notion, and Coda. Real-time co-editing is enabled by operational transformation (OT) or conflict-free replicated data type (CRDT) algorithms that merge simultaneous edits without conflicts, regardless of network latency.
Real-Time Co-Editing, explained at three levels
At home
Real-time co-editing means you and someone else can work on the same document at the same time, and you both see each other's changes instantly. In Google Docs, you can see your coworker's cursor moving and their text appearing as they type, and they see yours. You're both in the same document simultaneously, with no need to take turns, lock files, or email versions back and forth.
At work
Before real-time co-editing, document collaboration meant emailing files, managing version conflicts, and manually merging changes from multiple people. With real-time co-editing, a team can write a proposal, review a financial model, or refine a design simultaneously: all in one live document. Changes are merged automatically, and there's always one single source of truth rather than multiple file versions on different people's computers.
At home
Presence indicators (showing whose cursor is where with colour-coded indicators) are a key UX element of real-time co-editing that make collaboration visible. Comment threads within documents allow asynchronous discussion of specific passages without cluttering the document itself. Suggestion mode (in Google Docs and Word) lets reviewers propose edits that the document owner can accept or reject, rather than making changes directly. These features transform documents from static files into collaborative workspaces.
At work
Real-time co-editing works differently for different content types: text documents (Google Docs, Notion pages) have well-established OT algorithms; spreadsheets (Google Sheets, Airtable) face more complexity because formula changes can have cascading effects; design files (Figma) use vector data structures with component-level merging; and code editors (VS Code Live Share, CodeSandbox) must handle syntax constraints and execution context. Each content type has different technical constraints that shape the collaborative editing implementation.
At home
Conflict-free replicated data types (CRDTs) are an alternative to operational transformation that allow distributed editing without a central server coordinating edits. CRDTs enable offline editing with eventual consistency: you can edit a document without an internet connection, and when you reconnect, your changes merge automatically with anyone else's changes made during the same offline period. Open-source libraries such as Yjs and Automerge bring CRDTs to many apps, while Google Docs uses OT with a server mediating all edits.
At work
Enterprise considerations for real-time co-editing include document locking policies (some regulated industries require controlled review cycles incompatible with free-form real-time editing), audit trails (who changed what when: available in Google Workspace and Microsoft 365 admin consoles), permission models (commenter vs. editor vs. viewer access by individual or group), and data residency (where document data is stored during real-time sync affects compliance with data sovereignty regulations). Microsoft's Copilot integration into co-editing environments adds AI-assisted content generation to the collaborative editing context.
Real-world examples
At home
Lena and a freelance contractor needed to co-write a business proposal in one day. Using Google Docs, they worked simultaneously from different locations: Lena drafting the services section while the contractor worked on pricing. They could see each other's cursors, leave inline comments, and resolve questions in the document without switching to a messaging app. The proposal was done in four hours instead of the usual two-day email chain.
At work
Fatima's UX team of six designers used Figma's real-time co-editing to run a design sprint. All six worked in the same Figma file simultaneously: some on low-fidelity wireframes, others on component design, one organizing the page structure. The real-time visibility of everyone's work surfaced inconsistencies immediately and eliminated the 'hand off design files and wait for feedback' bottleneck that had slowed their previous sprint process.
Common confusions
- Many users assume shared document links (emailing a copy) is the same as real-time co-editing — Sharing a copy of a document by email creates a separate file for each recipient: any changes they make exist only in their copy, and merging those changes back requires manual reconciliation. Real-time co-editing means everyone works in the same live document with changes instantly visible and automatically merged. The distinction is between multiple separate copies being edited independently vs. one single document being edited simultaneously.
- Some teams avoid real-time co-editing because they worry about conflicting changes overwriting each other — Real-time co-editing platforms use sophisticated algorithms (OT or CRDTs) specifically designed to merge simultaneous edits without losing anyone's changes. Conflicts (like two people editing the same word simultaneously) are handled gracefully: both changes are preserved and the system presents the result. In practice, truly conflicting simultaneous edits on the exact same text are rare because users can see each other's cursors and naturally avoid editing the same text simultaneously.
For analysts
When a client's team is still collaborating on documents by emailing files and consolidating versions manually, quantify the time cost before recommending a switch to real-time co-editing tools. Track how many email rounds and manual merges happen per document in a typical project cycle. The productivity gain from eliminating that cycle is immediate and measurable, usually one of the most impactful workflow improvements available.
History & origin
Real-time collaborative editing has roots in Douglas Engelbart's 1968 'Mother of All Demos', which showed two people editing together, but the first widely recognized live collaborative document editor was SubEthaEdit (2003), a Mac text editor. Google Docs (which grew out of Writely, a startup Google acquired in 2006) popularized real-time co-editing for office documents by bringing it to a web browser accessible to anyone without special software. The technical breakthrough was applying operational transformation algorithms to text editing: a problem formally studied since Ellis and Gibbs' 1989 paper on the GROVE group editor. Figma (launched 2016) brought real-time co-editing to design tools, which had been exclusively single-user desktop applications (Adobe products). The COVID-19 pandemic (2020) accelerated adoption of real-time co-editing tools across all categories as remote teams needed to replicate the experience of working side-by-side.