# Logseq Problems & Issues 2026 - Slow Graphs, Sync & DB Migration

Source: https://www.tryorbye.com/products/logseq
Last analyzed: 2026-10-21
Try or Bye score: 56/100

## Verdict: Try with caution

Logseq works for some teams, but users report recurring problems (score 56/100). Most reported issues: Why is Logseq so slow with a large graph?; iCloud and Dropbox sync conflicts lose text; Logseq mobile app is slow and laggy. Not a good fit for: Mobile-first note takers; Teams; Non-technical users wanting zero setup. Users most often switch to Obsidian, Tana, Anytype.

## What it is

Logseq is a free, open-source outliner for networked note-taking: daily journals, bullet blocks, backlinks, queries and a graph view. In April 2026 it split into two apps: Logseq OG (local Markdown files, maintenance-only) and the new database-based Logseq with end-to-end encrypted sync, which is still rolling out to Open Collective backers. It suits privacy-minded individuals who think in outlines; teams and mobile-first users struggle.

## Common errors & fixes

### Logseq "Unable to Start Synchronization, Please Check if the Local Time Is Correct"

This sync error appears when your computer's clock drifts from internet time, even if it looks right. Forcing a time sync in your OS settings and restarting Logseq fixes it.

1. **Force a time sync** — Windows: Settings > Time & language > Date & time > Sync now Mac: System Settings > General > Date & Time > toggle Set time automatically off and on Linux: enable NTP, e.g. timedatectl set-ntp true
2. **Check the time zone** — Make sure the time zone is set automatically or matches your location Restart Logseq
3. **Restart and log in again** — Quit Logseq completely Reopen and start sync If it persists, log out and back in to the sync account

Full guide: https://www.tryorbye.com/products/logseq/issues/check-local-time-error

### Logseq DB Import: Pages Empty or Missing

Importing a Markdown (OG) graph into the Logseq database version can leave some pages empty or skip them, and doesn't convert assets, some query macros, embeds or org-mode files reliably. Keep your Markdown folder as the backup, re-index in OG before importing, verify results, and stay on Logseq OG until it works.

1. **Back up first and keep OG** — Copy your graph folder somewhere safe Keep Logseq OG installed; the Markdown graph keeps working there
2. **Re-index in OG before importing** — Open the graph in Logseq OG Graph menu > Re-index and wait for it to finish Then run the import in Logseq (DB)
3. **Verify the import** — Compare page counts in All Pages between OG and DB Spot-check pages with images, queries and embeds List what's missing before deleting anything
4. **Re-import missing pages** — The import always creates a new graph, so redo it after fixing problem files Some users report better results importing through the Logseq CLI
5. **Report the bug** — File an issue on the logseq db-test GitHub repository with an example file

Full guide: https://www.tryorbye.com/products/logseq/issues/db-import-pages-missing

### Logseq "File Has Been Modified on Disk" Error

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.

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

Full guide: https://www.tryorbye.com/products/logseq/issues/file-modified-on-disk

### Logseq iCloud Not Syncing on iPhone

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.

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

Full guide: https://www.tryorbye.com/products/logseq/issues/icloud-not-syncing-ios

### Logseq Mobile App Slow and Laggy

The Logseq iOS and Android apps are widely reported as slow with large graphs: long loading, laggy input and endless 'parsing files'. Clearing the cache, trimming huge pages and keeping the graph small on mobile help; many users fall back to another app for capture.

1. **Clear the app cache** — iOS: delete and reinstall Logseq (your iCloud files stay) Android: Settings > Apps > Logseq > Storage > Clear cache Reopen and let the graph re-parse fully
2. **Split huge pages** — On desktop, break very long pages and journals into smaller linked pages Let them sync to the phone
3. **Let the first parse finish** — Keep the app open on Wi-Fi and charging until parsing completes Avoid editing during the first load
4. **Update the app** — Install the latest version from the App Store or Google Play The 2026 DB version includes mobile UX upgrades

Full guide: https://www.tryorbye.com/products/logseq/issues/mobile-slow

### Why Is Logseq So Slow?

