README file from
GithubNested Properties
YAML frontmatter nests, but Obsidian's Properties editor does not. Give a note a nested structure and the panel shows you nothing useful — the values are there in the file, and the only way to read or change them is to edit the raw YAML by hand and hope you get the indentation right.
This plugin renders nested objects and arrays as a collapsible tree in the Properties panel, where you can read them, edit them, change their types, and rename or delete a nested key across the whole vault.
---
level1simple: simple1
level1Nested:
level2simple: simple2
level2Nested:
level3simple: simple3
level3Nested:
level4simple: simple4
level4Nested:
level5simple: simple5
---
Inspired by this feature request.
Demo vault
The documentation is a demo vault. Every feature has a note whose own frontmatter demonstrates it — open the note, look at the Properties panel, and you are looking at the feature.
Start reading here — it is plain markdown, so it works on GitHub with nothing installed.
A copy of the vault ships with every release. You can access it via any of the following:
- Running the
Nested Properties: Open demo vault command. - Downloading
nested-properties-demo-vault.zipfrom the Releases. It unzips into a singlenested-properties-demo-vault-<version>folder. - Browsing its source in
demo-vault/in this repository.
What it does
- Nested objects and arrays as a tree in the Properties panel, collapsible to any depth. 01 Nested objects · 02 Nested arrays · 05 Deeply nested and scrolling
- Mixed and complex shapes — lists holding different types, and arrays of objects. 03 Mixed lists · 04 Array of objects
- Edit in place — add, remove and reorder entries from the context menu, and change a nested property's type without rewriting the YAML. 06 Context menu actions · 07 Changing property types
- Type a nested value from the keyboard — enter
{ author: Jane, year: 2024 },[a, b],[]or[{ title: Intro }]as a property's value and press Enter, and it becomes an object, a list or a list of objects. 12 Typing nested values - Keyboard navigation — move through the tree, open and close it, edit a value, add an entry and remove one with the keys Obsidian uses for its own properties. 13 Keyboard navigation
- Rename or delete a nested key across the whole vault, not just in the note you are looking at. On desktop, with the vault in a
gitrepository, the Should commit bulk operations setting records each run asgitcommits, and the Undo a bulk operation... command reverts one. 09 Vault-wide rename and delete - Find them — search nested properties the way you search anything else. 10 Search nested properties
- Use them in Bases — pick
book.authoras a column, sort by it, and edit it right in the table cell, with no formula. 14 Nested properties in Bases - See the full key of a nested entry when the short name is ambiguous. 08 Full key display
- Read it without opening it — a collapsed property shows a one-line preview of its content, and you can choose how many levels arrive expanded, vault-wide or per note. 11 Initial expand level
Initial expand level
A nested property arrives collapsed by default, and a collapsed row is readable on its own: it shows a one-line preview of its content rather than an opaque { ... }, with any complex value inside it elided so the row stays one line tall.
If you would rather some of it arrived already open, set Settings → Nested Properties → Initial expand level — 1 opens the nested property but not its children, 2 opens the children too, and so on. An array index counts as a level of its own, so in generated.foo.0 the array item sits one level below generated.foo.
A note can override the setting for itself:
---
nestedProperties:
initialExpandLevel: 2
---
Typing nested values
A text value written as a one-line YAML collection becomes the value it describes when you press Enter or leave the field, and opens so you can keep editing it:
{ author: Jane, year: 2024 }becomes an object, and{}an empty one;[a, b]becomes a list, and[]an empty one, with the cursor in it so you can type the next item straight away;[{ title: Intro }, { title: Outro }]becomes a list of objects;{author:Jane}works too: the space after a key's colon is optional.
It works on a nested text entry as well as on a top-level property. A top-level list is shown with Obsidian's own List widget for that note only: the property's type is not changed, so other notes are not affected. If the property is set to Text for the whole vault, Obsidian marks the list with its usual type-mismatch warning, as it does for a list written in Source mode. An empty list is saved the way Obsidian saves an empty List, as an empty value.
Ordinary text is left alone: a whole value that is one wikilink such as [[Note]], placeholders such as {{date}}, and anything that is not valid YAML stay as typed. Inside a list YAML's rules apply, so a link there is written in quotes: ["[[a]]", "[[b]]"] is a list of two links, while [[a], [b]] is a list of two lists. To keep a value like { a: 1 } as text, turn off Settings → Nested Properties → Should convert flow collections.
Keyboard navigation
A nested property works like a list of rows, and an object or list row opens onto its children. With a row focused, the keys are the ones Obsidian already uses for its own properties:
| Key | On a row |
|---|---|
| ↓ or j, Tab | Next row, skipping the rows inside anything collapsed |
| ↑ or k, Shift+Tab | Previous row |
| Enter, Space or → | Edit a value; on an object or list, open it and go to its first row |
| A / i | Edit a value with the cursor at its end / start |
| ← | Close an open object or list; otherwise go to the row it sits in |
| Delete (Cmd+Backspace on macOS) | Remove the entry |
| o | Add a property (or an item) next to this one |
| Shift+F10 or the Menu key | Open the row's menu |
Add property and Add item take the focus too, and Enter or Space presses them. A value finished with Enter hands the focus back to its row.
See also
| Plugin | Features | How Nested Properties differs |
|---|---|---|
Better Properties |
Unlisted; additional property types and per-property settings; object type | Narrower focus: nesting; vault-wide rename/delete and search |
Nested Frontmatter |
Unlisted; read-only nested Properties rows; clickable links | Same nesting goal; editable values |
Nested Frontmatter Properties |
Nested object/array rows in the Properties panel; add/remove keys and items | Broader nesting UI: collapsible tree, type changes, vault-wide rename/delete and search |
Solenoid Properties |
List/table/frame/cube property types; popup editor for nested tabular YAML | Broader nesting scope: arbitrary nested objects and arrays |
YAML Editor |
YAML text editor; frontmatter, blocks and files; completion, folding, snippets | Alternative UI: edits nested values through Properties rows |
YAML Properties |
Replaces in-note Properties with editable YAML text | Alternative UI: keeps Properties and gives each nested key a row |
Last searched for similar plugins on 2026-10-26.
Installation
The plugin is available in the official Community Plugins repository.
Beta versions
To install the latest beta release of this plugin (regardless if it is available in the official Community Plugins repository or not), follow these steps:
- Ensure you have the BRAT plugin installed and enabled.
- Click Install via BRAT.
- An Obsidian pop-up window should appear. In the window, click the
Add pluginbutton once and wait a few seconds for the plugin to install.
Debugging
By default, debug messages for this plugin (id: nested-properties) are hidden.
If you need to enable them refer to the documentation.
Changelog
All notable changes to this project will be documented in the CHANGELOG.
Contributing
Contributions are welcome — see CONTRIBUTING to get set up.
Support
Filing an issue (for AI agents and humans)
Open issues through the issue forms, not as blank issues.
To report a bug from inside Obsidian, run the Nested Properties: Report a bug command. It opens the bug form with the plugin version, the Obsidian version and your operating system already filled in.
Filing from the CLI or the API (gh issue create --body, or an AI agent filing for you) skips the form, and gh issue create --template cannot load an issue form. In that case, open the matching form in .github/ISSUE_TEMPLATE/, copy every field as a ### <label> heading in the form's order, and fill in each one. Always state the plugin version, the Obsidian version and your operating system.