Making Obsidian play nice with Logseq

This setting, as I understand it, only governs the keywords you cycle using the Ctrl/CMD+Enter shortcut.


That makes sense! Thank you.

1 Like

Hi all,
I am trying this integration with some success, but OneDrive complains about files with non-allowed characters in the file names, in the folder bak. In fact those (temporary?) files have colon, backslash etc in the name (e.g. Anybody else with the same problem? Is the folder bak for version control?
Thanks in advance

1 Like

If Logsec and Obsidian are working off the same files, how do you deal with the differences in the header styles – Logseq’s format for aliases (first block, alias “double colon”) versus Obsidian’s implementation of aliases in its metadata protocol (aliases: [], etc.)? Sorry if I missed this.


For things like aliases and block references, etc. you really have to pick which app is your main app and just use the other one without those features. The Logseq mobile app is imminent so I personally will be phasing out using Obsidian altogether… it was really just a stopgap to be able to access my files on mobile.


Thanks very much. My own hesitation in commiting to that approach is based on the good track record of the Obsidian developers, which gives me some confidence in the app’s continued development.


I would go WAY further with this suggestion, as I am running into major conflicts using the journaling feature in both Logseq and Obsidian and actually losing data through overwriting. Disable all plugins in Obsidian, except the ones urgently necessary. @Luhmann, your suggestion to complement LogSeq with Obsidian plugins, such as Readwise is brilliant, as usual :star_struck:.

1 Like

Those are my thoughts, sometimes. But I consider it less and less likely. LogSeq is still awaiting its mass onboarding as I see it. Obsidian is in full swing, so not really comparable. Another aspect is loading speed, but this will improve over time. One of the most enticing aspects of Logseq is a clean UI, especially for outlining. Obsidian is really ugly in this department. Add in the Roam- like link behavior and you are one happy LogSeq customer :grin:


I’m having heading styling issues with Obsidian when using indented children like is done with Logseq. These bulleted headings aren’t showing as headings. The hashtags are still visible:
Screen Shot 2021-12-05 at 2.21.48 pm

Does anybody know a way around this?

Figured it out. Using the CodeMirror Options plugin, Enable OpenMD Mode needs to be toggled on.

1 Like

Is there a fix for this?

I often note today’s date in Logseq using /today.Things work fine in logseq, but on Obsidian I get ‘nott created yet’ error.

My daily notes format is the same as logseq (YYYY_MM_DD). I

Yes, I use daily notes both in Logseq in Obsidian
In Logseq I have

 :journal/page-title-format "yyyy-MM-dd"
 :journal/file-name-format "yyyy-MM-dd"
 :date-formatter "yyyy-MM-dd"

Logseq has a settings how the date is rendered and how the journal file is named, it should be the same to work with Obsidian ( by default this might be different in Logseq, I dont remember)

check if your journal plugin is looking for the notes in the right folder (should be “journals” )


Thanks for the tips.

I have used Obsidian for the past two years and find it an excellent tool. Logseq’s block referencing and its ability to update blocks (in real time while they are being viewed), I find very powerful for my Zettelkasten.

I have found a few portability issues though

1. Block references don’t play well in Obsidian

I use block references heavily and Obsidian does not recognise them so, for example it will display a block reference as ((1e514c8c-a6d4-4589-8369-91c68b6e805b)) in the Obsidian Editor.

So until Obsidian can render logseq block references correctly I would only use Logseq (Desktop or Mobile) to view Logseq graphs (vaults). If you don’t use block references and only page links then Obsidian does a pretty good job of rendering Logseq pages

2. Page embeds show the {{ embed and }}

But the Page Links in the page embed do work

3. Logbook blocks are displayed

For example, Obsidian shows

  CLOCK: [2022-02-22 Tue 20:23:43]
  CLOCK: [2022-02-22 Tue 20:36:19]

rather than suppressing it on the Obsidian Preview mode

4. QUERIES do not work

No surprise here

There is an obsidian plugin which I am closely monitoring at which is starting to develop logseq compatibility within Obsidian. Over time this could be a very useful plugin.

Allan @ adxsoft


This is great!

What is the purposes of the ‘Tasks’ step where you create a page called [[logseq tasks]]? I don’t quite follow why we need to do this.

This is a way to find Logseq tasks in Obsidian. I no longer use this workflow since there is now a Logseq mobile app.

Thanks for the reply, I just downloaded the logseq app which is great! So won’t need this either. May be worth editing the original post so other users are aware of the app.

I have the same problem.How did you solve it? Change the cdn setting back?

Same here. I didnt get what was that query for. I am using tasks plug-in in ob at the moment. Unsurprisingly, it doesnt work with logseq

I finally figured out one of the display issues I had when Obsidian read my Logseq files. The way indents and spaces are handled differently was causing ugly displays in Obsidian. I couldn’t figure out why I wasn’t getting the standard bullets and only seeing dashes. That kept me from really using Obsidian. I fixed my template and now they look just as nice in Obsidian as they do in Logseq. This may have been obvious, but I couldn’t figure it out.

I have a daily notes template that looks like this:

  template:: daily-journal-template
  template-including-parent:: false
	- #### General & Planning
		- What do I want to get accomplished today and this week?
		  collapsed:: true
	- #### Meetings
		- Meetings for today
	- #### Tasks

So I changed to this:

## Daily Notes

#### General & Planning
   - What do I want to get accomplished today and this week?

### Meetings
   - Meetings for today	

### Tasks

Note that those leading spaces are actually tabs. So changing them to 3 spaces instead of tabs makes both programs display them correctly with bullet points not dashes.

I hope this helps someone else that missed this feature.

1 Like