Logseq slows down mostly with large graphs and very long pages: search can take seconds, pages open slowly and typing lags. Split long pages, re-index the graph, update the app and keep the graph on a local drive; the DB version is reported to be faster.

1. **Split very long pages** — Find your longest pages (huge journal days, imported docs) Move sections into their own pages and link them Or right-click a bullet and zoom in to edit just that block
2. **Re-index the graph** — Make sure no page has unsaved changes Open the left sidebar graph menu and choose Re-index Wait for parsing to finish before typing
3. **Update Logseq** — Install the latest release of Logseq OG or the DB version Older versions had known slow-typing bugs with many linked references
4. **Disable heavy plugins** — Settings > Plugins: turn off plugins one at a time Restart and compare speed
5. **Linux: adjust compositor latency** — On KDE, open System Settings > Display > Compositor Set latency to prefer lower latency Restart Logseq
6. **Try the DB version on a copy** — Back up your graph folder Import a copy into Logseq (DB) and compare speed before switching

Full guide: https://www.tryorbye.com/products/logseq/issues/slow

### Logseq Sync Not Working

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.

1. **Sync your system clock** — Windows: Settings > Time & language > Date & time > Sync now Mac: System Settings > General > Date & Time > turn on Set time automatically Restart Logseq and try again
2. **Find and rename very long page names** — Open the developer console (Cmd+Option+I on Mac, Ctrl+Shift+I on Windows/Linux) and look for 'file name is too long' Rename or delete the page with the very long title Let sync run again
3. **Sign out and back in** — Open the sync menu and log out Quit and reopen Logseq Log in and re-enable sync for the graph
4. **Check your sync access** — Confirm your Open Collective contribution is active Make sure you're using the same Logseq account on every device Contact Logseq on the forum if sync still won't appear
5. **Test another network** — Try a home or mobile hotspot instead of a work network If that works, ask IT to allow Logseq through the firewall
6. **Wait for a full sync before editing** — Open Logseq on the second device and wait until sync shows it's up to date Only then start editing to avoid overwriting newer content

Full guide: https://www.tryorbye.com/products/logseq/issues/sync-not-working

### Logseq Blank White Screen on Startup

A blank white (or black) Logseq window usually comes from corrupted local app data, a broken config.edn or a bad update. Update Logseq, check the developer console, re-index, and if needed back up and remove the local app-data folder.

1. **Update or reinstall Logseq** — Download the latest version from logseq.com or GitHub Install over the existing app and restart
2. **Check the console for errors** — Press Cmd+Option+I (Mac) or Ctrl+Shift+I (Windows/Linux) Look at the Console tab for a red error pointing to config.edn, a plugin or a theme
3. **Re-index the graph** — If the sidebar appears briefly, open the graph menu and choose Re-index
4. **Reset local app data (backup first)** — Quit Logseq Mac: rename ~/Library/Application Support/Logseq to Logseq-old Windows: rename C:\Users\<you>\.logseq to .logseq-old Reopen Logseq and add your graph folder again; your notes stay in the graph folder
5. **Undo recent config.edn edits** — Open your graph folder > logseq > config.edn in a text editor Revert the last change or restore a backup copy Restart Logseq

Full guide: https://www.tryorbye.com/products/logseq/issues/white-screen

## Common problems

