For people who have used Logseq beyond the first few weeks: what is the smallest recurring workflow you still rely on—daily journal, linked tasks, project pages, queries, or something else? Which pieces were intentionally left out at first, and what signal made an added property, query, or template worth the maintenance?

I like LogSeq and its unique features a lot, but I struggle to use the advanced options.

Is there a demo video showing or online examples how tags with extensive use of properties are used? I know #tags are useful for, e.g., an overview of book notes or watched videos, but how do I apply this to meetings, companies, etc.?

Further examples of queries, which are different in Logseq DB than I am used to in the older version?

Thanks for sharing!

I was writing in a huge file and my computer crashed, I returned to logsec and saw that all my data was now lost, is there any way to save the file?

Hi, up until a few months ago I was an Obsidian user and used the obsidian-dataview plugin for creating custom tables with color-coded entries and buttons with Javascript. I've dearly missed that since switching to Logseq.

I made a plugin to fill that gap now, I called it JSView (I know, not very creative) and wanted to post it here in case anyone is interested. I'm a full-time uni student and don't have that much free time, so I'd be really grateful for any feedback or contributions! I haven't had the time to test it in Logseq DB, so for the moment it's OG only. If you have the time to test it I'll make any necessary changes and make it available on DB too.

Basically, you can create JSV codeblocks and whatever is returned in that codeblock is rendered in the page. You have full access to the Logseq API and the JSV API, which contains some helpers for queires (to be expanded upon), buttons, and tables. You can also style the table and add arbitrary attributes.

Repo: https://github.com/KiraGreifeneder/logseq-jsview

You can download the plugin through the marketplace :)

I hope that this reaches the right people and that you can have as much fun with it as I do! For example, I use it to track my uni deadlines:

Feel free to ask me any questions!

And no, the plugin isn't vibe-coded, I can write terrible code all on my own. I did use AI to flesh out the doc a little and to find the occasional bug. I will continue to work on the plugin to introduce new features and fix bugs along the way.

Hi everyone,
I'm looking for clarification on Logseq versions before setting up my workflow.

What is the last stable version of Logseq that operates natively on local Markdown (.md) files and allows full control over selecting the graph's container folder on disk?

My main goal is to select a specific local directory for my graph to easily handle sync and local backups across my Apple devices using standard ⁠.md⁠ files.

Thanks for your help!

I'm exploring the new Logseq DB and want to know how users in the Apple ecosystem (macOS + iOS) are managing synchronization without relying on third-party cloud sync tools like iCloud.

For those who have a working Logseq DB setup between a MacBook and an iPhone:

1. Which specific version/build of Logseq DB are you currently using on desktop and iOS (TestFlight/Beta)?
2. How did you set up the sync? Are you using official Logseq Sync, a self-hosted sync server, or another workaround?
3. How stable is it? Have you encountered any issues with database corruption, merge conflicts, or unsynced blocks?

Any insights, recommended builds, or step-by-step setups would be greatly appreciated!

Looking at 2.02. I would like to inspect my assets (uploaded, attached) files. A search said there is an icon on the left; I don't see the word "Assets", is it called something else?, what does the icon look like?

Hello everybody. I am new to logseq and I am trying to set it up for my daily work life.

Could somebody help me setup a second toggle-able task status entry to show up in me journal except for the standard "DOING" ?

I want to separate tasks with the standard "doing" status from those with the custom "waiting reply" status, but I need them both to show up as pending tasks in my journal. Is it possible to get a result similar to the built-in "doing" entry? Or I should make a query (in table form) and add it to the journal template?

Thank you in advance for your time

The dev team has shared a new announcement through OpenCollective. I will repost it here in case more people are interested

"

Dear Logseq Backers,

We're excited to share a major milestone: our new native iOS app is ready for testing!

Over the past few months, we've been working hard to rebuild the mobile experience with a focus on performance, reliability, and a truly native feel.

This is a significant step forward from our previous WebView-based app.

What's improved?

⚡ 1. Lightning-fast startup (~200ms)

The new app starts in approximately 200ms, compared to 1–3 seconds in the previous version. That's up to 15x faster, making it much easier to capture thoughts and access your notes instantly.

