Multiple template folders

Feature requests
1

Use case

I share sub-folders from my vault with other people, and I’d like to be able to have shared templates with them too. This is however not possible because the template plugin can only read from a single location, making it hard for have one set of templates that are shared and another set that are unique to myself.

2

+1 I have the same use case. It would be great to have multiple template folders.

4

+1 for organizing templates

This is VERY interesting
How do you sort them: and are the values static or did you find a way to make them add ingredients when you alter the amount of persons to be cooked for?
Would love to know more about your setup. Maybe a use case in a dedicated forum thread?

5

Hi its a while ago and maybe you have a solution.
But when I read this my first idea was to use hard links or symlinks or so.
I haven’t tested it by myself. But as I know, with that you can “copy” afolder from place A to place B.
The difference is, that it is no copy. It is more like a mirror. All you are doing at place A is reflected at place B.

6

I see this working as a cascade where a list of candidate templates is built based on the location of the current working file.

Assuming that the name of the directory in which templates are stored is consistent, then it would be a case of drilling down from the vault root to the current working file and compiling the a list of templates from any that are met along the way.

For example:

[vault root]/
├── _tpls/
│   ├── tpl-a.md
│   └── tpl-b.md
├── foo/
│   ├── _tpls/
│   │   └── tpl-c.md
│   ├── bar/
│   │   └── bar-note.md
│   ├── bat/
│   │   ├── _tpls/
│   │   │   └── tpl-d.md
│   │   └── bat-note.md
│   └── foo-note.md
└── root-note.md

Choosing “Insert template” from:

  • root-note.md ⇒ tpl-a.md, tpl-b.md
  • foo-note.md ⇒ tpl-a.md, tpl-b.md, tpl-c.md
  • bar-note.md ⇒ tpl-a.md, tpl-b.md, tpl-c.md
  • bar-note.md ⇒ tpl-a.md, tpl-b.md, tpl-c.md, tpl-d.md

This is not a million miles from the “attachments” paradigm:

Screenshot 2026-05-09 at 03.02.32
Screenshot 2026-05-09 at 03.02.321426×366 34 KB

7

Resurrecting this because this seems like a no-brainer easy win for this otherwise surprisingly underpowered core plugin.

I have a unique proposal to add here, that I’d argue should be more broadly adopted: Obsidian has provided us “Bases”, which has proven to be a fantastic way of dynamically creating a collection of notes. As a third way of specifying templates, maybe one could provide a .base file which has querying logic that resolves to a list of notes that qualify as templates?

My use case:

Just to put it out there: I have a vault that has a “shared” folder which is a OneDrive-synced folder shared between my team, while the rest of my vault is personal to me. I’ve made templates that would be useful the share across the team, but I also have some that only are useful for my workflow.

This means there are logically two template folders, but it’s impossible to use both at the same time. I can copy templates from the shared one to my personal one, but I wouldn’t get any updates made to those shared templates.