- **Why is Logseq so slow with a large graph?** (performance): Users with thousands of pages report slow search (around 3 seconds), notes taking about a second to open, long re-index times and typing lag. Pages with 500+ bullets or many code blocks are the usual trigger; one user cited slowness at roughly 3,400 pages as a reason to leave.
- **iCloud and Dropbox sync conflicts lose text** (reliability): Keeping the same graph open on two devices synced by iCloud, Dropbox or OneDrive triggers 'file has been modified on disk' prompts and occasionally older versions overwriting newer ones. Users recover text from the logseq/bak folder, but one Android user lost most notes by picking the wrong option.
- **Logseq mobile app is slow and laggy** (mobile): Android users describe the app as nearly unusable with slow loading and laggy input, and reviews consistently rate mobile as the weakest part of Logseq, years behind desktop. Several people switched after opening the same files in Obsidian mobile and finding it far smoother.
- **Logseq sync not working or overwriting notes** (reliability): Forum threads report Logseq Sync stuck, refusing to start ('check if the local time is correct'), failing on long file names, or overwriting content edited before a device finished syncing. Some users also found it too slow to be usable.
- **Logseq OG frozen: Markdown version gets no new features** (reliability): Since the April 2026 split, the file-based app (now Logseq OG) only receives security, dependency and Electron updates. Users who chose Logseq for plain Markdown files must either accept a frozen app or move to the database version, where Markdown support is still being researched.
- **Migrating a Markdown graph to Logseq DB loses pages** (reliability): Users importing large Markdown graphs into the database version report some pages arriving empty or missing, #tags converted to links, broken image assets and unsupported query macros, embeds and org-mode files. The import always creates a new graph rather than merging.
- **Is Logseq dead? Years of slow releases** (reliability): The long database rewrite had no public timeframe, the stable app went months without updates and commit activity dropped in late 2025. Users who moved away cite lost faith after the stagnation, even though the DB version is now actively developed.
- **Steep learning curve for blocks and queries** (onboarding): Reviews say people who quit Logseq cite the learning curve; some needed months for the block-based workflow to feel natural. Advanced queries are a common sticking point.
- **Logseq opens to a blank white screen** (reliability): Desktop users on Windows, Mac and Linux report a white or black window on launch, often after an update or a config.edn edit. Fixes involve clearing the app-data folder or re-indexing; some Linux cases had no confirmed fix.
- **Logseq sync requires paying through Open Collective** (pricing): The app is free, but official sync and DB early access are tied to Open Collective tiers ($5/month Backer, $15/month Sponsor), with invites rolled out gradually. Free users must set up their own syncing via iCloud, Dropbox or Git, which is where most conflicts happen.
- **No real team collaboration yet** (usability): Logseq is built for individuals. Collaboration is a stated goal of the database version, but comparison articles still group Logseq with single-user tools and point teams to Tana or Notion.
- **Missing tasks, calendar and AI built in** (integrations): Reviewers note Logseq has no proper task manager, calendar or email integration and no built-in AI organization, so many users run two or three apps alongside it.

## What users like

- **Free and open source**: The desktop and web apps are free for personal and company use; paying is optional and goes to Open Collective.
- **Privacy-first, local data**: Logseq OG stores notes as local Markdown files, and the new sync encrypts data on-device with your own password before it reaches Logseq's servers. Reviewers rate privacy and data ownership as its strongest point.
- **Excellent outliner and daily journal**: Users who like thinking in bullets praise the block outliner, block references and journal-first workflow; it's often what people miss after switching to Obsidian.
- **Easy to leave: plain Markdown files**: Because OG graphs are Markdown, users can open the same folder in Obsidian; only Logseq-specific syntax like page-link tags and date links needs cleanup.
- **DB version is noticeably faster**: Early users of the database version describe it as very fast, and the team positions it as the path to better performance and sync.
- **Self-hosted sync option**: 2026 changelogs added a custom sync server URL, so technical users can run their own sync server.

## Pricing

- **Free**: $0.00 (free) — hidden costs: Official sync is not included; you have to sync files yourself with iCloud, Dropbox, Syncthing or Git, which risks conflicts.
- **Backer (Open Collective)**: $5.00 (monthly) — hidden costs: Paid as a recurring Open Collective contribution, not a normal subscription; processor fees are deducted.
- **Sponsor (Open Collective)**: $15.00 (monthly)

## Who should and shouldn't use it

- **Privacy-focused individuals** — Good fit: Local storage, open source and on-device encryption keep notes under your control.
- **Outliner and journaling fans** — Good fit: The block outliner and journal-first flow are its best-loved features.
- **Students and researchers on a budget** — Good fit: Everything core is free; linked notes work well for literature notes.
- **Users with very large graphs** — Depends: Thousands of pages slow OG down; the DB version is faster but still in beta.
- **Mobile-first note takers** — Avoid: The mobile app is consistently called slow and behind desktop.
- **Teams** — Avoid: No mature collaboration yet; Notion or Tana fit shared work better.
- **People who want plain Markdown long-term** — Depends: Logseq OG keeps Markdown but is maintenance-only; the DB version moves away from files.
- **Non-technical users wanting zero setup** — Avoid: Sync, queries and the OG/DB split require tinkering.

