Logseq "File Has Been Modified on Disk" Error
Workaround available Windows, Mac, Linux, iOS, Android Updated October 21, 2026
Quick answer
Logseq shows this prompt when a file changed outside the app while it was open, usually from iCloud/Dropbox/OneDrive sync, an external editor or multiple windows. Pick the version carefully, recover from logseq/bak if needed, and keep the graph open on one device at a time.
Most likely fix: Compare before choosing.
Symptoms
A prompt asks whether to keep the disk version or the Logseq version; it keeps reappearing; text disappears after choosing.
Why it happens
- Cloud sync service updating files while Logseq is open
- Editing the same file in VS Code, Obsidian or another editor
- Multiple Logseq windows holding separate copies
- Files outside the pages folder with permission errors
How to fix it
Try these in order — the most common fix is first.
1. Compare before choosing
- Read both versions in the diff dialog
- Keep the one with your newest text; copy anything missing from the other first
2. Recover lost text from backups
- Open your graph folder > logseq > bak
- Find the page's backup copies by date
- Copy the missing text back into the page
3. Use one device and one window at a time
- Close Logseq on other devices before editing
- Avoid multi-window mode on the same graph
- Wait for iCloud/Dropbox to finish syncing before opening
4. Re-index the graph
- Open the graph menu and choose Re-index
- Reopen the page
5. Keep notes inside the pages folder
- Move Markdown files edited elsewhere into graph > pages
- Re-index
This guide also covers
- logseq file has been modified on disk
- logseq modified on the disk
- logseq conflict
- logseq lost notes
- logseq bak folder
Still not working?
If Logseq keeps failing, you're not alone. See every Logseq problem users report or the alternatives people switch to.