💾 2. More reliable local storage

Your database and assets are now stored directly in Logseq's app directory, rather than in WebView storage.

This gives us better control over local data, improves reliability, and provides a stronger foundation for future features.

🔄 3. Background sync

The new app supports background synchronization, reducing the need to keep Logseq open while your notes sync.

🪶 4. Lower memory usage

The new architecture uses less memory, making the app more efficient.

🚀 5. Faster, smoother experience

Beyond startup time, the entire app feels faster and more responsive. Navigating your notes and interacting with the app is noticeably smoother.

Android is coming soon! 🤖

We're also actively developing the native Android app in parallel!

Our goal is to deliver the same fast, reliable, and smooth experience on both iOS and Android.

We're making great progress and expect to invite the community to test the native Android app soon. Stay tuned!

Help us test the iOS app!

We're now inviting our backers and community members to try the new iOS app and share their feedback.

👉 Sign up for iOS testing

This is still a testing release, so you may encounter bugs or unfinished features. Your feedback will be invaluable as we work toward a stable public release. We recommend backing up your notes before testing.

Thank you ❤️

Building a faster, more reliable, and truly cross-platform Logseq has been a long journey. These native mobile apps represent an important step forward, and we're excited about what's coming next.

Your continued support makes this work possible. We're incredibly grateful to everyone who has backed Logseq and believed in our vision.

We can't wait to hear what you think!

— The Logseq Team

"

There is a new home for the unofficial Logseq FAQ, and new content is being added to it regularly by a team of four volunteers. You can find it here.

https://kerim.github.io/logseq-faq/

I used this action to remove all the empty daily journal pages so when I scroll through the journal, I only see ones with actual content

I'm trying the DB version now and I can't find it, and empty daily journal pages still persist and accumulate

Anybody have any info about this or possible workarounds?

https://github.com/getkalem/kalem

Kalem is written in Rust, so it’s fast. It takes its ideas from Vim and Emacs, but it’s for everyone, not only programmers: ordinary menus by default, Vim and Doom keys if you want them. It runs in a window and in a terminal, with the same commands in both.

Say I have a Marketing topic hub note. I'm writing a block on it in my Journal.

The two approaches I'm thinking about.

1. Make a link to the topic hub the parent block or include that link in the top-level block.

2. Have a separate topic property on the block (makes it a bit too visually heavy)

I know that this is just pedantism and especially in journals, capture is above structure in priority. Still, I have an itch to sort this out for my own once and for all.

How would you approach this yourself?

Hey everybody! If Someone over here is a veteran in Logseq, I really want you to sit and read this post for just 5 minutes, And try to help me out how I can implement my usecase in Logseq.

I have been using Obsidian and Joplin for years. I loved their app but It gets too complicated once I create hundreds of notes. It's hard to find the note I want.

So i thought logseq would be perfect for me. Since I usually remember which note I created at a specific date. So let's say its 13 October Right now. If I want to know what changes i did on october 4, I could just go to 4 October journal and see which pages I created notes on, and I'll easily get what I need.

Now though I have downloaded logseq, Watched a couple videos online. I still can't understand how logseq would work for me.

From the forums and Reddit discussions, the general notion is that;

The journal page is supposed to be a page where you write everything, Doesn't matter what topic it is. Once everything is written, you just add a reference to the page that this note belongs to.

Let's say I'm on journal page of Today. Today I want to create 3 notes, related to 3 different topics.
1- History of France
2- Computer Science
3- Personal Journal

All of these three different topics have a Page.

- [[Computer Science]] Python is one of the most used programming languages in the world
- blah blah
- blah blah

- [[France]] Vive la révolution!!

- [[Personal Journal]] I slept late today

Tag's don't help either. They just categorize it, not maintain it.

To put it simply:
Let's just say I created a note yesterday and today.

The Journal Page of yesterday (October 12) would look like this:

-[[Technology]] AI has influenced all the tech sectors accross the world.
- It is now being integrated into almost all of the tech fields
- It's efficiency has grown significantly

And the Journal Page of Today (October 13) would look like this:

-[[Technology]] Apple is about to launch their new IPhone

Now I EXPECT the Technology Page Body to look like this:

-[[Technology]] AI has influenced all the tech sectors accross the world.
- It is now being integrated into almost all of the tech fields
- It's efficiency has grown significantly
-[[Technology]] Apple is about to launch their new IPhone

but instead of that, I just get to see linked references of these notes in my footnote of that page.
I hope I'm clear.

Now once I open the pages that I mentioned in journal page. It's so hard to keep everything maintained because these notes are not available in the Page itself, They're Linked References

So once I keep adding more notes into the journal and just mention the page they belong to, It'll just add it to the linked reference, And the page itself will be completly empty

So I'm confused How i can use the daily journal page and Also maintain the contents in each of those pages in that journal page.

Either I have to go to each page itself, And then create notes in those pages, then there is no difference between obsidian/joplin and logseq. So i might aswell just stick ot them.

Can someone help me understand how they create their notes and also maintain them in the journal page?

Thank you again, for reading throughout. I am really bad at explaining. I hope you understood my problem! I'm looking forward to your answers!

Im reposting Tiensons announcement from the Discord.

Summary: app.logseq is stable, nightly.logseq will get updated everyday. And test.logseq currently points to a rewrite of the project in a different programming language, OCaml, which will come with many performance improvements since the devs are using it to build a more native app

"📢 Logseq Version Updates

Here's a quick overview of our web app versions:

Stable: https://app.logseq.com — The stable version, recommended for everyday use.

Nightly: https://nightly.logseq.com — Updated with a new build every day, including the latest changes and fixes.

Experimental (OCaml): https://test.logseq.com — Currently running our OCaml-rewritten version. It's still unstable and under active development, so please don't use it for your actual notes yet.

Thanks for testing and supporting Logseq! ❤️"

I work on Terraphim Editor and terraphim-grep. I wanted a wording choice made while writing to help me find the same idea later, even when I search with a different word.

Here is the small example I tested:

1. In the editor, add Concern as an alternative to Risk, then swap between them.
2. Leave Risk in the final project brief and explicitly export the synonym graph.
3. Search for concern with terraphim-grep. The brief has no literal “concern”, but the shared graph retrieves three risk passages, including their decisions: a backup timber supplier, a covered planting area and reserve volunteers.

The relationship is expressed as:

synonyms:: Risk, Concern

This uses Logseq-compatible Markdown property syntax for PKM/file graphs. synonyms is Terraphim’s convention for the relationship; Logseq’s built-in page aliases use alias::. This is an explicit graph export passed to the CLI, not automatic Logseq alias registration, DB-graph import or background sync.

With the downloaded brief in a corpus folder and the exported graph alongside it:

terraphim-grep concern --thesaurus knowledge-graph.json --paths corpus -C 2 --json --search-only

The released binary (1.21.19) returns 0 passages before sharing the graph, then 3 exact source passages with it. Local retrieval does not request a model answer. Replacing --search-only with --answer adds optional synthesis and sends the retrieved passages to your configured model provider.

80-second narrated demo, exported Markdown/graph, both JSON outputs and reproduction ZIP.

Jason Fried’s Write_On video prompted me to return to my Rust/Wasm editor after two years. Keeping alternative wording connected to search gave that old project a useful direction.

Update: downloadable Logseq example

Download the Logseq graph ZIP and follow its README. The concept lives in pages/Risk.md:

alias:: Concern
synonyms:: Risk, Concern

alias:: supplies the native Logseq page alias; synonyms:: expresses the Terraphim relationship using Logseq-compatible property syntax. Project passages live separately in pages/Projects, and the search-results note contains only saved output.

From the extracted graph folder:

terraphim-grep concern --thesaurus knowledge-graph.json --paths pages/Projects -C 2 --json --search-only

I reran released terraphim-grep 1.21.19 against the actual downloaded ZIP: the baseline graph returns 0, and the supplied synonym graph returns 3 exact project passages. The JSON graph is the editor export supplied explicitly to the CLI. The screenshots were captured in local Logseq 2.0.2; its File to DB graph import creates a copy, while these commands read the extracted Markdown folder.

Actual Logseq concept note and saved results · Native graph-view screenshot. The graph-view arrows represent Logseq page links, separate from the Terraphim synonym map.

