When multiple people edit a Notion page at the same time, sync conflicts can create duplicate blocks, lost text, or broken formatting. Notion does not offer a built-in per-page conflict resolution setting. However, you can manage how conflicts are avoided or handled using workspace-level settings, page permissions, and real-time collaboration best practices. This article explains the root cause of sync conflicts and provides actionable steps to reduce or resolve them on a per-page basis.
Key Takeaways: Managing Notion Sync Conflicts per Page
- Workspace Settings > General > Offline Mode: Disable offline mode to prevent stale edits from creating conflicts.
- Page-level share permissions: Restrict edit access to a smaller group to reduce simultaneous edits.
- Manual conflict resolution: When a conflict occurs, use the conflict banner to compare versions and merge manually.
Why Notion Sync Conflicts Happen and How They Affect Pages
Notion sync conflicts occur when two or more users edit the same block or page simultaneously while at least one user is offline or has a slow connection. Notion uses a collaborative editing model where changes are synced in real time. When a user goes offline, makes edits, and then reconnects, the server may receive conflicting versions of the same block. The result is a duplicate block, a split page, or a conflict banner at the top of the page that requires manual resolution. This is not a bug but a design trade-off to support offline editing and real-time collaboration.
What Triggers a Sync Conflict
A sync conflict is triggered when the server receives two different edit histories for the same block. This happens most often when:
- A user edits a page while offline and another user edits the same block online.
- Two users edit the same block within milliseconds of each other on a slow network.
- A third-party integration modifies a page while a user is actively editing it.
How Conflicts Appear in Notion
When a conflict is detected, Notion adds a yellow banner at the top of the page that says “Sync conflict detected.” Below the banner, the conflicting block appears twice, sometimes with a small warning icon. The user must manually decide which version to keep or merge the content.
Steps to Reduce Sync Conflicts on a Specific Page
Since Notion does not allow setting a conflict resolution strategy per page in the traditional sense, the best approach is to reduce the chance of conflicts and handle them when they appear. Follow these steps for each page where you want tighter control.
- Open the page that needs conflict control
Navigate to the page in your workspace. Make sure you are the workspace owner or an admin with page-level permissions. - Click Share in the top-right corner
The Share menu shows all people and groups with access to this page. Click the Share button to open the panel. - Remove edit access for unnecessary collaborators
For each person or group that does not need to edit, change their permission from “Can edit” to “Can view” or “Can comment.” Reducing the number of editors directly reduces the chance of simultaneous edits. - Disable offline mode for the workspace
Go to Settings & Members > Settings > General. Under Offline Mode, toggle it off. This forces all edits to happen online, preventing stale offline edits from causing conflicts. Note that this affects the entire workspace, not just one page. - Encourage editors to refresh the page before editing
Teach your team to press F5 or Ctrl+R before starting to edit a high-traffic page. This ensures they have the latest version and reduces the chance of editing a stale copy. - Use a locked template for critical pages
If the page is a template, lock it by clicking the three-dot menu in the top-right, selecting Lock page. Editors cannot modify locked content, which eliminates conflicts entirely for that section.
How to Manually Resolve a Sync Conflict When It Occurs
When a conflict does happen, you must resolve it manually. Notion does not offer an automatic merge or a “keep latest” option. Here is the step-by-step process to resolve a conflict on a per-page basis.
- Locate the yellow conflict banner at the top of the page
The banner says “Sync conflict detected.” Below it, you will see two versions of the same block side by side or stacked. - Compare the two versions
Read both versions carefully. One may contain edits from an offline user, the other from an online user. Decide which version is correct or if you need to merge text from both. - Delete the version you do not want
Click the six-dot handle to the left of the block you want to remove and select Delete. Alternatively, select the text and press Backspace or Delete. - Merge content if needed
If both versions contain valuable information, copy the text from the deleted block and paste it into the kept block. Format the merged content as needed. - Dismiss the conflict banner
After you delete or merge all conflicting blocks, the yellow banner disappears automatically. The page is now synced.
If Notion Still Shows Sync Conflicts After Following the Main Steps
Conflict banner appears even with one editor
If only one person is editing the page but conflicts still appear, the issue is likely caused by a third-party integration or a slow sync. Check your integrations by going to Settings & Members > Connections. Remove any integrations that may be modifying the page. Also, clear your browser cache and reload Notion.
Duplicate blocks keep reappearing after deletion
This happens when the conflict is not fully resolved. Make sure you delete every duplicate block, not just the first one. Sometimes Notion creates multiple conflict blocks. Scroll through the entire page and delete all duplicates. If the problem persists, duplicate the page and delete the original.
Offline edits are not syncing at all
If a user made offline edits and those edits never appear, the offline session may have expired or the device lost its local storage. To prevent this, ask users to manually trigger a sync by opening the page on a stable internet connection and waiting for the sync icon in the top-left to turn solid. If the offline edits are gone, they cannot be recovered.
Notion Sync Conflict Prevention Methods Compared
| Method | Scope | Effectiveness |
|---|---|---|
| Disable offline mode in workspace settings | Entire workspace | High — prevents all offline conflicts |
| Restrict page permissions to fewer editors | Per page | High — reduces simultaneous edits |
| Lock the page | Per page | Very high — eliminates edits entirely |
| Refresh page before editing (F5 or Ctrl+R) | Per user session | Medium — depends on user discipline |
| Manual conflict resolution | Per conflict | Low — reactive, not preventive |
Notion does not have a per-page conflict resolution strategy setting. The methods listed above are the only ways to control how conflicts are prevented or handled on a specific page. Locking the page is the most reliable method for content that must never be edited simultaneously.
You now understand that sync conflicts in Notion are caused by concurrent edits, especially when one user is offline. By restricting page permissions, disabling offline mode, and locking critical pages, you can significantly reduce conflicts. When a conflict does appear, use the manual resolution steps to merge or delete duplicate blocks. For maximum control, combine page locking with workspace-level offline mode disablement.