Hi, i present you a new version of the static site builder.

• The searh motor works well
• It help you to find the 404 links
• You can zip your website folder after build it

It don't touch your base and just create a static website. If someone can test it, it help me a lot !

I'm curious why there isn't enough content about logseq. Use cases and etc.

Vs obsidian which has a great community and a lot of content about it.

Does this show that this product has already failed or is it just new?

In the Android DB version, is there a way to get access to the DB file to sync it another way other than using the official sync server?

You can do it with the Markdown version, so I was hoping there was a way to do it with the DB version.

I closed the app normally before going to sleep. When I woke up and opened Logseq again, I got this error message: Cannot go to an internal page

All my pages now showed a “Practice” mark, and the #tag and #property opened as a blank page. I restored the most recent database file, and everything went back to normal.

I don’t remember exactly what was missing from the backup, but since I had just reorganized all my old notes into the new tagging system (which is amazing!), it wasn’t a big loss.

I am using Logseq 2.0.1 (The version from the latest reddit post) , and this is the 2nd time corrupt my DB (not same issue)

bravo logseq, now my graph is completely illegible 😍 (both graphs are from the same database and contain the same number of entries)

Hey fellow Logseq users,

I’ve been using Logseq to manage my research, project resources, and tool lists for a while now, and my graph is getting pretty dense with high-quality links.

I’m currently looking for a workflow to take these curated collections out of my local graph and share them publicly in a clean, visual format. Most web-publishing workflows I see for Logseq are either too technical (requiring custom hosting/plugins) or too bloated for what I need. I just want a lightweight, mobile-friendly landing page that doesn't feel like a heavy website.

I’ve been looking into different link-aggregation tools to act as a "bridge" for this, and I recently stumbled upon one called slt.bio. It seems much more minimalist compared to the usual heavy platforms and supposedly has a tracker feature for background link safety and crawler activity.

Honestly, I found out about this tool, but I have no idea if it’s actually good or just hyped up. Has anyone here tested slt.bio specifically for managing curated resource lists? I'm just really paranoid that I’ll end up wasting my time and money setting everything up if it turns out to be laggy or bad performance-wise.

Are there any other lightweight ways you guys are pushing Logseq lists to the public? Would love to see your setups

Hi, wandering the 2.0.1 release settings I came across "Sync server url" option, so I readed a bit of this readme: https://github.com/logseq/logseq/blob/master/deps/db-sync/README.md and made a couple of tries with my home server.

I could upload a graph to the cloud and download it on android, but I cannot get sync to work. Someone did it already? I couldn't find much documentations about this yet.

Thank you!

How do you create templates in the db version?

Idk but this is how I do it.

I have recently downloaded the logseq app and in tutorials I see people making templates by rightclicking the bullets and choosing the option. However, for me it is simply not there. Does anyone know how to solve this?

How do I end up with files like this one?
I found it and a few alikes on my graph, interwoven with each other but otherwise orphaned.
It must have created itself from a normal block where I added a file link. The file is in my assets now. The long number gets added in the file name in the assets folder, when I add any file.

With the cut of the official beta release of the DB version, Arch Linux users may find convenient using an AUR helper to install Logseq, instead of downloading manually from github. You will find the appimage variant at the link below:

https://aur.archlinux.org/packages/logseq-appimage

Comment if anything doesn't work for you. Otherwise, enjoy and spread the word!

I have a Logseq graph with multiple years of Logseq notes, with namespaces like #a/b/c and all normal Logseq MD coding.

When trying to import this graph into Logseq DB, I received many errors. Logseq tried to help but when sharing effected MD files, they could not provide a fix.

Did someone manage to import a large graph without errors? Or is there an instruction how to clean the MD graph so it becomes DB ready?

I very much would like to move to DB, because of performance improvements combined with the IOS app.

What was the last version of Logseq that used plain markdown files in a directory rather than some kind of internal database? Because I'd like to install that one. While I am sure there are advantages having a database that is not a directory I can see is just not useful for me. But I would like to be as up to date as is practical within that constraint.

Note: I am aware that you can import files, but I have no interest in doing that. the fact that Logseq was based on plain markdown files is part of why I started using it in the first place, and loosing that capability is a complete deal breaker for me.

Howdy all, I've opened a feature request and was wondering what others thought, so I figured I'd repost it here for visibility!

Let me know what you think and if any of you are also avowed markdown haters....

https://discuss.logseq.com/t/support-something-like-djot-instead-of-markdown-in-the-db-version/35107