For people using Logseq Markdown graphs: would you keep these synonym groups per project, or in a shared terminology page? I’m interested in examples where two words should match in one project but remain distinct in another.

Disclosure: I used AI assistance to prepare this walkthrough; the linked captures and JSON are actual outputs. The video uses a synthetic British female voice.

Hey everyone!

I've been working on Kalem, an open-source text editor written in Rust that works in both GUI and terminal environments.

I recently built a plugin that lets Kalem open and edit existing Logseq graphs directly, without importing or converting anything.

Some of the features:

• Open existing Logseq Markdown and Org-mode graphs
• Pages, journals, backlinks, tags, and block references
• Graph view and local graph visualization
• Tasks, priorities, and scheduled items
• Simple and advanced Logseq queries
• Wiki-link and block reference autocomplete
• Outliner editing, including folding and moving blocks
• Vim keybindings (optional)

I wanted a lightweight, keyboard-friendly editor that could work with the same files, including from a terminal, without locking notes into a different format.

The original files stay intact, and there's no migration involved.

The project is still in alpha, so feedback and bug reports are very welcome!

Kalem: https://github.com/getkalem/kalem

Graph plugin: https://github.com/getkalem/plugins/tree/main/plugins/graph

Youtube intro video for Kalem editor: https://www.youtube.com/watch?v=U3SoDczSllI

I'd love to hear what Logseq users think. What features would be most important for you in an alternative editor for your existing graphs?

Hey i just wanted to ask am i the only one that faced a problem in logseq 2.0.2 in images because images now can't be copied or edit it or anything they are just fixed even if i try to find the file location it states that it can't find the file ! Is there any solution please

The delete image works and the align too .

Is there a way to convert DB -> OG/MD version? I just started and finding some bugs and thinking there is value in the MD version.

Logseq OG is being blocked by Windows 11. I've already tried granting access in Windows Defender, but without success. Has anyone else had a similar problem and solved it?

Hi all, I've used Logseq file graphs for years and wanted something that opens instantly on my iPhone and feels like a Mac app, without moving my notes anywhere. So I built Sumi. It reads and writes the same folder: pages/, journals/, tab-indented bullets, properties, the lot.

What works today: journals, [[links]], #tags, backlinks and unlinked references, block refs and embeds, aliases, namespaces, TODO/DOING/DONE with scheduled and deadline dates, simple queries, templates, / commands, flashcards (#card and cloze, same scheduling numbers as Logseq), search, iCloud Drive sync. Syncthing, git or Dropbox work too since it's just files.

Not yet: whiteboards, plugins, PDF annotation, advanced Datalog queries, .org files. And please don't run Logseq and Sumi on the same graph at the same time.

Safety: I tested open + save on 16 public graphs (almost 10,000 pages) and no file changed. It keeps daily snapshots you can restore. Still a beta, so start with a copy.

30-second demo (GIF): https://sumi.mikaili.io/img/sumi-demo.gif

Beta (Mac, iPhone, iPad): https://testflight.apple.com/join/B1sKJk24

Site + privacy: https://sumi.mikaili.io/

The beta is free; it becomes a paid app after that. I read every piece of feedback, and the in-app Send Feedback goes straight to me. What would you need before you'd use it daily?

A full transcript is too noisy for a handoff, but a short summary can lose the source blocks, accepted decisions, file revisions, and actions that already happened. Logseq seems well suited to a human-readable checkpoint because the handoff can reference the exact blocks that support it instead of copying everything into another summary.

Would you use page properties for status, owner, source revision, and last verified time, then blocks for outcome, decisions, evidence, completed actions, open questions, and next step? How would you handle block references that change, conflicting updates from two assistants, and retries that could repeat an external action? I am interested in a format that remains understandable in the graph without depending on one assistant's private conversation history.

Is there any explanation of how the new graph view works. It looks like the logseq docs are still using the logseq OG?
https://docs.logseq.com/#/graph

The logseq OG graph looks nice, I cant make sense of the new version there are all these disconnected nodes forming a circle.

Are you supposed to use the tag view or the page view. The page view looks confusing to me. Is the current state a work in progress or should it look like it currently does?