In Obsidian, Frontmatter is a section at the top of your note that contains metadata formatted in YAML (YAML Ain't Markup Language). This section is enclosed by triple dashes (---) and is used to define key-value pairs. The metadata you include could be about the note's title, creation date, tags, or any custom properties relevant to your note-taking process.
The syntax is straightforward. For example:
---
title: My Note Title
tags: [note, idea, project]
created: 2025-03-30
---
Here, the metadata is clearly defined above the main content of your note, making it easier for Obsidian and its plugins to recognize and utilize the structured data.
Frontmatter serves several essential functions:
As a note taker, you can leverage frontmatter in various ways:
To create frontmatter in a note, simply open a new note and at the very beginning, insert a block of text enclosed by triple dashes:
---
title: Meeting Notes: Team Sync
tags: [meeting, team, work]
created: 2025-03-30
attendees: [Alice, Bob, Charlie]
location: Conference Room A
---
This snippet sets up your note with structured information that you can later reference or query using Obsidian’s search features or plugins.
Beyond standard fields such as title or date, you can also define custom properties. These are especially useful for templates and recurring workflows. For instance, if you regularly take meeting notes, you might include custom fields like "attendees" and "location" to ensure consistency.
Obsidian’s Templater plugin lets you insert dynamic values into your notes. Instead of manually typing out dates or titles, you can use placeholders like {{date}}
to automatically generate the current date. This seamless integration of metadata and dynamic content enhances your overall productivity.
Moreover, with plugins like Dataview, you can query your vault using this structured metadata. For example, you can list all notes tagged with "meeting" and sort them by date:
table title, created
from "Meetings"
where contains(tags, "meeting")
sort created desc
This query will compile and display your notes in a neat table based on the frontmatter details.
Establishing a consistent structure in your frontmatter helps maintain a well-organized vault. Some best practices include:
One of the most powerful aspects of frontmatter is its integration with various plugins, which extend Obsidian’s functionality:
These integrations empower you to create an interconnected and efficient note-taking system where metadata is not just static information, but a driving force behind your workflow.
The table below compares some of the key frontmatter properties commonly used in Obsidian and their typical applications:
Property | Description | Usage Example |
---|---|---|
title | The name or subject of the note. | My Daily Journal |
tags | A list of keywords or categories. | [meeting, project, research] |
created | Creation date of the note. | 2025-03-30 |
modified | Date when the note was last updated. | 2025-03-31 |
aliases | Alternative names for the note. | [Journal, Daylog] |
custom fields | Additional info like status, location, etc. | status: in-progress |
The radar chart below illustrates an opinionated analysis of common aspects of frontmatter usage among note-takers in Obsidian. It reflects the importance of various aspects such as organization, custom properties, plugin integration, template usage, and filtering.
The mindmap below provides a simplified visual representation of the key aspects and workflow of using frontmatter in Obsidian. It showcases how metadata creation leads to improved organization, integration with plugins, and streamlined note-taking routines.
For a comprehensive overview and step-by-step instructions on using frontmatter in Obsidian, check out the video tutorial below. The video demonstrates how to create YAML frontmatter, integrate plugins, and optimize your note-taking workflow.