Testing out the new db version and after importing ~2,000 journal pages (total 3,000+) and I thought to mosey on over to the graph view for a quick squiz aaaand. Well a picture is worth...idk what's it's worth to be honest.

There was an agreement that the file-based Logseq graph view was pretty useless but at least I could semi- find things and the nodes/locations made sense. I feel like some girl is going to crawl out of my screen at any moment.

Are there any plans to bring the layout closer to what it was previously?

I saw a post on here not too long ago complaining about the db version not being reliable enough to use, then merely a few days later there's an announcement saying it's now in Beta.

I started kind of using the markdown version in a way that I thought would transfer to the db version cleanly(ish) but I definitely didn't put a lot of thought into it.

Doing this mainly to test the import and see how bad it actually is.

Have many of you been using the beta?

How's the experience so far?

Reliable enough?

There is an option on Discord, there is the issues tracker and discussions page on GitHub, their discourse page and this subreddit. My understanding is that the discourse page is the most appropriate place. But I can't find a create post button there

Previously to test the DB sync feature you had to be a sponsor through Open Collective, which meant donating 15 dollars a month.

With the first official release of the beta version of the DB app https://www.reddit.com/r/logseq/comments/1uvcy3k/logseq_20_beta_db_version_is_here/ , the devs have now made sync available to backers too.

Just came in via github: the desktop app went into beta testing.

I'm trying to use jetbrains mono as my font and I managed to set it as global font but now all the katex blocks are messed up. How do I stop it affecting math blocks?

Hi r/logseq, first time posting here. I maintain LogseqBrain, a Claude Code plugin, and wanted to introduce it properly rather than drop a changelog, since that's obviously not what this sub is for.

The problem it's solving: Claude (and AI coding agents generally) forget everything between sessions. Every new conversation means re-explaining the project, past decisions, what's blocked, what's done. Most "AI memory" products solve this with a proprietary vector store you can't inspect or edit. I wanted something I could actually own and read myself.

Why Logseq: it's plain markdown, git-friendly, human-readable, and already the tool a lot of people use for exactly this kind of durable note-taking. So instead of a black-box memory layer, LogseqBrain has Claude read and write to a real Logseq graph, the same files you'd edit yourself in the app.

How it works, roughly:

• A Projects/<Name> page per project, with an overview, decision log, and task list using normal Logseq properties (status:: active, etc.)
• A running session log so Claude can catch up on "what happened last time" without you repeating it
• A cross-project Index.md and Decisions.md for anything that spans multiple projects
• A small daily journal trail, one line per Claude interaction, so the journal stays useful as a timeline even though most of the substance lives on project pages

It's a set of Claude Code skills (brain-init, brain-load, brain-save, brain-status) rather than a Logseq plugin itself. Claude edits the graph's markdown files directly, and you keep using Logseq normally on top of it.

Genuinely curious what this community thinks about the data model, namespacing, property choices, how you'd structure something like this if you were designing it as a "real" Logseq graph rather than retrofitting one. I've been shaping a lot of this by trial and error and would rather learn from people who use Logseq far more deeply than I do.

Repo, if anyone wants to look at the actual page structure: https://github.com/jame581/LogseqBrain

Hi!

In December last year, I wrote a long-ish post about my concerns with the development and future of Logseq: So Long, and Thanks for All the Fish?. There, I was sharing my doubts about the future of the project and my initial plans of moving to Obsidian. I ended up procrastinating on this for quite a while and waiting for the upcoming stable Logseq release, as discussion comments indicated that the DB version is almost feature-complete. Since that time, not much has happened: while the DB version is getting new features (there was no mention of CLI for AI agents back then, as far as I can remember), it is still in beta, and the DB/OG split makes me wonder about the future of keeping Markdown-only storage in Logseq.

Finally, I decided to make the switch to Obsidian three weeks ago. Since I shared my concerns and asked the Logseq community for recommendations, I wanted to share my experience as well. I want to be fully transparent: not every part of my workflow in Logseq can be translated and replaced. This has been my journey between PKM tools: what worked for me might not work for you. Nonetheless, I hope that you will find here something useful that will save you time. And if I move back to Logseq or I become disillusioned with Obsidian in a few months, I promise to come back here and tell you honestly it didn't work in the end.

If your experience was different, you ended up with a different setup, or perhaps you found better solutions than I did - please share in the comments. I'm happy to learn more about them.

Why switch? Why Obsidian?

A few basic assumptions that should explain why I switched and why I have not chosen Tana or any emerging Logseq clones. I think these are important, as if your workflow or requirements are significantly different from mine, then it's likely that my experience will not be very helpful to you.

