How to use Obsidian and Logseq together and why a Markdown backend matters

The core idea is to run Logseq and Obsidian side by side without locking your notes into a single app—by making both tools write to the same Markdown files on the same local folder, then syncing that folder with Git. That setup means edits in one system instantly appear in the other, while Markdown keeps the notes readable for decades across many editors and platforms.

Logseq and Obsidian serve different writing styles. Obsidian is favored for long-form documents such as scripts, presentation notes, and training material. Logseq is favored for its block-based workflow, especially when pulling together many separate notes into one page. Keeping both tools in the same “digital brain” avoids forcing everything into a single interface.

To make them work together cleanly, the transcript highlights a few specific configuration steps. In Obsidian, the settings path goes to Files and Links, where the “default location for new notes” is set to the same folder Logseq uses—specifically the “pages” folder. It also recommends installing the community plugin “Daily Notes” in Obsidian, then matching Logseq’s date format (year-month-day) and storing those daily notes in the “journals” folder. With those aligned, most of the day-to-day functionality comes from just those settings.

The reason the integration holds up over time is that both apps use Markdown text files as a backend. Logseq writes to a local folder, and Obsidian reads and writes to the same folder, so changes stay synchronized. The workflow then extends beyond the local machine by using Git to sync the Markdown folder to the internet. That lets the same notes be accessed remotely through Logseq’s web browser on a phone or laptop, with the setup remaining consistent across devices.

Markdown is treated as the long-term insurance policy. Because Markdown is plain text, it can be read and edited by many tools—ranging from modern note apps to older editors like Vim and even basic Windows Notepad. The transcript cites Markdown’s longevity (developed in 2004) and emphasizes that text-based notes remain portable even if a specific app disappears.

That portability becomes especially important when comparing against cloud-first services like Notion. Notion can export data to Markdown and CSV, but the risk is losing access if the service becomes unavailable or an account gets locked. The transcript’s backup guidance is practical: for Markdown-based notes, store the files in a synced location (Dropbox, OneDrive, Google Drive, iCloud) or use Git for version history. For Todoist, backups require manual action—Todoist provides a daily backup file in settings that can be downloaded, so the advice is to automate it with a recurring task. For Notion, the advice is to export the correct top-level page (and include subpages and attachments), then store that export as an offsite backup.

Overall, the approach is less about fear of companies vanishing and more about reducing the damage from mistakes, account blocks, or support delays—so the notes remain recoverable even when something goes wrong.