Logseq iCloud Not Syncing on iPhone
Workaround available iOS, iPadOS, Mac Updated October 21, 2026
Quick answer
On iOS, Logseq can only write inside its own Logseq folder in iCloud Drive; a graph stored anywhere else won't sync or shows 'renamed or deleted' errors. Move the graph into that folder, avoid opening it on two devices at once, and restart iCloud on the Mac if it stalls.
Most likely fix: Move the graph into the Logseq iCloud folder.
Symptoms
Changes made on iPhone/iPad never appear on desktop (or vice versa), pages are missing, files show as waiting to upload, or errors say a file was renamed or deleted.
Why it happens
- Graph not inside the Logseq iCloud folder
- Same graph edited on two devices at once
- iCloud daemon stuck on the Mac
- Empty pages not written as files
How to fix it
Try these in order — the most common fix is first.
1. Move the graph into the Logseq iCloud folder
- On the Mac, open iCloud Drive in Finder
- Move your graph folder into the folder with the Logseq icon (subfolders are fine)
- On iPhone, open Logseq and add the graph from that location
2. Edit on one device at a time
- Close Logseq on the Mac before editing on iPhone
- Wait for iCloud to finish uploading before switching
3. Restart iCloud sync on the Mac
- Open Terminal and run: killall bird
- Or reboot the Mac
- Check that files finish uploading in Finder
4. Recover missing text
- Check graph > logseq > bak for older copies
- Restore missing content manually
5. Consider official sync
- If iCloud keeps conflicting, use Logseq's encrypted sync (Open Collective backers) or Syncthing instead
This guide also covers
- logseq icloud not syncing
- logseq ios not syncing
- logseq iphone sync
- logseq icloud folder
- logseq pages missing ios
Still not working?
If Logseq keeps failing, you're not alone. See every Logseq problem users report or the alternatives people switch to.