Property support for non-markdown files

Use case or problem

The use case is binary file management. Obsidian already supports inline rendering of PDFs, audio and video files. This fact invites such files to become integral part of the vault. However, Obsidian does not support assigning metadata to binary files, like it does for markdown. You cannot tag a PDF, for example. The same goes for canvases, AFAIC.

It is possible to use a “twin” markdown file, and there are plugins that try to automate this, but that is cumbersome.

Now that we have properties and property panes it seems logical to extend property support to binary files. It is clear, though, that properties for binaries would have to be stored externally w.r.t. the file, like in a JSON file inside .obsidian.

Proposed solution

The property pane works for binary files exactly as it does for markdown files.

Current workaround (optional)

Creating markdown files that mirror/link to the binary files.


This would be very useful in canvas and can be implemented in the JSON without external dependencies.

1 Like

Would be very helpful, using twin markdown files is very cumbersome and sucks overall

1 Like

+1 for this. It would be a true game changer for me and my admittedly idiosyncratic uses of Obsidian :smile: