Lesson 3.2: The Graph View - Obsidian Course

Nodes, Edges & What You're Seeing

Open the Graph view from the left ribbon icon (the little connected-dots symbol) or via the Command palette — "Open graph view." Your vault appears as a cloud of dots joined by lines. Two words unlock the whole thing:

Node — a dot. Every note in your vault is one node. Bigger dots usually mean more-connected notes (a setting we'll meet). Faded, hollow dots are usually ghost/unresolved notes — those "link first, create later" placeholders from last lesson. Attachments (images, PDFs) can appear too, if you enable them.
Edge — a line. Every internal link between two notes draws one edge. The graph is literally a drawing of the [[links]] you've been making. No links, no lines.

That's the entire concept: notes are dots, links are lines. The graph doesn't know anything you didn't tell it — it's a visualization of the web you built by hand in Lesson 3.1. Which means the graph is also a mirror: a sparse, stringy graph says "I haven't linked much yet," and a dense, clustered one says "my ideas are talking to each other." Neither is a grade — both are just feedback.

🧠 Mindset

The first time people open the graph, they feel one of two things: "whoa, that's beautiful" or "mine looks pathetic compared to the screenshots online." Ignore both reactions. Those dazzling galaxy-graphs belong to people with thousands of notes and years of linking — and half of them admit they never actually use the graph. A small, honest graph of your real notes is worth infinitely more than a gorgeous one you built to look impressive. Your graph will grow on its own, one link at a time. Don't perform for it.

Global Graph vs. Local Graph

Obsidian gives you two flavors of graph, and knowing which to reach for is half the skill.

🌌 The global graph

This is the famous one: every note in your vault at once, with every link drawn. It's the big-picture, bird's-eye view. It's great for questions like "what does my whole vault look like?", "where are my dense clusters?", and "which notes are floating alone out at the edges?" It is not where you go to find one specific note — for that you have the Quick switcher and Search.

🔎 The local graph

The local graph shows the neighborhood around one note — the note you're currently viewing, plus the notes it connects to. Open it from the Command palette ("Open local graph") or the note's more-options menu. It answers a much more useful everyday question: "what is this note connected to, and what's one step further out?" Because you can control how many steps out it reaches (the depth setting, next section), the local graph is the one that actually earns a spot in your daily workflow. Pop it in the sidebar next to a note and it becomes a little live map of that idea's surroundings.

	Global graph	Local graph
Shows	The entire vault	One note + its neighbors
Best question	"What's the shape of everything?"	"What's around this note?"
Great for	Spotting orphans, clusters, overall health	Exploring one idea's connections while you work
Daily usefulness	Occasional review	Genuinely handy as a sidebar companion

Reading the Graph: Clusters, Hubs & Orphans

A graph is only useful if you can read it. Three shapes tell you almost everything.

graph TD subgraph Health cluster SLEEP["Sleep"] --- CAFF["Caffeine"] SLEEP --- EXER["Exercise"] CAFF --- FOCUS["Focus"] HUB["Health MOC"] --- SLEEP HUB --- CAFF HUB --- EXER HUB --- FOCUS end subgraph Cooking cluster PASTA["Pasta"] --- SAUCE["Tomato Sauce"] PASTA --- PANTRY["Pantry Staples"] end ORPHAN["🏝️ Random Idea
(orphan — no links)"]

Two clusters (a busy Health group with a hub note, a smaller Cooking group) and one orphan floating alone with no connections.

🕸️ Clusters

A cluster is a tight knot of notes with many links among them — your notes on a topic naturally pull together. When you tune the physics (next section), related notes drift toward each other and form visible blobs. Seeing distinct clusters is a good sign: it means your topics are internally connected. Seeing two clusters that should be related sitting far apart with no line between them is a prompt — maybe they want a link, or a shared hub note.

⭐ Hubs

A hub is a node with unusually many edges — everything in a cluster points to it. If you turn on node-size-by-links, hubs are the big dots. These are often your most important notes: an index, a Map of Content, a project home. Finding your hubs tells you where your thinking already organizes itself. (Hubs are exactly what Lesson 3.3 will teach you to build on purpose.)

🏝️ Orphans (isolated notes)

An orphan is a node with no edges at all — a note nothing links to and that links to nothing. It floats out at the edge of the graph, alone. Orphans aren't shameful, but they're worth noticing: an unlinked note is a note you'll probably never rediscover, because there's no doorway back to it. The global graph makes orphans obvious at a glance, and you can even filter to show only orphans — which turns "find my forgotten notes" into a two-click job. Rescuing orphans (linking them into a cluster) is one of the most genuinely valuable things the graph helps you do.

✅ Pro Tip — the graph is a to-do list in disguise

Don't just admire the graph — act on it. A big cluster with no hub? Consider a Map of Content. Two clusters that should touch? Add a bridging link. A drift of orphans at the rim? Spend five minutes giving each one a home. The graph's real value is turning "vague sense that my vault is messy" into specific, clickable jobs.

Graph Settings: Filters, Groups & Forces

Open the graph and click the settings gear (top-left of the graph pane) to expand the controls. They're grouped into a few collapsible sections. Here's what each one actually does.

🔍 Filters

The Filters section narrows which notes appear. You get a search box that accepts the same query syntax as global Search, so you can scope the graph to a slice of your vault:

tag:#project — show only notes tagged #project
path:"Work/" — show only notes in the Work folder
Any search text — show only notes matching it

Filters also include toggles for whether to show tags, attachments, existing files only (hide ghost notes), and — the useful one — orphans on or off. Turning everything off except orphans is the fastest way to find isolated notes.

🎨 Groups (and colors)

The Groups section is where the graph gets genuinely informative. You define a group by a search query and assign it a color. Every node matching that query gets painted that color. Now your graph isn't just dots — it's a color-coded map. For example:

tag:#project → orange
tag:#book → green
path:"Daily/" → blue

Suddenly you can see that your green book-notes cluster together, that your daily notes form a blue chain along the edge, and where your orange projects connect to everything else. Color-coding by tag or folder is what turns the graph from decoration into a diagnostic tool. You'll do exactly this in the project.

⚛️ Display & Forces

The Display section controls appearance: node size, link thickness, text fade, arrows, and node size based on number of links (turn this on to make hubs pop). The Forces section controls the physics simulation that lays the graph out. These four sliders are the ones people fiddle with endlessly, so here's what each really means:

Force	What it does	Turn it up when…
Center force (gravity)	Pulls all nodes toward the middle	Your graph is flying off-screen and you want it gathered
Repel force	Pushes nodes apart so they don't overlap	Nodes are cramped and labels overlap — spread them out
Link force	How strongly a link pulls its two notes together	You want connected notes to clump into tighter clusters
Link distance	The resting length of each link line	You want more (higher) or less (lower) space along each edge

💡 A good starting recipe

There's no "correct" setting — it's aesthetic and depends on vault size. A comfortable starting point for a small vault: moderate center force, fairly high repel (so nodes breathe), medium link force (so clusters form without collapsing into a ball), and medium link distance. Nudge one slider at a time and watch what happens — the layout re-simulates live. When you like it, that's your graph. Don't chase perfection here.

⚠️ Important Note: Graph settings are a view preference, not a change to your notes. Coloring a group, hiding orphans, or cranking the repel force never edits a single note — it only changes how the graph is drawn. Experiment freely; you can't hurt anything.

The Local Graph as a Sidebar Companion

This is where the graph stops being a party trick and becomes part of how you work. Open a note, then open its local graph and drag that pane into the right sidebar so it sits beside your note. Now, as you move from note to note, the local graph updates to show the neighborhood of whatever you're reading.

The local graph has two settings the global one doesn't lean on as hard:

Depth — how many link-hops out from the current note to show. Depth 1 shows only direct neighbors; depth 2 adds neighbors-of-neighbors; and so on. Depth 1 or 2 is the sweet spot — higher and the local graph balloons into a mini global graph and loses its point.
Show neighbor links / render both directions — whether to include links between the neighbors, and whether to follow both outgoing and incoming links. Turning on neighbor links reveals little clusters right next to your note that you might want to bridge.

Used this way, the local graph answers a question you have constantly: "what else touches this?" You're writing about a book and the local graph reminds you it's connected to three project notes you forgot about. That's the graph paying rent.

✅ Pro Tip

Pair the local graph with the Backlinks pane from last lesson. Backlinks give you the sentences ("here's exactly how this note is mentioned"); the local graph gives you the shape ("here's the constellation around it"). Text and picture together are a fuller portrait of an idea's place in your vault than either alone.

An Honest Take: What the Graph Is Really For

Time for some candor, because this is where a lot of Obsidian advice oversells. The global graph is the app's most photographed feature and its most overrated one as a daily tool. Let's be straight about it.

What the graph is genuinely great at:

Feedback. "What's disconnected?" "Where are my orphans?" "Do my topics actually cluster, or is everything one big blob / a hundred islands?" The graph answers these at a glance in a way no list can.
Inspiration. Panning around your own web occasionally sparks a "oh, these two should connect" moment. It's a low-effort way to stumble into forgotten notes and unexpected links.
Health checks. A periodic look (say, monthly) tells you whether your linking habit is working — is the graph knitting together, or fraying into orphans?

What the graph is not good at:

Daily navigation. Nobody sane finds a specific note by hunting for its dot in a cloud of 800. The Quick switcher (type a name, hit Enter) and Search are dramatically faster. The graph is a map to look at, not a menu to click through.
Being a goal. A pretty graph is a side effect of good notes, never the objective. Optimizing your vault to make the graph look cool is backwards — it leads to fake links and wasted evenings.

⚠️ Watch Out — the graph-gardening trap

It is very easy to lose an hour tweaking forces and admiring your constellation while writing zero new notes. That's productivity procrastination in its purest form. Enjoy the graph, use it for feedback, then close it and go write. The value of your vault lives in the notes and links — the graph is just the reflection.

The healthiest way to relate to the graph: treat it like a mirror you glance in occasionally, not a dashboard you live in. It tells you how your vault is doing. Then you go do the actual work — writing and linking — that makes the reflection better.

🎯 Project: Tune, Color & Rescue an Orphan

Three concrete moves that cover everything this lesson taught: make the graph readable, make it informative with color, and use it to do one genuinely useful piece of vault maintenance.

🏋️ Make your graph work for you

Objective: Configure a graph you can actually read, color-code a group, and find plus rescue a real orphan note.

Instructions (about 20 minutes):

(2 min) Open the global graph. Just look. Do you see any clusters? Any dots floating alone at the edges? Get oriented before you touch a slider.
(4 min) Open the settings gear → Forces. Nudge repel up until nodes stop overlapping, then adjust link force and link distance until related notes form visible clusters you can read. Turn on "node size based on number of links" in Display so your hubs pop.
(4 min) Go to Groups → add a group. Enter a query like tag:#project (or any tag/folder you actually use) and pick a bright color. Add a second group for a different tag in a contrasting color. Watch your graph light up by category.
(4 min) In Filters, turn off everything you can and make sure orphans are shown — or use the "existing files only" + orphan toggles — so isolated notes stand out. Find one orphan: a note with no lines at all.
(5 min) Click that orphan to open it. Ask: what does this note relate to? Add at least one [[link]] from it into a relevant cluster (and, ideally, one link to it from a hub note). Return to the graph — your orphan now has an edge and has drifted home.
(1 min) Bonus: open a note, launch its local graph, set depth to 2, and dock it in the sidebar. Browse a couple of notes and watch it update.

💡 Hint — good group queries to start with

tag:#project        → orange   (all your project notes)
tag:#book           → green    (reading notes)
path:"Daily/"       → blue     (daily notes)
["type": "moc"]     → purple   (hub notes, if you use a 'type' property)

Use whatever tags and folders you actually have. The point is to see your own vault colored by meaning, not to copy these exactly.

🧩 Stuck finding an orphan?

If your vault is small and everything's already linked, make one: create a quick note (Scratch idea), write a sentence, and don't link it. Open the graph — there it is, alone at the edge. Then rescue it by linking it to something related. You've just practiced the whole orphan-hunting loop you'll use for real as your vault grows.

✅ Project Completion Checklist

You adjusted the forces until the graph was readable
You turned on node-size-by-links and can spot your hubs
You created at least one colored group from a tag or folder
You used filters to surface orphans
You found an orphan and gave it at least one link (rescued it)
You opened a local graph and understand its depth setting

🎯 Quick Quiz

Question 1: In the graph view, what does a single edge (line) represent?

Question 2: What's the graph view least good at?

Best Practices for the Graph

✅ Do's

Color a few groups by tag or folder. It's the single change that makes the graph informative instead of decorative.
Use the orphan filter for maintenance. A monthly orphan-rescue session keeps your vault connected.
Keep a local graph in the sidebar. That's the version you'll actually use.
Act on what you see. Every insight from the graph should become a link, a hub, or nothing.

❌ Don'ts

Don't navigate by the global graph. Use Quick switcher and Search — they're far faster.
Don't add links just to make the graph prettier. Fake connections pollute your real web.
Don't lose an evening to the force sliders. Good enough is good enough — go write.

📓 Learning Journal

Open your learning-journal note in your vault and, after this lesson, jot down:

Key concepts you learned
Techniques that clicked for you
Questions or confusion points to revisit
Ideas you want to try
Your progress and feelings about learning this

✍️ This lesson's prompt: What did your graph reveal that a list of notes never would? Name the orphan you rescued and where you connected it. And be honest with yourself: is the graph something you'll actually use for feedback, or is it mostly eye-candy for you right now? Either answer is fine — the point is to know which.

📝 Lesson Summary

🎓 Key Takeaways

In the graph, nodes are notes and edges are links — it's a drawing of the web you built by linking.
The global graph shows the whole vault (big-picture feedback); the local graph shows one note's neighborhood (useful daily, with a depth setting).
Read the graph by spotting clusters, hubs, and orphans — and act on what you see.
Tune it with filters, color-coded groups, and the four forces (center, repel, link force, link distance).
Honestly, the graph is best as feedback and inspiration, not navigation — enjoy it, learn from it, then go write.

🎉 What You've Accomplished

You can now open your vault's map and actually read it — telling clusters from orphans, hubs from leaves — and you can tune it into a color-coded diagnostic instead of a random cloud of dots. Better still, you have a clear-eyed sense of when the graph helps and when it's just pretty, which saves you from the trap that swallows a lot of new users. You even performed real maintenance: rescuing an orphan.

❓ Common Questions at This Stage

My graph looks tiny and stringy compared to the ones online. Am I doing it wrong?

Not at all. Those galaxy-graphs come from vaults with thousands of notes and years of linking, and plenty of them are more decorative than useful. A small graph just means a young vault. Keep writing and linking; it fills in naturally. The size of your graph is not a measure of the quality of your thinking.

Can I show tags and folders in the graph, not just note links?

You can show tags as nodes via a filter toggle, which draws lines from notes to their tags — sometimes illuminating, sometimes cluttered. Folders aren't drawn as connections (folders aren't links), but you can color notes by folder using a group with a path:"Folder/" query, which is usually what people actually want.

Do my graph settings save? Will they be there next time?

The global graph remembers your settings between sessions. You can also save a graph as a bookmark/saved view so you can return to a specific configuration (e.g. an "orphans only" view) in one click. Local graph settings are per-pane. None of this changes your notes — it's all just display.

🔭 Looking Ahead

The graph showed you that some clusters have a natural hub at their center — a note everything points to. In the next lesson you'll learn to build those hubs deliberately: Maps of Content, the hand-curated notes that organize a topic far more flexibly than any folder, and the "Home" note that becomes your vault's front door.

✅ Before the Next Lesson

Make sure you've rescued at least one orphan — a connected vault makes the next lesson land
Note which of your clusters is biggest; it's a prime candidate for a Map of Content
Keep a local graph docked in your sidebar as you work for a day and see if it earns its spot
Write your Learning Journal entry for this lesson

📚 Additional Resources

🌟 Encouragement for the Journey

You looked your whole vault in the face today — and instead of being dazzled or discouraged, you learned to read it. That's rarer than it sounds. The graph will keep growing as you write, and every orphan you rescue is a note you've saved from oblivion. Now let's give your best clusters a proper home. On to Maps of Content. 🔮

📝 Lesson 3.2: The Graph View

📚 What You'll Learn