Notion Offline Mode Shows Conflicting Edits: Fix

When you use Notion offline and reconnection happens, you may see a banner that says “Conflicting edits detected” or see duplicate blocks and scrambled content. This occurs because Notion’s sync engine cannot automatically merge changes made on two different devices while one was offline. This article explains why these conflicts happen and provides the exact steps to resolve them without losing work.

Why Conflicting Edits Appear After Using Notion Offline

Notion’s offline mode stores your changes locally on your device. When you go back online, the app tries to sync those local edits with the version stored on Notion’s servers. If another device or user edited the same block, page, or database entry while you were offline, Notion cannot determine which change is the correct one. The result is a conflict banner and duplicated or overlapping content.

Conflicts happen most often when:

• You edit a page on your phone while your laptop is offline and also editing the same page.
• Two team members edit the same database row simultaneously, and one goes offline.
• You close Notion without waiting for sync to finish, then reopen it later offline.

Notion does not support real-time conflict resolution like Google Docs. Instead, it presents you with both versions and asks you to pick one. Understanding this limitation helps you avoid losing data.

Steps to Fix Conflicting Edits in Notion Offline Mode

Follow these steps in order. Do not skip the manual review step, as automatic choices may discard important changes.

1. Reconnect to the internet and open Notion
   Make sure your device has a stable internet connection. Open Notion. The app will attempt to sync automatically. If a conflict exists, a yellow or red banner appears at the top of the affected page with the message “Conflicting edits detected” or “Sync conflict.”
2. Click the conflict banner to open the resolution dialog
   Click the banner. Notion opens a split-view dialog showing your local version on the left and the server version on the right. Each version is labeled with the device name and the timestamp of the edit.
3. Review both versions block by block
   Scroll through both panels. Look for blocks that are duplicated, missing, or out of order. Note which version contains the correct content for each section. Do not rely solely on the timestamps — the older edit may be the correct one.
4. Choose one version or merge manually
   At the bottom of the dialog, you see three buttons: Keep This Version (left), Keep That Version (right), and Keep Both. If one version is entirely correct, click its button. If both versions have parts you need, click Keep Both. Notion will combine the content, but you must then manually delete duplicate blocks and reorder them.
5. Manually clean up the merged page
   After selecting Keep Both, the page will contain all blocks from both versions. Delete any duplicate text, images, or database entries. Drag blocks to restore the correct order. Check database properties for conflicting values — you may need to re-enter data in the correct field.
6. Use page history if the merge is broken
   If the page becomes unreadable or you accidentally deleted important content, press Ctrl+Shift+H (Windows) or Cmd+Shift+H (Mac) to open page history. Select a version from before the conflict occurred. Click Restore to revert the page to that clean state. Then re-apply your offline changes manually.

If Notion Still Shows Conflicting Edits After the Main Fix

Conflict banner does not disappear after choosing a version

Rarely, the banner persists even after you resolve the conflict. Close Notion completely and reopen it. If the banner remains, clear the Notion cache:

1. Close Notion completely.
2. On Windows, press Win+R, type %appdata%\Notion, and press Enter. Delete the Cache folder.
3. On Mac, open Finder, press Cmd+Shift+G, type ~/Library/Application Support/Notion, and delete the Cache folder.
4. Reopen Notion and sign in. The conflict should be resolved.

Database rows show duplicate entries after offline editing

When you edit a database property while offline, Notion may create duplicate rows instead of updating the existing one. To fix this, open the database, sort by the “Last edited” column to find the duplicates. Delete the rows that are clearly redundant. If you cannot tell which row is correct, export the database as CSV before deleting anything, then compare the data.

Images or files appear as broken links after reconnection

Files uploaded while offline may not sync properly. The file may still be in your local cache but not on the server. Re-upload the file while online. To avoid this in the future, wait until you are online before uploading images or attachments.

Notion Offline Mode: Conflict Resolution vs Manual Merge

Item	Conflict Resolution Dialog	Manual Merge
When to use	Banner appears automatically after sync	After choosing Keep Both, or when the dialog does not appear
Effort	Low — pick one version or keep both	High — must reorder and delete duplicates manually
Risk of data loss	Low if you pick the correct version	Medium — you may accidentally delete the wrong blocks
Best for	Short pages with few edits	Long pages or database rows with many edits

If the conflict dialog does not appear even though you see duplicate content, you must perform a manual merge. Open the page, compare it with the version in page history, and copy blocks from the history back into the current page. This is time-consuming but guarantees no data is lost.

After fixing the conflict, you can now use Notion offline with less worry. To prevent future conflicts, enable offline mode in Settings & Members > Settings > Offline Mode before you go offline. Also, avoid editing the same page on two devices at the same time. If you frequently work offline, consider using page history as a backup — press Ctrl+Shift+H to save a snapshot before editing.