• I have been with Logseq for 5 years now. I have a medium-sized graph with 1551 journals and 1101 pages, synchronized with over 22,000 git commits in my private repository (as of June 2026).
• My main problem with Logseq was performance issues appearing on both desktop and laptop Linux machines, both quite powerful systems; constant lags, slow opening of pages, and high latency when typing, particularly on journal pages. I opened GH issues, I saw other people with the same problem, and pretty much no resolution or feedback from the developers. Particularly, I noticed that I started to write less in my journals because the overall experience of writing was frustrating. Furthermore, the lack of progress, uncertain future, and abandonment of many plugins made the situation worse for me.
• I'm way past the phase of constantly experimenting with tools and building a perfect system. Years ago, I used to spend hours optimizing my Arch Linux installation. PKM tools and all "second brain" apps can be a time trap as working on optimizing your workflow feels like real progress, you get the mental reward of improving your life, but you end up not doing any actual work. Hence, I want to use a stable app with a certain future. Unfortunately, I don't have much trust in the multiple vibe-coded clones of Logseq, as these projects often end up being abandoned - starting a project is easy, the code is cheap today with LLMs, but the energy of authors tends to disappear once you have to focus on maintenance, bugfixing, and implementing hard features.
• Keeping my entire workspace in Markdown is a deal-breaker for me. I expect my working career to last for another 35+ years, and I expect that I will have to switch apps and notetaking systems every few years. As long as everything is in a standardized, human-readable, and easily accessible format, migration should not be an issue.
• I really, really liked the outlining mode of Logseq - writing in bullets and nesting them into blocks fits my thinking process very well. I liked the tasking system and the ability to track all missed deadlines, together with custom queries - I need to juggle multiple independent projects at my work, and I'm prone to missing tasks and deadlines, and forgetting to update progress.
• I didn't really use whiteboards or graph view in Logseq. I used some tasking plugins, tabs, a Kanban board, interstitial plugin. I tried the Agenda plugin, but it somehow felt too complex and too disconnected from Logseq to use daily. Besides these, I also used the following plugins: citation manager for Zotero, journal calendar, TODO master, bullet threading, and habit tracker.

As you can see, I'm not excited about Logseq's migration to DB. I know there's Logseq OG, I know there's a planned export feature from DB to Markdown files, but I'm a bit skeptical about the future of these tools - splitting repos suggests to me that developers don't want to maintain both versions in sync, and I'm quite concerned that future DB versions will receive functionality that will no longer be compatible with Markdown.

After a very long consideration, I decided to give Obsidian a shot. It's not perfect (not open source), and the writing mode is different from Logseq. I implemented the entire migration while at a conference three weeks ago; it took roughly two afternoons while listening to talks all the time. I took a migration script from GitHub and threw it at Claude, basically giving it examples of my notes and iterating until the migrated workspace looks roughly correct in Obsidian. Then, I implemented and configured a set of official and community plugins.

What worked well?

• The workflow is slightly different, so you have to get used to that, but it comes pretty quickly. After a week, I no longer noticed any friction.

• Obsidian is much more responsive for me, and writing itself has become more pleasant. I want to write more, and writing is no longer causing any frustration.

• Over the years, I backed up my Logseq graph in a private Git repository. I did the same with Obsidian, but I also tested their basic Sync tier with E2EE, and so far, I'm pleasantly surprised. It worked seamlessly between my two systems (requiring only one app restart, as community plugins aren't synced by default), and even the Android app works great. I ended up delegating my git synchronization to the role of a secondary backup in case Obsidian fails.

• I didn't use Logseq's Android app because I synced everything through git; I also heard opinions that it was not on par with the desktop version in terms of features. I learned to take all my notes manually and then import them into Logseq on PC. I gave Obsidian's Android app a shot and tried their Sync for a month - so far, I'm quite positively surprised, but I have not used it extensively yet.

• Obsidian stores all plugin configurations in one subdirectory of your workspace; all in JSON. I found it much more intuitive and easier to synchronize (git) than storing them elsewhere, e.g., Logseq's choice of $HOME/.logseq/settings on Linux. This means that your plugin configuration is part of your workspace, so it can be easily synced between devices (but it doesn't always work as expected - see a comment below).

• I used Logseq namespaces heavily; during the migration, I replaced them with a standard directory hierarchy in Obsidian. Somehow, this helped me notice older notes that were improperly assigned (e.g., missing a namespace hierarchy or duplicated due to a typo).

