Canvas: Add properties/YAML tied to a canvas (as a whole)

Use case or problem

I think having frontmatter values in canvas files just as in the normal .md ones could be a really powerfull feature allowing us to combine our visual thinking with incredible plugins as Datawiew, Spaced Repetition or the core Search plugin.
As the quantity of .canvas files increases this need of metadata will become more evident just as in any actual Obsidian Workflow

Proposed solution

I wish it could exist a section in the side bar of the canvas plugin with an option to add metadata information

Current workaround (optional)

Related feature requests (optional)


So much this - i really wonder why this isnt requested more often.
Once you start using this more and more, and the number of canvas-files keep growing, you quickly realize that linking to a canvas isnt enough.
Frontmatter is the best way to keep it in line with the rest of the workflows.

So a big +1 from me!!!

Related: Tags in Canvas files: Allow tags for a canvas - #4 by ButteredBread

I wonder. These could possibly be combined. Because I imagine if this was implemented, the area where any tags or metadata would go would be the same area.

  • 1 for this feature, definitely necessary for proper integration with note systems build around it!

I vote for this too. I use dataview to make tables of my pages by various topics, but canvases get lost. The idea of adding metadata is a must have.

1 Like

+1 this is essential so canvas files can be used with dataview… and obsidian without dataview… well, it’s not really obsidian

1 Like

Since tags are just one specific frontmatter entry for metadata, I believe there has to be a frontmatter support for canvas first, before there even can be a tag support for canvas.

The Canvas files are JSON Files with data about nodes, edes and texts. Adding another key:object element should be straight forward. I guess the parsing the additional data (it is JSON and not the regular frontmatter stuff) is the effort here…

I think a good solution would be to have a “meta-data-card”, which should be found ONLY ONCE under the cogwheel-icon.
This special card should then accept YAML, inline:: or inline-tags…

Really want this feature so much… :slight_smile:

I use a database (DB-Folder) to track all my files and they all come with a metadata-block…
So it would be damn cool to be able to put all that inside a canvas template aswell…

1 Like

This is essential, or at the very least allow us to assign tags to the canvas files. There is pretty much no way to index these files. In my opinion, it’s a terrible idea (adoption-wise) to delay this feature any longer, we are roughly 8 months since release and still no way to categorize or fit well into existing workflows.

Use case or problem

I use YAML data to create dashboards for my notes, but since Canvases are written with JSON formatting, no plug-in recognizes them. Therefore, Canvases tend to be “invisible” to my workflows.

Proposed solution


  1. Enable Obsidian to recognize a YAML block within a Card in the Canvas,
  2. Or create a YAML asset at the bottom (e.g. “Drag to add YAML block”) specifically for YAML to be entered & treated differently. There can be only 1 YAML block per Canvas to avoid any clashing.

Current workaround (optional)

I’m currently just adding YAML data directly to a Card in the Canvas, hoping that this feature will be added in the future and that I don’t need to go through all my Canvases in the future to add this information.

Related feature requests (optional)

Similar to all of the posts related to how tagging should work properly within Canvas.


This is extremely important! I don’t understand why it is not standarized in same way as the note. Please add support for YAMLs!

+1 here

I’m still not using Canvas as i’d like because of the lack of YAML support.


I agree, please add frontmatter support

I agree, please add Yaml support. It would also be nice if one could add/insert navigational links to elements on the canvas, in order to create a graphical dashboard.

+1. Slightly surprised this hasn’t been addressed yet.


Especially now with Properties – this makes a lot of sense, especially if we could add cssclasses.


I agree, please add frontmatter support

+1 to this. I was really surprised to learn that I can’t add frontmatter to canvases, and this limits the usefulness of canvases in my workflows.

+1, is there any current workaround for this?