Notion Block Editor Performance: Engineering a Smooth Experience

Tech · 7 min read

Notion’s block editor uses collaborative CRDTs to maintain conflict-free edits across clients, but the original implementation suffered from rendering jank and sync delays under larger documents. Engineers reworked the rendering pipeline to implement virtualized DOM diffing for blocks, incremental layout calculations, and prioritized sync streams. The approach decouples collaborative state convergence from immediate visual updates to keep the editor responsive.

A key technical pivot was batching operational transforms and performing local optimistic updates while queuing heavier semantic operations (like formula recalculations) in background workers. This reduces perceived latency for typing and drag-reorder operations. The team also introduced content-level snapshots that allowed clients to reconcile large-scale edits without retransmitting entire document trees.

The tradeoff involves eventual consistency nuances: users occasionally observe transient divergence in formula outputs or embedded widget states until background reconciliation completes. Notion offsets user confusion with explicit sync indicators and manual refresh affordances. The case shows that scalable collaborative editors require both CRDT correctness and pragmatic engineering to meet modern UX expectations.