Obsidian properties in YAML frontmatter (v1.4 - OUT NOW!)

Obsidian 1.4 introduces a redesigned YAML frontmatter experience that adds a real “properties” layer on top of plain text—complete with typed fields, clickable note links, and a dedicated properties pane. The practical payoff is fewer silent breakages (like malformed YAML or inconsistent property names) and less manual work to keep metadata and links working as notes evolve.

For years, YAML frontmatter has been powerful but fragile: a missing dash or an incorrectly defined key/value pair can break metadata without obvious warnings, and links inside frontmatter historically didn’t reliably update when a note was renamed. Many users responded by moving links into comments inside the note body—clickable, but redundant and harder to keep clean. Obsidian 1.4 tackles both problems by adding a new UI for frontmatter and properties, while still preserving the underlying text-based YAML for compatibility with external editors and IDEs.

In the new UI, each property shows an icon that corresponds to its type. Instead of typing raw YAML, users can add properties through the interface and select property types such as Text, List (multi-select), Number, Checkbox (Boolean), Date, and Time. The interface also infers types automatically in some cases—for example, choosing a date type when the value looks like a date. Most importantly, once a property type is set, Obsidian restricts what can be entered: a field defined as Number won’t accept arbitrary strings, and a Date field switches to a date picker rather than freeform typing.

Existing properties can be retagged with new types, but inconsistent historical data can trigger compatibility errors. If earlier notes stored mixed values for the same key (including placeholders like “none” or template-derived strings), changing the type forces those values to be reconciled. The workflow implication is clear: teams and individuals aiming for consistency may need to “rejig” older notes to match the new typed standard.

Link handling improves as well. In the frontmatter UI, note links become clickable and update when the target note name changes—eliminating the need for the old comment-based workaround. URL properties are also supported, and clicking them opens the linked resource in the browser.

Beyond the UI, Obsidian adds a new core plugin called Properties, enabled by default. It provides two panes accessible via the command palette: one for file properties (useful while editing) and another that lists all properties across the vault. That “all properties” view helps spot inconsistencies—such as near-duplicate keys or mismatched types—by letting users inspect and change property types from a centralized place.

Compatibility isn’t universal. Some plugins require adjustments: Templater can break if a property type is changed to Number/Date while templates still output templater strings; Fantasy Calendar may lose its nested-key date picker UI because the new model doesn’t support nested keys the same way; and the Banners plugin may mis-parse frontmatter depending on whether it expects source mode. Other tools, including Dataview and ExcaliBrain, continue to parse frontmatter, though users may need to adjust list formatting (e.g., comma-separated values may need to become explicit arrays).

Overall, Obsidian 1.4 reframes frontmatter from “typed-by-hand YAML” into a typed metadata system—trading some migration friction for stronger consistency, better link behavior, and a smoother editing experience for heavy frontmatter users.