Enhance The New Metadata Properties in Obsidian MD with These Plugins

Obsidian’s new “file properties” feature turns note metadata into editable, user-friendly fields—checkboxes, dates, and sidebar views—making it far easier to manage structured information than the old front-matter-only workflow. The core upgrade is that properties aren’t just text at the top of a note; they can be edited in a more guided way (including type-specific controls like calendars) and surfaced through dedicated views that support cross-note searching and filtering.

In practice, adding a property starts from the command palette: “Add file property” creates a field with a name and value, defaulting to text. Changing the property type is interactive—warnings prompt the user to update the type (for example, switching to a checkbox), and date fields can be set either by typing or by selecting from a calendar. For daily notes, date properties also include a quick-jump button that navigates to the corresponding day, reducing the friction of scrolling through long documents just to edit metadata.

For long-form notes, properties can be managed without jumping to the top by using “Show file properties” in the sidebar. Even more powerful is “Show all properties,” which aggregates a vault’s properties across notes. From there, clicking a property value can populate a search filter for all notes sharing that field. The workflow supports more precise queries too: adding a colon and a value lets users narrow results (e.g., filtering podcast notes by a specific podcast name). There’s also a property-search mode that selects a field and value directly from the search pane.

Where the workflow becomes “pro” is automation and richer interaction. A community plugin called Templator can predefine property sets when new notes are created. By installing Templator, pointing it at a templates folder, and enabling “trigger templator on new file creation,” every new “podcast episode” note can automatically receive fields like URL, rating, and finished status. Templator variables then go further by auto-filling values at creation time. Using TP file variables (like `{{tp file title}}`) and date logic via the Moment library, a daily note template can compute a “week” property (e.g., Week 35) from the note title, then insert a link to the relevant weekly note.

To make property entry feel natural inside the writing flow, the workflow adds inline property editing. It relies on the Data View plugin for property fields inside text, plus an additional plugin (installed via BRAT if needed) that syncs those inline fields back into the properties menu. A simple syntax—using double colons after a field name—creates an inline field that syncs to the corresponding property, with customizable underline behavior to avoid ambiguity when multiple fields exist.

Finally, navigation solves a practical limitation: property fields are effectively single-line, so long summaries can’t be fully browsed from tables. The solution uses Obsidian header links: a daily note template adds a link to a specific “Summary” header using the title variable plus a hashtag anchor. That link can appear as a hoverable icon in weekly tables, letting users preview the full summary and jump directly to the section without scrolling. The result is a metadata system that’s not only structured, but also fast to fill, easy to search, and simple to navigate across notes.