Why Notion Sync Cannot Show Real-Time Cursor for Specific Browsers

You may notice that when you collaborate in a Notion document, the colored cursor showing where your teammate is typing does not appear in certain web browsers. This real-time cursor feature relies on WebSocket connections and specific browser APIs that not all browsers support equally. This article explains the technical reason behind the missing cursor, lists which browsers are affected, and shows how to verify your browser’s compatibility so you can switch to a supported one if needed.

Why Notion Real-Time Cursor Depends on WebSocket and SharedWorker

Notion’s real-time collaboration feature uses WebSocket technology to maintain a persistent, two-way communication channel between your browser and Notion’s servers. When you move your cursor or type, your browser sends a small data packet through this channel. Other collaborators’ browsers receive the packet and render a colored cursor at the corresponding position.

To keep this channel alive even when you switch tabs or minimize the window, Notion also relies on the SharedWorker API. A SharedWorker is a background script that runs independently of any single browser tab. It maintains the WebSocket connection so that your cursor remains visible to others even if you briefly navigate away from the Notion tab.

Some browsers either lack the SharedWorker API entirely or restrict how WebSocket connections are managed in background scripts. When the SharedWorker cannot start or the WebSocket handshake fails, Notion falls back to a polling mechanism that only syncs changes at intervals of several seconds. In this fallback mode, real-time cursor movements are not transmitted, and the colored cursor disappears from collaborators’ views.

Which Browsers Are Fully Supported

Notion officially supports Google Chrome and Microsoft Edge (both built on the Chromium engine) for real-time cursor display. These browsers implement SharedWorker and WebSocket according to the W3C specification without additional security restrictions that would block the connection. Users on Chrome 90 or later and Edge 90 or later will see real-time cursors without any manual configuration.

Which Browsers Have Limited Support

Mozilla Firefox and Apple Safari are known to have intermittent issues with Notion’s real-time cursors. Firefox has historically restricted SharedWorker lifetime in certain privacy modes, causing the background script to terminate after a few minutes. Safari, especially on iOS, limits WebSocket connections when the tab is not active, which prevents cursor updates from being sent. In both cases, the cursor appears frozen or does not appear at all.

Steps to Check and Fix Real-Time Cursor in Your Browser

1. Open the Browser Developer Console
   Press Ctrl+Shift+J on Windows or Cmd+Option+J on macOS to open the console. In Firefox, press Ctrl+Shift+K or Cmd+Option+K.
2. Check for WebSocket Errors
   Type navigator.onLine in the console and press Enter. If it returns true, your network connection is active. Then look for any red error messages containing the words “WebSocket” or “SharedWorker”. A message like “WebSocket connection to ‘wss://…’ failed” confirms the browser is blocking the connection.
3. Verify SharedWorker Support
   Type typeof SharedWorker in the console and press Enter. If the result is "undefined", your browser does not support SharedWorker. Real-time cursors will not work in that browser.
4. Switch to a Supported Browser
   If you see errors or "undefined", install Google Chrome or Microsoft Edge. Open the same Notion page in the new browser and confirm that the colored cursor appears when a collaborator edits.
5. Disable Browser Privacy Extensions
   In Firefox, open Settings > Privacy & Security > Enhanced Tracking Protection. Set it to “Standard” or add notion.so to the exceptions list. In Safari, go to Safari > Settings > Privacy and uncheck “Prevent cross-site tracking” if it is enabled.

If Notion Still Shows No Cursor After Switching Browsers

Cursor Visible Only in Desktop App but Not in Browser

The Notion desktop app uses a native WebSocket implementation that bypasses browser restrictions entirely. If you see cursors in the desktop app but not in any browser, the issue is browser-specific. Continue using the desktop app for real-time collaboration, or update your browser to the latest version.

Cursor Appears but Freezes After a Few Minutes

This symptom indicates that the SharedWorker terminated. In Firefox, open about:config, search for dom.workers.sharedWorkers.enabled, and confirm it is set to true. In Safari, ensure you did not enable “Private Browsing” mode, which disables SharedWorker entirely.

Cursor Shows for Some Collaborators but Not Others

Each collaborator must use a supported browser. Ask the person who cannot see cursors to follow the verification steps above. If all collaborators are on Chrome and cursors still fail, a Notion server-side issue may be present. Check the Notion Status page at status.notion.so for ongoing incidents.

Browser Support for Notion Real-Time Cursor: Comparison

Item	Google Chrome	Mozilla Firefox
WebSocket support	Full	Full
SharedWorker support	Full	Partial (disabled in Private Browsing; may terminate after inactivity)
Real-time cursor visible	Yes	Not reliably
Recommended for Notion collaboration	Yes	No

Apple Safari is not included in the table because its behavior varies significantly between macOS and iOS versions. In general, Safari on macOS has partial SharedWorker support, while Safari on iOS lacks it entirely. For a consistent real-time cursor experience, use Chrome or Edge on all platforms.

You can now identify whether your browser supports Notion’s real-time cursor by checking for WebSocket and SharedWorker availability. If the cursor is missing, switch to Google Chrome or Microsoft Edge, or use the Notion desktop app. For advanced troubleshooting, disable privacy extensions that block WebSocket connections and verify that your browser is up to date.