Obsidian Quiet Outline: a quieter, searchable outline pane for Obsidian

The pane that stops expanding while you type

The README describes the plugin in one line, an outline plugin makes headings easier to read, and then the first feature in the list is the one the whole project is named for, no auto-expand when editing.

That is a real annoyance in Obsidian. The built-in outline follows the caret, so as you type a heading and then start writing under it, the tree expands underneath you, the list shifts, and the heading you were reading moves. The README puts it plainly with a pair of animated GIFs, one of the default Outline and one of Quiet Outline, and the difference is visible in a second.

The plugin is not a fork of the outline view or a replacement for it in the sense of adding features to Obsidian's own. It is a separate pane, opened from the command palette, that presents the same heading structure with different behaviour. The repository description is Improving experience of outline in Obsidian, the language is TypeScript, the licence is MIT, and there is a Chinese version of the README linked at the top for readers who want it.

The scope is one pane, and the rest of the feature list is the argument for why a separate pane is worth the trouble.

Search, regex and searching through markdown syntax

The search support is the feature list's second entry and the one that goes furthest beyond what the built-in outline does.

The README describes a search box that filters the outline, a way to hide irrelevant results, regex support, and searching content by piercing through Markdown and HTML syntax. That last one is the interesting part. Because the tree is a list of headings, a plain text search matches heading text, but a heading in Obsidian can contain formatting, a link, or a tag, and the text you see is not the text that was typed. Piercing through the syntax means the search runs against the underlying content rather than the rendered label, so a search for a word inside a link still finds the heading.

There is a separate Markdown render support feature as well, which lets a heading in the tree display its markdown rather than its raw text, and the two features together make the tree behave like a preview of the note rather than a list of labels.

The README does not say which search implementation is used or whether the search is scoped to the active note, so if you are evaluating this for a vault with thousands of headings, that is a question to test rather than assume.

Markdown rendering, expansion control and a level switch bar

Three features handle the display of the tree itself.

Markdown render support renders a heading as markdown, so formatting in the heading shows up in the outline. Auto expand and collapse manages which nodes are open, and the Level Switch Bar changes the level at which the tree is expanded, so you can collapse the document down to its top-level sections. There is also a default level option, and the README notes that you can customize the default level per note, pointing at the release notes for version 0.3.33 for the details.

That per-note default is a small feature with a large effect on daily use. A vault where half the notes are meeting minutes with three levels and half are long research documents with six needs a different default in each, and a global setting forces you to adjust it every time you switch notes.

The remaining entry in this group is drag and modify note, which lets you drag a heading to change its level or its position in the tree. Editing structure by dragging in a pane that is not the note itself is a different interaction from editing the note's markdown, and it is the one place where the plugin offers an alternative to typing the structure.

The README shows a short animation for each of these rather than describing them, so the behaviour is best understood by looking at the GIFs in the repository.

Navigation beyond the note: Canvas, Kanban, Bases and PDF

The most recent additions to the feature list are the ones that push the outline outside the current note, and they are the reason to look at the plugin now rather than a year ago.

Navigate in Canvas, Navigate in Kanban and Navigate in Bases are three separate entries. The Bases one is described in the most detail: it lists the rows of the active Bases view, whether that view is a table, cards or a list, following its filters, sorting and grouping, and the property shown per row can be changed in the Bases settings tab. So the outline becomes a navigator for a database view rather than a heading list.

Navigate in PDF supports reading and displaying the table of contents, the outline or bookmarks, embedded in PDF files, with two behaviours: click to jump, where clicking an outline item navigates to the destination page and position in the PDF, and active page sync, which tracks and highlights the corresponding outline heading as you scroll or change pages.

The PDF support is the one that feels like a different product, because a PDF embedded in a vault is not part of the vault's heading structure at all, and giving the outline a view of the document's own bookmarks makes the pane useful for reading a specification rather than only for navigating notes.

The keymap section also notes that the same keys operate a canvas, with J, K, H and L to move to the next node, I to edit a file or text node, Z Z to zoom in a node and Z A to zoom out.

A vim-like keymap for the tree and for the search box

The keymap is the other half of what makes the pane pleasant, and it is documented in full.