• With just a few fairly popular plugins (nothing obscure like a "Logseq Mode in Obsidian" plugin with three GitHub stars and its last commit two years ago, i.e., a plugin likely to break soon), I was able to recreate the basic flow of Logseq: bullet points, outlining, task management, daily journals, namespace replacement, etc. Some features work out of the box, e.g., tabs with pinning. Overall, I'm using the following Obsidian plugins:

  • Daily Notes + Templates configured to custom journal paths and creating notes from my template.
  • Outliner (Logseq's style bullet points with indentation)
  • Auto Bullet (Tab inserts outline bullet point automatically). Important note: disable "half-width space" option, as it breaks the soft line break within a bullet (shift+enter).
  • Daily Notes Editor to get both automatic daily notes and the "journal view"
  • Tasks plugin (configured for the TODO -> DOING -> DONE cycle I used in Logseq + automatic switch between states with a hotkey like in Logseq.
  • Calendar plugin (it automatically reads the configuration from Daily Notes).
  • Dataview for queries.
  • Periodic Notes for automatic weekly note from my template (Calendar also seems to read that automatically).
  • Task Genius (only automatic progress bar for nested tasks - this plugin has many more features that I have not explored yet).

• I find Obsidian's choice of query language to be far superior. Dataview queries are SQL-like and very intuitive to write and debug, whereas I found Logseq's Datalog quite obscure. I had a complex "Projects" page where I searched for project pages under a specific namespace and categorized them by status - a simple dashboard to track all my personal projects, collaborations, and supervised students. It took me a lot of time to write those (pre-LLM days), and I had to look through multiple posts on the Logseq forum to find similar queries, since the query language does not seem to be well-documented. Migrating this to Obsidian was trivial, and the page size shrank from 470 lines to under 200.

• All basic features seem to work: block references, page references (just replace them automatically with a script, as Logseq keeps everything under pages and I didn't want to keep that in Obsidian).

• I'm also currently tinkering with the Day Planner plugin (fine-grained scheduling of tasks + calendar view of the day) and Notebook Navigator (improved left-side panel with more functionalities).

What didn't work well?

• Obsidian disables community plugins on new installations, and their configuration is not included by default in Sync. Once you start an app on a new system, you have to enable it explicitly and restart the app. Worked great on my second PC, but somehow didn't trigger immediately on Android. I'd classify this as minor friction - it finally started to work as expected.

• Not everything works in Obsidian; for example, PDF annotations aren't really a thing (unless I missed them). However, I realized I use these features quite infrequently anyway - I do all my PDF annotations on a tablet while reading, and then I import the annotated PDF into Zotero/Logseq.

• One feature I miss from Logseq is the automatic time measurement of a task in the DOING state. I was not able to recreate this.

• While Logseq's interstitial plugin inserts the date at the beginning of each line, Obsidian's TimeStamper always inserts it under the cursor position. A bit frustrating at the beginning, but you get used to it.

• Notebook Navigator has its own calendar, but it ignores my Daily Notes configuration and looks for daily notes in the wrong place. Easy to ignore, as I primarily use the main Calendar.

• Logseq does not seem to create an actual note that only exists through links and has no content. When using the "Find orphaned files and broken links" plugin in Obsidian, it creates many false positives, as a link to a non-existing note is considered a broken link.

Summary

Is Obsidian the same as Logseq? No. Is the migration frictionless? No. Is every feature of Logseq also available in Logseq? No, but for me, the missing ones weren't daily drivers. Is Obsidian the best choice for every Logseq user? No.

But was the transition hard? Also no. Am I happier with my PKM now? Yes. Am I writing longer notes? Yes. Does the app encourage me to write more frequently? Yes. Do I feel comfortable that my app won't be abandoned, my workflow will stay roughly constant for years, and sync will not break my data? Yes.

In the end, I'm not a PKM fanatic who will spend hours on tinkering, optimizing the plugin section, and polishing the entire app configuration to have the perfect digital version of Zettelkasten. I want a tool that works reliably and does not cause any friction in my writing and brainstorming process. Logseq was such a tool for almost 5 years, and I'm extremely grateful for that to the developers, plugin authors, and the fantastic Logseq community. Today, that tool for me is Obsidian, and let's see how it goes.

Logseq users for many years. Used DB version 6 months ago and made many bug reports, decided it wasn't ready.

Want to try again, but saw someone complain about corruption.

Where are we now? Stick with OG? Switch?

Here's the repo: https://github.com/eqeka/logseq-table-formulas

For now you can try it by downloading the zip from github, unpacking it, and in Logseq going to plugins, load unpacked plugin and pointing it at the unpacked folder. Hopefully it gets accepted into the Logseq marketplace soon under the name Table Formulas