Obsidian/Q/Is there a VS Code extension that helps obsidian users have an obsidian-compatible view of obsidian markdown files and navigate between wiki links?
Is there a VSCode/Extension that helps obsidian users have an obsidian-compatible view of obsidian markdown files and navigate between wiki links?
My Notes
- “Obsidian-compatible” here means wiki-style
[[links]], optional backlinks/embeds, and navigating notes on disk like a vault—not pixel-perfect Obsidian UI.
Answer
- AI/Response
- Yes. Several VSCode/Extensions add Obsidian-like wikilinks, navigation (go to definition / Ctrl/Cmd+click), autocomplete on
[[, and sometimes backlinks or embeds. None fully replicate Obsidian’s reading view, but many teams combine one of these with the built-in Markdown preview (VSCode/Command/Markdown/Open Preview / preview to the side). Strong general options
- Foam (repo) — Large install base; wikilink completion, go to definition, peek references, graph, daily notes, optional link reference definitions for standard Markdown compatibility, and navigation in the Markdown preview (per marketplace/docs). Good default if you want an Obsidian-adjacent workspace inside VS Code.
- Markdown Notes (repo) — Longstanding
[[wiki-links]], backlinks panel, peek/go to definition, autocomplete, piped links; explicitly aimed at Obsidian/Roam-style workflows. - WikiLens (repo) — Roam/Obsidian-like UX: page-centric explorer, backlinks,
![[embeds]], daily pages. Check repo activity if you care about ongoing maintenance.
Obsidian-branded or narrow extensions
- Obsidian Navigation — Click/hover to open linked
.md files for [[FileName]] in the editor; marketplace notes Markdown preview pane link navigation is not implemented yet (planned). - obsidian-vscode-extension — Click wikilinks, create missing notes,
[[ completion, hover shows linked file content (smaller extension by install count).
Commercial / fuller “vault in VS Code”
- AS Notes — Wikilinks, backlinks, rename propagation; claims Markdown preview resolves nested wikilinks for navigation-style reading (verify in trial against your vault layout).
Caveats
- Vault layout matters: Obsidian often uses flat or folder notes with unique names; some extensions assume unique filenames vs path-relative wikilinks—match extension settings to how your vault is stored.
- Preview vs editor: Built-in preview follows standard Markdown; wikilink clicking in preview is extension-dependent (Foam documents preview navigation; Obsidian Navigation explicitly does not yet).
Sources