Try or ByeTry or Bye

Logseq Sync Not Working

Workaround available Windows, Mac, Linux, iOS, Android Updated October 21, 2026

Quick answer

Logseq Sync usually stalls because of a wrong system clock, a file name that's too long, firewall blocks or an account without sync access. Sync the system clock, find and rename the offending page, sign out and back in, and confirm your Open Collective backer status.

Most likely fix: Sync your system clock.

Symptoms

Sync icon stays grey or spinning, changes don't reach other devices, sync works on one device but not another, or an error says it can't start synchronization.

Why it happens

  • System clock out of sync
  • A page whose file name is too long for the filesystem (often from Zotero or web clips)
  • Firewall or corporate network blocking the connection
  • Account doesn't have sync access (backer status or invite)
  • Editing on a device before it finished pulling changes

How to fix it

Try these in order — the most common fix is first.

  1. 1. Sync your system clock

    1. Windows: Settings > Time & language > Date & time > Sync now
    2. Mac: System Settings > General > Date & Time > turn on Set time automatically
    3. Restart Logseq and try again

  2. 2. Find and rename very long page names

    1. Open the developer console (Cmd+Option+I on Mac, Ctrl+Shift+I on Windows/Linux) and look for 'file name is too long'
    2. Rename or delete the page with the very long title
    3. Let sync run again

  3. 3. Sign out and back in

    1. Open the sync menu and log out
    2. Quit and reopen Logseq
    3. Log in and re-enable sync for the graph

  4. 4. Check your sync access

    1. Confirm your Open Collective contribution is active
    2. Make sure you're using the same Logseq account on every device
    3. Contact Logseq on the forum if sync still won't appear

  5. 5. Test another network

    1. Try a home or mobile hotspot instead of a work network
    2. If that works, ask IT to allow Logseq through the firewall

  6. 6. Wait for a full sync before editing

    1. Open Logseq on the second device and wait until sync shows it's up to date
    2. Only then start editing to avoid overwriting newer content

This guide also covers

  • logseq sync not working
  • logseq sync stuck
  • logseq sync doesn't work
  • logseq sync not syncing
  • unable to sync logseq graph

Still not working?

If Logseq keeps failing, you're not alone. See every Logseq problem users report or the alternatives people switch to.

Other Logseq errors