Get AI summaries of any video or article — Sign up free
The Obsidian Feature You Didn’t Know You NEEDED thumbnail

The Obsidian Feature You Didn’t Know You NEEDED

FromSergio·
5 min read

Based on FromSergio's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Enable Bookmarks from Settings → Core Plugins, then create bookmarks via the top-right button or the command palette (Command P).

Briefing

Obsidian’s new Bookmarks feature turns “start notes” into a flexible workspace layer—letting users save not just notes, but graph filters, searches, canvases, headings, and even attachments as quick-jump items. The payoff is practical: a dedicated bookmarks pane becomes a distraction-free control panel for whatever work is active, while the underlying files keep their original names and remain fully accessible in the vault.

At its core, Bookmarks replaces the older Start Notes core plugin. Instead of a note automatically living in its own Start Notes view, Bookmarks creates bookmark entities that can be titled independently of the original file. That small detail matters when context changes: a note titled “April monthly newsletter” can be bookmarked under a project-specific label like “Next newsletter,” without renaming the real file on disk. Bookmarks also behave like temporary focus tools. They can be reordered by drag-and-drop, revealed in file navigation, and removed without deleting the underlying content—so users can “laser focus” on the current task and discard the bookmark later.

Beyond basic note pinning, Bookmarks adds structure through bookmark groups, including nested folder-like organization. Users can create groups such as “April To Do’s” and assign bookmarks into those groups, effectively building a folder hierarchy inside the bookmarks pane. This becomes especially useful for graph view workflows. Previously, graph filters had to be rebuilt every time; now graph view configurations can be saved as bookmarks with their own titles, groups, and color-coded queries. A saved graph filter can exclude entire folders (like journaling), hide specific paths (like books), omit tags (such as “mocks”), and limit results to existing files—then be recalled instantly.

The same saving logic extends to other navigation surfaces. Searches can be bookmarked so a complex query returns with one click. Canvases can be saved as bookmarks, letting users jump back to a specific visual workspace (for example, a canvas tied to a YouTube video). Even headings inside notes can be bookmarked, so navigation lands on the exact section rather than the top of the document. The feature is broad enough to include attachments like images or PDFs, and it can also “bookmark all tabs” (active notes) via the command palette.

In personal use cases, the feature becomes a project manager. Permanent graph view bookmarks live in a dedicated “graph views” group, while active work sits in project-specific folders—such as a studio renovation project, each YouTube video’s script and canvas, and an ongoing effort to use AI across a vault without sending data to OpenAI. When projects finish, bookmarks are deleted while the final outputs remain, keeping the left-side UI focused on what’s currently worth attention. The result is a workflow where the bookmarks pane stays open, enabling quick switching between projects and frequent revisiting of goals—without relying on a massive file list.

Cornell Notes

Obsidian Bookmarks upgrades the older Start Notes idea into a system for saving “work contexts” as quick-jump items. Bookmarks can be titled independently of the original file, can be grouped into folder-like structures, and can be removed without deleting the underlying content—making them ideal for temporary focus. The feature also saves complex graph view filters, searches, canvases, and even specific note headings, so users can return to the exact view they were using. For active projects, keeping the bookmarks pane open turns it into a lightweight dashboard that replaces scrolling through the vault. When work ends, bookmarks can be discarded while final notes remain, keeping the interface clean and task-relevant.

What makes Bookmarks more than a simple “pin a note” feature?

Bookmarks create bookmark entities that can be titled independently of the original note’s filename. They can be organized into bookmark groups (folder-like structures), reordered via drag-and-drop, and removed without deleting the underlying vault content. That combination supports both context-specific naming (e.g., labeling a note by what it means in a current project) and temporary workflows (discard bookmarks when a project ends).

How does independent bookmark titling work in practice?

A real file keeps its original title in the vault, even if the bookmark uses a different name. For example, a note titled “April monthly newsletter” can be bookmarked as “Next newsletter.” Clicking the bookmark navigates to the same underlying note, but the bookmarks pane shows the project-appropriate label.

Why are saved graph view bookmarks a workflow upgrade?

Graph view filters previously had to be rebuilt each time, which was time-consuming and error-prone. With Bookmarks, a configured graph view—such as excluding journaling notes by path, excluding books by path, hiding a specific tag like “mocks,” and limiting to existing files—can be saved as a bookmark. Resetting the graph and returning to the saved bookmark restores the exact filter instantly, with optional query-based colors.

What other Obsidian elements can be bookmarked besides notes and graph views?

Bookmarks can be saved for searches (reusing complex search queries), canvases (jumping back to a specific visual workspace), and note headings (right-click a header and bookmark it so navigation lands on that section). The system can also bookmark attachments like images or PDFs, and it includes a “bookmark all tabs” command to capture currently open notes.

How does the feature support project-based organization without clutter?

Active work gets its own bookmark folder (e.g., one folder per YouTube video containing its canvas, script note, and topic connections). When the project finishes, the bookmarks are deleted while the final outputs remain. Keeping the bookmarks pane open means the left-side UI shows only what’s currently relevant, reducing reliance on a large file list.

Review Questions

  1. How does independent bookmark titling help when the meaning of a note changes across different projects?
  2. Describe two ways saved Bookmarks reduce repeated setup work in Obsidian (one should involve graph view or search).
  3. Why might someone prefer deleting bookmarks after a project ends rather than keeping them indefinitely?

Key Points

  1. 1

    Enable Bookmarks from Settings → Core Plugins, then create bookmarks via the top-right button or the command palette (Command P).

  2. 2

    Bookmark titles can differ from the underlying file title, letting users label content by current project context without renaming vault files.

  3. 3

    Use bookmark groups to organize bookmarks into folder-like structures, including nested group organization.

  4. 4

    Save graph view filters as bookmarks to avoid rebuilding complex include/exclude queries every time.

  5. 5

    Bookmark searches, canvases, and specific headings to jump directly to the exact view or section needed.

  6. 6

    Remove bookmarks freely when projects end; the underlying notes, headings, and attachments remain in the vault.

  7. 7

    Keep the bookmarks pane open as a project dashboard to switch tasks quickly and revisit goals without scanning the full file list.

Highlights

Bookmarks can be named for the task at hand while the original note title stays unchanged in the vault.
Saved graph view filters eliminate the need to recreate graph settings repeatedly—path exclusions, tag exclusions, and orphan handling can be recalled instantly.
Headings and canvases can be bookmarked, enabling navigation to a specific section or visual workspace rather than just the top of a note.
The workflow treats bookmarks as disposable focus containers: delete them when done while keeping final outputs.
A “bookmark all tabs” command captures currently active notes so returning to a working set takes one action.

Topics

  • Obsidian Bookmarks
  • Graph View Filters
  • Saved Searches
  • Canvases and Headings
  • Project Workflow