Steps to reproduce
- Create a new note in Obsidian.
- Add headers to the note, for example:
# Header 1
Text under Header 1.
## Subheader 1.1
Text under Subheader 1.1.
## Subheader 1.2
Text under Subheader 1.2.
# Header 2
Text under Header 2.
- At the top of the note, create a table of contents using standard Markdown links to these headers, assuming conventional slugified IDs:
## Table of Contents
- [Header 1](#header-1)
- [Subheader 1.1](#subheader-11)
- [Subheader 1.2](#subheader-12)
- [Header 2](#header-2)
- Switch to Reading View and try clicking on these links to navigate to the corresponding headers.
Did you follow the troubleshooting guide? [Y/N]
Y
Expected result
Clicking on the links in the table of contents (e.g., [Header 1](#header-1)) should navigate to the respective headers within the same note. This is the standard behavior in many Markdown renderers, where headers are automatically assigned slugified IDs (e.g., “header-1” for “Header 1”) based on their text.
Actual result
The standard Markdown links do not work; clicking on them does not navigate to the headers. Instead, to link to headers within the same note in Obsidian, you must use the proprietary syntax [[#Header Text]], such as:
## Table of Contents
- [[#Header 1]]
- [[#Subheader 1.1]]
- [[#Subheader 1.2]]
- [[#Header 2]]
Only this Obsidian-specific syntax successfully navigates to the corresponding headers.
Environment
SYSTEM INFO:
Obsidian version: v1.8.7
Installer version: v1.7.7
Operating system: Windows 10 Pro 10.0.19045
Login status: not logged in
Language: ru
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on
RECOMMENDATIONS:
none
Additional information
This lack of support for standard Markdown anchor links (using slugified IDs like #header-1) affects the portability of Obsidian notes to other Markdown-based platforms, such as GitHub or static site generators, where the conventional syntax is widely supported and expected. For example, a note written in Obsidian using [[#Header 1]] will not link correctly when viewed in another Markdown renderer that relies on standard anchor links, and vice versa. Supporting both the standard Markdown anchor link convention (e.g., [Header 1](#header-1)) and Obsidian’s proprietary syntax would improve compatibility and ease of use across different tools.