## Alternatives

- **Obsidian** (https://www.tryorbye.com/products/obsidian): The closest replacement: same local Markdown approach, much faster on large vaults and mobile, huge plugin ecosystem. You lose Logseq's native outliner and block-first feel.
- **Tana** (https://www.tryorbye.com/products/tana): Outliner with supertags and team features; better for shared work. Cloud-only, no local-first mode, and paid plans for full use.
- **Anytype** (https://www.tryorbye.com/products/anytype): Open-source, local-first with end-to-end encrypted sync included; object-based instead of outline-based.
- **Capacities** (https://www.tryorbye.com/products/capacities): Object-based notes (books, people, meetings) with built-in AI and a polished UI; cloud-based and less suited to pure outlining.
- **Roam Research** (https://www.tryorbye.com/products/roam-research): The original block-reference outliner Logseq was modeled on; stable and cloud-synced, but about $15/month and cloud-only.
- **Notion** (https://www.tryorbye.com/products/notion): Best when you need team collaboration and databases; much weaker for offline use and privacy.

## FAQ

### Is Logseq worth it in 2026?

For individuals who love outlining and want free, private, local notes, yes. It's harder to recommend if you rely on mobile, have a very large graph, or need team features. The 2026 split means you pick between a frozen Markdown app (Logseq OG) and a faster database version still rolling out to backers.

### Is Logseq dead?

No. After a long, quiet database rewrite, Logseq split in April 2026: the database version is actively developed with new sync, mobile and CLI work, while the Markdown app became Logseq OG and only gets security and Electron updates.

### Is Logseq free?

Yes. The desktop and web apps are free for personal and company use. Paying via Open Collective ($5/month Backer or $15/month Sponsor) gives early access to builds, the DB version and official sync.

### How much does Logseq Sync cost?

Sync is tied to Open Collective: a July 2026 update said DB beta and RTC sync are available to all active monthly backers ($5/month). There's no separate public sync price page yet, so check Open Collective before paying.

### What is the difference between Logseq OG and Logseq DB?

Logseq OG is the original app that stores notes as Markdown files; it's in maintenance mode. Logseq (DB) stores notes in a database, adds encrypted sync and is where new features land. Both can be installed side by side.

### Why is Logseq so slow?

Mostly large graphs and very long pages: users with thousands of pages or pages with 500+ bullets report slow search, slow page opening and typing lag. Splitting long pages, re-indexing and keeping the graph outside busy sync folders help; the DB version is reported to be faster.

### Should I switch from Logseq to Obsidian?

If speed, mobile or long-term Markdown support matter most, many users have and say it felt much faster. Because both use Markdown, you can open the same folder; expect to fix Logseq-specific tags, date links and block references.

### Can I use Logseq with iCloud?

Yes, but on iOS the graph must live inside the Logseq folder in iCloud Drive, and you should avoid having the graph open on two devices at once, or you'll get sync conflicts.

### Will my Markdown notes survive the move to Logseq DB?

Your Markdown files stay untouched and keep working in Logseq OG. Importing them into the DB version creates a new graph; users report some empty or missing pages, broken assets and unsupported macros, so keep a backup and check results.

### Is Logseq good on mobile?

It works offline, but reviews and forum users consistently call the iOS and Android apps slow and behind desktop. If you take most notes on a phone, test it with your real graph first.

### Is Logseq secure and private?

It's one of the more private options: OG keeps files locally, and the new sync encrypts data on your device with your own password before upload.

### Can teams collaborate in Logseq?

Not really yet. Collaboration is a goal of the DB version, but for shared notes today Notion or Tana are better choices.

---
Try or Bye aggregates problem patterns from user reviews, forums, and app stores. Methodology: https://www.tryorbye.com/methodology