How I tested a graph-view idea by adjusting my local install

Hey there!

tldr; I wanted to test-drive a small (graph-view) idea I had before making an official feature request, so I started poking around my local install to make it work. As a result, my graph-view works better for me now than before :slight_smile:


I wanted the graph view to adjust the size of nodes based only on the amount of backlinks to that note. Currently, node size is based on outgoing links and backlinks. Here’s how it’s currently working and Google BackRub approach for reference.


To change the javascript to test out this feature, I extracted my local installation, edited the lines of code I figured would achieve my result, repackaged the installation and reloaded my running Obsidian app.

After the intitial set up, the workflow is good enough to poke around and test things out quickly.


It works! Yay! My graph-view now renders nodes based on their backlinks only.

Here’s a before and after picture to illustrate with a sample data vault:

Before with default rendering where the “Index Note” has the same size as the “Authority Note”:

…and after editing where only the “Authority Note” has more weight because of its backlinks:

I’m very happy with how it helps me view the graph. When running it against my personal vault, the topography changes for the better for me. Far less noise from index notes. It helps me discover what notes have, over time, become the real “authorities” or important topics in my mind-space. That wasn’t possible before.

Here’s the workflow in detail for MacOs:

Detailed workflow

  1. Install development dependencies (MacOS)
# Install asar for extracting and re-packaging app
$ brew install npm
$ npm install -g asar js-beautify
$ cd ~/Library/Application\ Support/obsidian
# Note: Your version number may very well differ
$ cp obsidian-0.8.2.asar obsidian-0.8.2.asar.bak
# Extract source
$ asar extract obsidian-0.8.2.asar obsidian-0.8.2
# Beautify obfuscated/minimized js for easier editing
$ js-beautify obsidian-0.8.2/app.js -o obsidian-0.8.2/app.js
  1. Open obsidian-0.8.2/app.js or other files with an editor of your choice.
  2. Make the edits you want to make.
  3. Repackage the app after you’ve made your change:
$ asar pack obsidian-0.8.2 obsidian-0.8.2.asar
  1. Then, in Obsidian, reload the app with ⌘ R.
  2. Check out how your changes work.
  3. Rinse and repeat from step 3 to step 6

Note: After updating to a newer version, existing changes will be lost unless you start tracking versions somehow on your own.

Hope this is interesting and still counts as a (maybe even nifty) hack.


This is a truly amazing discovery. I agree with you that the backlinks should be criterion for the size of a node. Everyone has their own wishes and ways of using their notes, but to detect important topic in one’s collection of notes/zettelkasten this is it.

I have long been wondering what I could get out of the graph view, how it could help me make better use of the links and what they mean. Now the penny has dropped.

Many thanks and I sincerely hope the devs will take your discovery and its implication into consideration.


Is there an easy way to add this on a Windows installation?

In any case, this looks like any excellent toggle to add to the official Graph view feature.


Totally. For me, best-case it’s a discovery tool and in worst-case a nice-to-have toy. I’ll put together a more formal feature request this week.

1 Like

Hi @icebear! I truly don’t know much about Windows, I’m sorry.

But the steps probably remain the same. Locate the actual installation and look for obsidian-YOUR-VERSION.asar, get that unpacked, edit and repack in the same location.

I saw your post about the different toggles and I very much agree with you there. It should be possible to switch/combine between size based on outbound and backlinks, word count, directory etc.

Yes please !!

To add to the best-case discovery scenario: The backlinks-based, less-noisy version of the graph-view has helped me discover:

The 1. "Elephants in the Room"

The “elephants in the room”, the “blind spots” that live in the space between notes that I either choose to ignore or underestimate.

I can “ask” the graph:

  • What am I missing?
  • What’s NOT in this picture?
  • What note or idea or topic SHOULD be huge but isn’t?
  • What am I actively NOT taking note of?

2. The "Pretend-Authorities"

These are heavily backlinked notes that I thought mattered but aren’t really important.

I can “ask” the graph:

  • Is this really important to me?
  • Does this truly deserve the “air-time” it’s getting?

I then remove and clean up those backlinks to down-regulate the notes’ relevance.

Hope this makes sense.



Alexis, this makes a lot of sense and certainly helps me see more clearly how I can use the graph to contribute to my thinking, if only we eventually get offered the option, somehow, to make the graph view backlinks based.

Once again, my congrats on this excellent discovery, and thanks for helping me see the the forest for the trees, which is what my graph view really looks like.


Hi Klaas! Same to you, thank you for thinking out loud and thinking this through with me.

I’m trying to “learn in public” by posting comments. (Usually I’ve got major “digital social anxiety” so your kind words help me a lot.)


No need for “digital social anxiety”, your wording is fine. In fact, I like the way you state things and explain things. Continue the way you’re going, you’re doing great !!

1 Like

Thank you @Klaas, will do!

1 Like

Thx for this great thread!
I will definitely try this out.


1 Like

@akaalias: not quite the same, but this could be a step in the right direction, albeit without a graph.

1 Like

This seems like a great way to improve the graph that I have been looking for!

However… what does this and step 3.) mean? :slight_smile:

I can open the graph.json in VSC, but there is no mention of backlinks. Could you maybe give an example of the lines that need to be edited?

The OP made another post where he mentioned the exact lines he touched to get this result. He mentioned it in his first post. Here is a link to it again… Graph nodes size should also depend on word count in addition to no of links - #5 by akaalias

PS: It would be great to get a toggle to switch this setting on or off.

1 Like

This is embarrassing… I didn’t click the link because I misunderstood “how it’s currently working” to mean the default setting of Obsidian being contrasted with Google BackRub. So thank you very much for taking the time to point out the obvious! :upside_down_face:

Also +1 for having this implemented as a feature.