Frontmatter Markdown Links
Michael Naumov21k downloadsAdds support for markdown links in frontmatter.
- Overview
- Scorecard
- Updates116
Obsidian treats a property whose whole value is one link, [[wikilink]] or [text](note.md), as a real link. But put several links in one value, such as "[[Chapter one]] and [Chapter two](<Chapter two.md>)", and Obsidian draws the whole value as one broken link: none of the links in it resolves, opens or counts as a backlink. And while you edit in Source mode, no link in the frontmatter is clickable at all.
This plugin makes every link in frontmatter a real link — each link in a multi-link value on its own, wikilinks and markdown links alike, clickable in Source mode, Live Preview and Reading, resolvable, and counted as a backlink on its target.
Long-requested on the Obsidian forum, for both internal and external links.
More screenshots
Demo vault
The documentation is a demo vault. Every feature has a note that explains what it does and why you would want it — and whose own properties are the demonstration.
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:
- Running the
Frontmatter Markdown Links: Open demo vault command. - Downloading
frontmatter-markdown-links-demo-vault.zipfrom the Releases. It unzips into a singlefrontmatter-markdown-links-demo-vault-<version>folder. - Browsing its source in
demo-vault/in this repository.
What it does
- Several links in one property become separate real links, and every frontmatter link is clickable in Source mode too — with paths that contain spaces working either percent-encoded or in angle brackets, and embeds supported too. 01 Frontmatter markdown links
- They count as backlinks, so a note linked only from inside a multi-link property still shows up on its target. 02 Backlinks
- Settings, including how much of this you want. 03 Settings
Renames
On a rename, Obsidian itself updates a property whose whole value is one link, markdown or wiki, and each link of a list property. Inside a value holding several links, Obsidian's own update would leave a wikilink pointing at the old name and could write the new name into a different markdown link, so this plugin steers that update to the renamed link alone and leaves the rest of the value as you wrote it. Up to version 2 this plugin handled renames itself. Since 3.0.0 it does not, and rename and delete handling belongs to Advanced Rename and Delete Handler instead — one plugin owning it for the whole vault, rather than a copy inside each plugin that happened to need it.
This plugin offers to install it, once, and carries your old Should handle renames value over for you to approve. Declining costs you nothing else: every feature above keeps working.
See also
| Plugin | Features | How Frontmatter Markdown Links differs |
|---|---|---|
Frontmatter Link Repair |
Finds unquoted frontmatter wikilinks; previewed file rewrites | Complementary repair: makes existing links work without rewriting note text |
Frontmatter Links |
Archived/unlisted; renders frontmatter links | Broader link support: splits multi-link values; resolves each target and counts backlinks |
Last searched for similar plugins on 2026-10-26.
Installation
The plugin is available in the official Community Plugins repository.
Beta versions
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:
- Ensure you have the BRAT plugin installed and enabled.
- Click Install via BRAT.
- An Obsidian pop-up window should appear. In the window, click the
Add pluginbutton once and wait a few seconds for the plugin to install.
Debugging
By default, debug messages for this plugin (id: frontmatter-markdown-links) are hidden.
If you need to enable them refer to the documentation.
Changelog
All notable changes to this project will be documented in the CHANGELOG.
Contributing
Contributions are welcome — see CONTRIBUTING to get set up.
Support
Filing an issue (for AI agents and humans)
Open issues through the issue forms, not as blank issues.
To report a bug from inside Obsidian, run the Frontmatter Markdown Links: 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.