How I Use The Obsidian Graph View

Obsidian’s Graph View isn’t just a big network diagram—it’s a set of practical controls for filtering, hiding clutter, and navigating relationships between notes. The core payoff is that users can browse and “resume” their thinking visually, without relying on folder hunting, and can do it at both the vault level and inside a single note via Local Graph.

At the vault level, Graph View is organized into four main areas: Filters, Groups, Display, and Forces. Filters let users narrow what appears by tags (e.g., selecting a tag like “moc”), by folder-like paths (e.g., journal templates and weekly journal folders), by filename search, and by keyword matches within headings or lines. Additional toggles refine results further: tags can be highlighted in the graph, attachments can be shown alongside their notes, and—crucially—Graph View can surface “existing files only” versus links to non-existent notes. That distinction matters because Obsidian often contains links to notes that haven’t been created yet; turning off “existing files only” reveals those placeholders.

Two relationship-based concepts drive deeper cleanup and discovery: “orphans” and “empty” nodes. Orphan notes are notes with no links pointing to them, meaning they’re disconnected from the rest of the network. Empty notes (the “existing files only” toggle behavior) can still be connected elsewhere, so they’re not the same problem. Groups add color coding by applying rules like “path” and “journal” to create visually distinct clusters, making large graphs readable. Display options control link direction (including double arrows when links are mutual), plus visual tuning such as text fading, note size, and link thickness. Forces adjust spacing so the layout fits the user’s screen and preference.

The creator’s first major use case is visual browsing: assign groups and colors based on filters like file name (e.g., “programming” and multiple MOCs such as history/philosophy). With color-coded clusters, scanning the graph becomes faster than using a traditional folder hierarchy, especially as vaults grow.

The second use case is resuming work where attention left off. One method is a recurring workflow around orphan notes: periodically toggle on orphans, review disconnected drafts, and wait for new notes to create connections over time. Another method uses “existing files only” as a reminder system—turning it off surfaces empty, non-existent, or placeholder notes so forgotten ideas reappear.

The third use case is local navigation inside a note page. Using the command palette to open “Local Graph,” users get a smaller, note-specific network with extra controls: depth (how many layers outward to show), incoming links (which notes point to the current note), outgoing links (which notes the current note links to), and neighbor links (when two connected notes link to each other). This local view effectively replaces the “file explorer” role of folders, offering a relationship-first way to navigate—particularly useful on large screens or dual displays.