Real-time Collaboration: Figma's 'Multiplayer' Model

Why it exists

Traditional workflows involved exporting, syncing, or emailing file copies, creating version control chaos and siloing collaborators. Real-time collaboration was created to establish a single source of truth, accessible to anyone with a link, making creative and technical work more inclusive and efficient.

The mental model

Shift from thinking about a file to thinking about a shared state. Instead of multiple people holding separate local copies, everyone connects to one authoritative document state hosted on a server. Your screen is a live viewport into that state, and your edits are messages sent to the server to update it for everyone at once.

How it works

Figma uses a client-server architecture. When you open a document, your client (a web page) downloads the file and opens a persistent WebSocket connection to a server process dedicated to that document. From then on, all edits are sent as small updates over the WebSocket and broadcast to other connected clients. The system handles offline work simply: when you reconnect, your client downloads a fresh copy of the document, reapplies your offline edits on top of this latest state, and then resumes live syncing. This design choice simplifies the complexity of merging changes after a long disconnection.

When to use it

This model is ideal for productivity tools where multiple stakeholders need to contribute to or view a single artifact concurrently. It shines in design tools, word processors, and diagramming software where the cost of version conflicts and manual syncing is high. It allows different roles, like writers and developers, to participate directly in the design process.

When not to use it

Building a robust real-time system is complex. For projects where work is naturally sequential or teams are small, simpler version control may be sufficient. If an application doesn't require simultaneous editing, the engineering overhead is likely not worth it. Figma itself avoided standard, highly complex algorithms like Operational Transforms (OTs) to ship faster, indicating that even pioneers of the space look for simpler solutions.

One canonical example

Figma's 'multiplayer' editing. When it launched, the idea of live collaboration in a design tool was controversial, with fears of "hovering art directors." Figma's bet was that making design accessible via a simple link would be transformative. By building their own custom, simpler-than-alternatives solution, they proved that real-time collaboration is a fundamental feature for modern web-based productivity tools, not just a novelty.