Michael Naumov4k downloadsShows the backlink's full path in the backlinks panel.
Obsidian's Backlinks pane lists each backlink by note name alone. If you keep a Meeting note in three different project folders — which is the natural way to organize them — the pane shows three identical rows and no way to tell which is which without opening each one.
This plugin shows each backlink's full path instead, so the list identifies its notes.
The documentation is a demo vault. Every feature has a note that explains what it does and why you would want it, with three same-named notes already in place so the ambiguity is in front of you.
Start reading here — it is plain markdown, so it works on GitHub with nothing installed.
A copy of the vault ships with every release. You can access it via any of the following:
Backlink Full Path: Open demo vault command.backlink-full-path-demo-vault.zip from the Releases. It unzips into a single backlink-full-path-demo-vault-<version> folder.demo-vault/ in this repository.| Plugin | Features | How Backlink Full Path differs |
|---|---|---|
Context Titles |
Folder context for duplicate names in the graph | Same disambiguation goal; targets the Backlinks pane |
Hierarchical Backlinks |
Separate backlink view; folder tree | Same path-context goal; keeps the core Backlinks pane and adds paths to rows |
Tab File Path |
File paths in tabs | Same path-display goal; targets the Backlinks pane |
Unique Tab Labels |
Parent-folder prefixes on tab labels | Same disambiguation goal; targets the Backlinks pane |
Last searched for similar plugins on 2026-10-26.
The plugin is available in the official Community Plugins repository.
To install the latest beta release of this plugin (regardless if it is available in the official Community Plugins repository or not), follow these steps:
Add plugin button once and wait a few seconds for the plugin to install.By default, debug messages for this plugin (id: backlink-full-path) are hidden.
If you need to enable them refer to the documentation.
All notable changes to this project will be documented in the CHANGELOG.
Contributions are welcome — see CONTRIBUTING to get set up.
Open issues through the issue forms, not as blank issues.
To report a bug from inside Obsidian, run the Backlink Full Path: Report a bug command. It opens the bug form with the plugin version, the Obsidian version and your operating system already filled in.
Filing from the CLI or the API (gh issue create --body, or an AI agent filing for you) skips the form, and gh issue create --template cannot load an issue form. In that case, open the matching form in .github/ISSUE_TEMPLATE/, copy every field as a ### <label> heading in the form's order, and fill in each one. Always state the plugin version, the Obsidian version and your operating system.