Knowledge Concepts
Graph view is a visual map of your notes showing each note as a dot and each link between notes as a line — making the structure of your knowledge base
Graph view is a visual representation of your notes as a network: each note is a dot (node), and each link between notes is a line (edge). Notes that are heavily linked appear as larger, more central nodes; notes with few links appear small and peripheral. Graph view makes the structure of your knowledge base visible — which concepts are most connected, which are isolated, and how different topic areas cluster together.
The graph is a map of your thinking, not your notes.
Graph view is a product of personal knowledge management tools, specifically those that implement bidirectional linking. When every wiki-link ([[Note Name]]) creates an edge in a network, and that network has hundreds of notes, visualizing the network becomes useful.
Roam Research was among the first PKM tools to prominently feature a graph view, making it a standard expectation for tools in the space. Obsidian's graph view is arguably its most recognizable feature — it appears in nearly every Obsidian screenshot and has become something of a status symbol for PKM enthusiasts who have built large, densely connected knowledge bases.
The underlying concept is from network science: notes as nodes, links as edges, clusters as communities. The graph view applies this to personal knowledge.
What creates the graph:
Every note in your knowledge base is a node. Every wiki-link ([[Note Name]]) or backlink creates an edge between two nodes.
Node size: In most graph view implementations, larger nodes have more connections. A note that 20 other notes link to will appear as a large node. A note with no links appears as a small, isolated dot.
Clusters: Notes that are densely linked to each other but less connected to other groups form visual clusters. If you have 30 notes about machine learning and they all link to each other, they form a cluster. If you have 20 notes about cooking that aren't connected to the machine learning notes, they form a separate cluster.
Zoom and navigation: Most graph views allow zooming in to see node labels and clicking on nodes to open the corresponding note. Hovering over a node often highlights its immediate connections.
Colors and filters: Obsidian's graph view allows filtering by tag (show only notes tagged #project), by folder, or by attachment type. Nodes can be colored by tag or by recency. Filters help you explore specific subsets of your knowledge base.
Hub notes: Notes with many connections appear prominently. These are often your most conceptually important notes — the ideas you return to repeatedly, the frameworks you apply across contexts, the people or projects that come up in many different notes.
Clusters: Groups of notes that link to each other reveal topic areas. If you've been writing primarily about three areas (say, product strategy, user research, and technical architecture), the graph will show three clusters. The connections between clusters reveal interdisciplinary thinking — notes that bridge topic areas.
Orphan notes: Notes with no links appear as isolated dots, usually in the periphery of the graph. These are notes you haven't connected to anything. Some are new and will be linked soon; others are genuinely isolated thoughts that may not belong in your connected knowledge system at all.
The shape of your thinking: After a year of consistent note-taking with linking, the graph reflects how you actually think about your domain. The large, central nodes are the concepts you consider foundational. The clusters are the topic areas you've developed most. The connections between clusters are where your cross-disciplinary insights live.
Imagine a product manager who has taken notes for 2 years in Obsidian, consistently using wiki-links.
Their graph shows:
[[Jobs to Be Done]] — linked to 40+ notes because they apply this framework constantly.[[User Research]]: 25 notes tightly connected, including interview transcripts, synthesis notes, and technique references.[[Growth]]: 20 notes about acquisition, retention, and monetization frameworks.[[Product-Market Fit]] sits between User Research and Growth clusters, linked to both.What they can do with this:
[[Jobs to Be Done]] in the graph → navigate to the note → read what makes it so central (probably their foundational framework note plus the backlinks from 40 other notes)."A denser graph is a better knowledge base." Not necessarily. A graph with thousands of nodes all linked to each other may indicate over-linking (linking everything to everything) rather than a rich knowledge base. Quality of connections matters more than quantity. A smaller graph with meaningful, intentional links is more useful than a large graph with mechanical link creation.
"Graph view is how you navigate your notes." Graph view is for exploration and overview — not day-to-day navigation. For finding a specific note: use search. For exploring what relates to the note you're in: use the backlinks panel. Graph view is a periodic check-in tool, not the primary interface.
"If your graph doesn't look like the Obsidian screenshots, you're doing it wrong." The beautiful, complex graphs in Obsidian screenshots represent years of consistent note-taking by people who document their workflows extensively. Your graph will look different based on how many notes you have, how you link, and what you write about. There's no "correct" graph shape.
"Graph view works the same in all tools." Implementations vary significantly. Obsidian's graph view is highly customizable with filters, colors, and forces. Logseq has a graph view. Roam Research has a somewhat simpler graph view. Notion has no graph view for regular notes (only for databases in some contexts). If graph view is important to you, evaluate the specific implementation in each tool.
Use it periodically, not constantly. Opening graph view every session is distraction. Opening it monthly to do a knowledge audit is useful. Specific purposes for opening graph view:
Filter to explore specific areas.
Rather than looking at the full graph (which is overwhelming at 500+ notes), filter: show only notes tagged #product-strategy. The resulting sub-graph shows how you've organized thinking in that area, which concepts are central, and which are peripheral.
Opening graph view: Ctrl+G (Windows) / Cmd+G (Mac) or clicking the graph view icon in the left sidebar.
Local graph view: Obsidian also has a "Local Graph View" — shows only the current note and its immediate connections (one or two degrees out). More useful for daily navigation than the full graph; accessible from the command palette or by Ctrl+clicking the graph view icon.
Graph filters in Obsidian: The graph panel (top right in graph view) allows:
#project.Forces: You can adjust the "forces" that determine how the graph lays out — the attraction between linked nodes and the repulsion between all nodes. A higher link force pulls connected notes closer together, making clusters more pronounced.
Bidirectional linking: The mechanism that creates graph edges. Every [[link]] you create adds an edge to the graph. The graph view visualizes what bidirectional linking creates.
Backlinks: The reverse-reference system that shows you who links to a given note. Graph view is the global view of all backlinks; the backlinks panel is the local view.
Zettelkasten: The note-taking system that relies on explicit connections between atomic notes. Graph view, in the context of a Zettelkasten, visualizes the web of connections Luhmann would have maintained in his physical card index.
Is graph view useful for beginners? Less so. Graph view is most useful with 200+ notes — below that, the graph is sparse and doesn't reveal much. In the early stages of building a note-taking system, focus on writing and linking. Graph view becomes a useful audit tool once you have a substantial knowledge base.
Can I export or share my graph view? Obsidian Publish (paid service) makes your notes publicly accessible with a navigable graph view — this is how many Obsidian users share their "digital gardens" publicly. Logseq has similar publishing capabilities. For a static export: screenshot the graph view.
Does the graph view work offline? In Obsidian (local-first): yes, fully offline. The graph is computed from your local files. In Roam Research (cloud): requires internet. Logseq (local-first): offline.
Graph view is one of the most visually striking features of modern PKM tools — and one of the most often misunderstood. It's not a navigation tool; it's an audit and exploration tool. The value it provides is a periodic bird's-eye view of how your thinking is structured: what's most connected, what's isolated, and what surprising connections exist between areas you thought were separate. That view, once or twice a month, provides insights about your own knowledge organization that would be invisible from inside individual notes.
Related reading: Building a Personal Knowledge Base.
More WebSnips articles that pair well with this topic.
Knowledge transfer is the deliberate process of moving knowledge from where it exists — an individual, team, or system — to where it is needed, in a form
A browser extension is a small software add-on installed in a web browser that adds features or modifies behavior — blocking ads, saving passwords
A content calendar is a planning tool that schedules what content will be published, when, where, and by whom — turning a content strategy from vague
A context window is the maximum amount of text an AI language model can process in a single interaction — everything in the prompt, the conversation
A knowledge silo is a condition where knowledge, information, or expertise is isolated within a team, department, or individual — inaccessible to others
A large language model (LLM) is a neural network trained on massive amounts of text to predict and generate language.