Vaultorial
English

Templater vs Core Templates in Obsidian: Which One You Need

Obsidian has two ways to stamp out repeatable notes: the core Templates plugin that ships with the app, and Templater, a community plugin that replaces it for people who hit its limits. They solve the same problem at different depths, and choosing wrong costs you either missing features or pointless complexity. This guide draws the line between them, shows working Templater code, and doubles as the install manual for every template on this site — each one declares which of the two it expects.

Core Templates: what Obsidian includes out of the box

The core Templates plugin does one thing: paste the contents of a template file into the current note. You point it at a folder (Settings → Core plugins → Templates), put skeleton notes in that folder, and trigger Insert template from the command palette or a hotkey.

It substitutes exactly three variables: {{title}} for the note's name, {{date}} and {{time}}, with optional format strings like {{date:YYYY-MM-DD}}. The same tokens work in the core Daily notes plugin, which fills its template automatically when it creates today's note. That combination — fixed structure plus today's date — covers more use cases than it sounds: meeting skeletons, journal pages, recipe cards, character sheets.

What it cannot do: compute anything. No yesterday or tomorrow, no dates derived from the note's title, no prompts, no conditional content. The moment a template needs to know more than the current moment, you have outgrown it.

What Templater adds to Obsidian

Templater is a community plugin (by SilentVoid13, installable from Settings → Community plugins) with its own command syntax inside <% %> markers. Where core Templates pastes static text, Templater executes commands at insert time and writes the results into the note.

The practically useful additions, in rough order of how often they matter:

  • Date arithmetic — yesterday, next Monday, the start of the week a note belongs to.
  • Dates parsed from the file name, so a note works no matter when you create it.
  • Prompts and file operations: ask for a value, rename or move the note, insert another file.
  • Folder templates: auto-apply a template whenever a note is created in a given folder.
  • Full JavaScript for whatever the built-ins do not cover.

That last bullet carries a warning worth taking seriously: Templater can run arbitrary code. Install it from Obsidian's official plugin directory only, and read any template you did not write before inserting it. Our zips contain plain Markdown and JSON settings — the Templater commands in them are inert text until you install the plugin and insert the template yourself.

Obsidian Templater examples you can copy

These are real excerpts from templates in our vaults, not toy snippets. Paste them into a template file and adjust the formats.

A daily note dated from its file name, with links to the previous and next day. Because the date comes from the title (not the clock), the template works when you create tomorrow's note tonight:

# <% tp.date.now("dddd, MMMM D, YYYY", 0, tp.file.title, "YYYY-MM-DD") %>

← [[<% tp.date.now("YYYY-MM-DD", -1, tp.file.title, "YYYY-MM-DD") %>]] | [[<% tp.date.now("YYYY-MM-DD", 1, tp.file.title, "YYYY-MM-DD") %>]] →

A weekly note that computes its own date range from a file name like 2026-W24, using the moment library Templater exposes:

start: <% moment(tp.file.title, "GGGG-[W]WW").startOf("isoWeek").format("YYYY-MM-DD") %>
end: <% moment(tp.file.title, "GGGG-[W]WW").endOf("isoWeek").format("YYYY-MM-DD") %>

A timestamp ID for zettelkasten permanent notes, stamped at creation so links never rot when titles change:

id: <% tp.date.now("YYYYMMDDHHmm") %>

A prompt and a cursor position — Templater asks for a value when you insert the template, fills it in, then leaves the cursor where the writing starts:

# Call with <% tp.system.prompt("Who is this call with?") %>

## Notes

<% tp.file.cursor() %>

The first three are running in context in the daily note template, the weekly note template and the zettelkasten starter vault — download any of them to see the full template files rather than excerpts.

Templater settings worth changing

Three settings cover most of the difference between Templater feeling clunky and feeling invisible. First, Template folder location: point it at the same Templates/ folder core Templates uses, so both systems read from one place. Second, Trigger Templater on new file creation: with this on, templates fire automatically when notes are created — including notes created by clicking a link that does not exist yet, which is what lets you click tomorrow's link in a daily note and land on an already-formatted page. Third, Folder templates: map a folder to a template (say, Meetings/ to your meeting skeleton) and every note born in that folder arrives pre-structured, no command needed.

One habit to adopt alongside: keep template files out of your search results and graph by excluding the templates folder under Settings → Files and links → Excluded files. Template code reads as gibberish everywhere except inside the template itself.

Core Templates or Templater: how to choose

The honest decision rule is shorter than the feature lists suggest. Start with core Templates. Switch when you catch yourself doing a computer's job by hand — typing yesterday's date, fixing links after a rename, re-deriving week ranges. Specifically:

  • Static skeleton plus today's date → core Templates is enough, and one less plugin to trust.
  • Notes created for dates other than today, prev/next navigation, derived ranges → Templater.
  • Prompted values, auto-applied folder templates, anything conditional → Templater, no contest.

The two coexist without conflict — many vaults keep core Templates for simple inserts and reserve Templater for daily and weekly notes. Our templates that benefit from dynamic dates ship both variants in the same zip (a core Templates file and a Templater file), so the choice is reversible: start simple, upgrade by switching which file your settings point at.

How to install a Vaultorial template

Every download on this site is a zip containing a complete vault: Markdown notes, a Templates/ folder, a Start Here note, a README with these same steps, and a minimal .obsidian folder with plain-JSON settings — no binaries, no bundled plugins. There are two ways to use one.

Path A — open it as its own vault (best for trying a system out):

  1. Download the zip from the template's page and unzip it.
  2. In Obsidian, choose Open folder as vault and select the unzipped folder.
  3. When Obsidian asks whether to trust the vault, the settings are readable JSON you can inspect — nothing executes on open.
  4. Read Start Here.md. It tours the structure and lists the first three things to do.

Path B — merge it into your existing vault (when the system has earned a permanent place):

  1. Copy the content folders (for example Daily/) and the Templates/ folder from the unzipped download into your vault.
  2. Point your template settings at the copied folder: Settings → Templates for core, or Templater's template folder setting.
  3. Mirror any plugin-specific settings the README calls out — for a daily note template, that is the Daily notes folder, date format and template file.
  4. If the template lists required community plugins, install them from Obsidian's directory; the template page and the README name every required and optional plugin before you download.

That is the whole procedure, and it is identical for every template here, from the meeting notes pack to the journal vault. If you are still deciding what to install, browse the daily notes and meetings & work sections, or start from the beginner's guide to Obsidian — it explains the vault concepts this page takes for granted.

Browse templates