Sync conflicts in Notion occur when the same page or database entry is edited on two devices at nearly the same time, and the app cannot automatically merge the changes. This typically happens when you edit a page offline on a mobile device while also making changes on the desktop app, or when two collaborators save conflicting edits within seconds of each other. Notion does not show a traditional conflict dialog like Google Docs instead, it creates duplicate content or displays a warning banner. This article explains how to identify, resolve, and prevent sync conflicts in your Notion workspace.
Key Takeaways: Resolving Sync Conflicts in Notion
- Conflict banner at top of page: Click “View conflicts” to see which edits were duplicated and need manual cleanup.
- Duplicate blocks or pages: Delete the extra content after verifying which version contains the correct data.
- Enable offline mode carefully: Avoid editing the same page on two devices while one is offline to prevent conflicts from occurring.
Why Sync Conflicts Happen in Notion
Notion uses a real-time collaborative editing model similar to Google Docs, but its conflict resolution is less automated. When you edit a page offline on the Notion mobile app or desktop app, those changes are stored locally. When the device reconnects to the internet, Notion attempts to merge your offline edits with the current server version. If the server version was also edited during that offline period, Notion cannot determine which change should win. Instead of overwriting data, Notion creates a conflict banner and duplicates the affected blocks or pages. This is a safety mechanism to prevent data loss, but it requires you to manually choose which version to keep.
Steps to Identify and Resolve a Sync Conflict
- Look for the conflict banner
Open the page that has a sync conflict. A yellow or orange banner appears near the top of the page with the text “There are conflicts in this page.” Click the “View conflicts” button in that banner. - Review the duplicated content
Notion shows you the original content and the conflicting version side by side or as duplicate blocks. Read both versions to identify which one contains the correct or most recent information. - Delete the incorrect version
Select the block or page that should be removed. Press the Delete key or click the six-dot icon on the left of the block and choose “Delete.” Keep only the version you want to preserve. - Confirm the conflict is resolved
After deleting the extra content, the conflict banner disappears. The page now shows only the data you chose to keep. If the banner remains, repeat steps 2 and 3 for any remaining duplicate blocks.
If Notion Still Shows Conflicts After the Main Fix
Conflict banner does not disappear after deleting duplicates
Sometimes the conflict banner persists even after you have removed all visible duplicate blocks. This can happen if Notion created a conflict on a subpage or a database entry within the page. Expand all toggle blocks and open any linked databases on the page. Look for conflict banners on each subpage or database item. Resolve each one individually using the same steps above.
Duplicated page appears in the sidebar or database
When a sync conflict affects an entire page rather than blocks within a page, Notion may create a duplicate page with “(conflicted copy)” appended to its title. Locate the duplicate page in your sidebar or database view. Open both the original and the conflicted copy. Manually copy any unique content from the conflicted copy into the original page. Then delete the conflicted copy by clicking the three-dot menu next to its title and selecting “Delete.”
Offline edits caused the conflict but the device is now online
If you intentionally work offline, you can reduce conflicts by enabling offline mode on only one device at a time. On the Notion desktop app, go to Settings & Members > Settings > Offline and toggle on “Make pages available offline.” On mobile, open the page you need and tap the three-dot menu, then tap “Make Available Offline.” Avoid editing the same page on two devices while one is offline. When you come back online, Notion syncs the changes and may show a conflict if another device edited the same page.
Notion Sync Behavior: Online vs Offline vs Real-Time Collaboration
| Item | Online Real-Time Editing | Offline Editing |
|---|---|---|
| Conflict risk | Very low — changes merge instantly | High — edits stored locally, merge on reconnect |
| Visibility of other edits | Cursor and changes appear live | No visibility until device reconnects |
| Conflict resolution | Automatic merge for most edits | Manual — duplicate blocks or pages created |
| Recommended usage | Always preferred for shared pages | Only when internet is unavailable |
How to Prevent Sync Conflicts in the Future
To minimize sync conflicts, follow these practices. First, keep your Notion app updated to the latest version on all devices. Outdated apps may have bugs that increase conflict frequency. Second, avoid editing the same page simultaneously on two devices if one device is offline. Third, if you must edit offline, take a screenshot of the page before you go offline so you can manually compare changes later. Fourth, use the “Last edited” property in your databases to see which version is more recent before resolving a conflict. Finally, consider using a dedicated offline device for critical edits and sync that device first before editing on another device.
Sync conflicts in Notion are a safety feature, not a bug. They prevent data loss when the app cannot automatically merge simultaneous edits. By following the steps above, you can resolve conflicts quickly and keep your workspace accurate. To further protect your data, enable page version history by going to the three-dot menu on any page and selecting “Page history.” This lets you restore a previous version if a conflict resolution goes wrong. As an advanced tip, create a dedicated database property called “Sync Status” with options like “Clean” and “Needs Review” to track pages that may have unresolved conflicts.