When the heading tree has focus, the keys are J and K, and the arrow keys up and down, to move, H and L, and left and right, to collapse and expand, / to focus the search input area, Z Z to centre the heading, G G to go to the top, Shift G to go to the bottom, Space to jump in the note without focusing into it, Enter to jump and focus into the note and clear the search input, and Escape to focus back to the note. When the search area has focus, Escape clears the search input and Enter returns focus to the heading tree.

    + `J` `K` (and ArrowUP ArrowDown) to move down/up
    + `H` `L` (and ArrowLeft ArrowRight) to collapse/expand 
    + `/` to focus search input area
    + `Z Z` to center the heading
    + `G G` to go to top
    + `Shift G` to go to bottom

The Space and Enter distinction is the one worth internalising, because it is the difference between jumping to a heading and jumping into it, which is the difference between reading and editing.

There are also a few plain hotkeys outside the vim map, to increase or decrease the level, to jump to the previous or next heading, and to copy all headings to the clipboard, which the README dates to release 0.3.32. The copy-all-headings one is the kind of small utility that matters when you want to paste a table of contents into a message.

Install by hand or from the community store

Installation is documented in two forms, and the manual one is worth reading because it tells you what the plugin actually is.

For a manual install, you download the latest release, extract it, and put the three files, `main.js`, `style.css` and `manifest.json`, into the folder `{{obsidian_vault}}/.obsidian/plugins/obsidian-quiet-outline`.

That three-file list is the shape of every Obsidian plugin, and it is the reason the plugin is easy to reason about. There is no bundler configuration to satisfy and no runtime dependency to install, because the bundle is what you drop into the vault.

From the community store the route is the usual one:

+ Open Settings > Third-party plugin
+ Click Browse community plugins
+ Search for "Quiet Outline"
+ Click Install

Using the plugin is then a command palette action, and the README says to open the command panel and input Quiet Outline and press Enter. The Markdown Render option is a setting in the settings panel, and it is the one that switches the tree to rendering headings as markdown rather than showing raw text.

The repository carries a manifest.json and a versions.json, which is the pair the release tooling keeps in step, and the package.json version is 1.0.1.

Two documented limitations, and one of them is Obsidian's

The Limitations section is short and both entries are worth reading before you install.

The first is about the editor rather than the plugin. Because of the lazy-rendering strategy of the built-in editor, where only text shown in the current window is rendered, scrolling too fast leaves some text unrendered and the editor stutters, so sometimes you cannot jump to the place you want by one click in edit mode, especially when the note is opened for the first time since the app started. The README says the Outline core plugin has the same issue, and the stated solution is to just click again.

The second is cross-level is not supported, which means you can use h1 to h2 to h3, but not h1 to h3 to h4, while h3 and h4 will be treated as h2 and h3. That is a deliberate simplification of the heading hierarchy, and it will be visible to anyone who skips levels in their notes, which is a habit that is easy to acquire by accident in a long document.

There is a third note about extended grammars. Some extended grammars in Obsidian are not supported by default, but the markdown parser can be extended to fix that, and the README invites an issue if you believe a grammar is frequently used and should be implemented. That is a reasonable way to handle a moving target, and it also means the plugin's markdown fidelity is partly your responsibility.

On maintenance, the repository is not archived, the last push was on 2026-10-19, and the recent releases are 0.5.21 from 2026-10-11, 0.5.20 from 2026-09-17 and 0.5.19 from 2026-09-11, so this is a plugin that is still changing.

Editorial conclusion

Quiet Outline fits an Obsidian user whose outline pane keeps jumping and expanding while they type, and who wants to search and filter headings the way they search notes. It is the wrong choice if you rely on Obsidian's own outline behaviour or need the cross-level jumps the plugin explicitly does not support, since h3 and h4 are treated as h2 and h3. Verify first that your vault uses the heading conventions the plugin expects, because the documented limitation is that some extended Obsidian grammars are not supported by default and need the markdown parser extended by hand.

Frequently asked questions

Official sources

1. guopenghui/obsidian-quiet-outline on GitHub
2. Issues
3. License: MIT
4. README
5. Releases