Notion Boost: a browser extension that adds an outline and 20+ tweaks to Notion

What the extension actually adds

The repository description calls it a Chrome and Firefox extension for Notion that adds 20 or more features, and the blockquote above the title gives the list: sticky outline, which is a table of contents, small text and full width by default, a scroll to top button, hiding the slash command menu, hiding the help button, bolder text, and more.

So the shape of the thing is clear. It is not a client for Notion and not an editor. It is a set of modifications to the Notion.so web interface, applied by a browser extension, and the listed features are almost all about density and about getting to a place in a long page.

The sticky outline is the one that changes how you work rather than how the page looks. Notion pages can be long, and the built-in navigation does not keep a table of contents in view, so you scroll to find the section you want. A pinned outline removes that scroll.

The pair of small text and full width by default addresses the other common complaint about writing in a browser, that the default reading column is narrow and the default type size is large. Bolder text is a third lever on the same axis, since the text weight Notion ships with is light at small sizes.

The remaining features are the removal of things: the slash command menu and the help button take up screen space and are only occasionally wanted. The scroll to top button is the answer to a page that is longer than the outline can cover.

The full feature list is maintained on the project homepage, and the README asks for missing features to be suggested through the repository's issue tracker, so the feature set is expected to grow with what users ask for.

Distributed through both stores, from one source tree

The distribution model is ordinary for an extension of this kind and worth describing because it shapes how you would evaluate updates.

There are two download paths, the Chrome Web Store listing for Chrome, Edge and Brave, and the Firefox add-on listing on addons.mozilla.org. The project homepage is https://gourav.io/notion-boost, which also carries the complete feature list and a page describing what is new in the latest update.

What makes the two builds come from one source tree is the build configuration, and the repository shows it plainly. There is a web-ext.config.ts, a wxt.config.ts, an entrypoints/ directory for the extension entry points, a components/ directory for the React components, styles/ for the stylesheets, public/ for static assets, and an assets/ directory for the images used in the readme.

The build tool is WXT, and the package.json scripts are the clearest description of the workflow.

        "dev": "wxt",
        "dev:firefox": "wxt -b firefox --mv2",
        "build": "wxt build",
        "compile": "tsc --noEmit",
        "postinstall": "wxt prepare",
        "lint": "eslint .",
        "package-chrome": "wxt zip",
        "package-firefox": "wxt zip -b firefox",
        "package": "pnpm run package-chrome && pnpm run package-firefox"

The Firefox development script passes -b firefox and --mv2, so the Firefox build can be developed against the Manifest V2 target as well as the default, which is what Firefox needs for the extension APIs in question.

There is also a dependency update check, check-updates running ncu with the repo and group formats, so a maintainer can see which packages are drifting.

How the extension is put together

The primary language is TypeScript, the licence is GPL-3.0, the default branch is main, and the last push was on 2026-06-03. The recent releases are v3.1.2 from 2022-08-07, v3.1.0 from 2022-05-21 and v3.0.10 from 2022-03-13, and the extension version in the package manifest is 1.0.0, which tells you the manifest version and the store release version are tracked separately.

The runtime dependencies are React and react-dom at 18.3.1, and nothing else. That is a deliberate and meaningful choice for a Notion extension, because Notion itself is a React application and a React component can be mounted into the host page's tree and inherit its context. The alternative, injecting DOM nodes from outside, is more fragile.

The build tooling is extensive. WXT at 0.19.11 is the extension framework, and it comes with a React module in @wxt-dev/module-react. The linting is ESLint 9 with the typescript-eslint 8 plugins, the import, promise, react and react-hooks plugins, and prettier with eslint-config-prettier and eslint-plugin-prettier so that formatting and linting do not fight.

The styling is Sass, with sass at 1.70.0, sass-loader and style-loader, and prettier-plugin-tailwindcss in the formatting set. The presence of a Tailwind plugin in the formatting chain while Tailwind itself is not a dependency is worth noticing: it suggests the CSS conventions of the project follow Tailwind's class naming, and the styles directory holds the actual stylesheets.

The type checking is separate from the bundling, with the compile script running tsc --noEmit, so type errors fail the build without emitting anything.

What breaks when Notion ships a redesign

There are three limits, and the first one is structural and unavoidable for this class of software.

The first is that the extension works against another company's interface. Notion's web client is not a stable API, it is a React application that the vendor changes, and a modification that relies on a particular element, class name or layout will stop applying when that changes. A sticky outline is a reasonable bet because the page structure changes less often, but a bold text override tied to a specific selector is a bet on markup.

That is also why the release history looks the way it does. The tagged releases stop in 2022 while the last push is in 2026, which is the signature of a project where the work is a series of small adjustments against a moving target rather than a sequence of releases with new capabilities.

The second is that the extension only helps inside the browser and only on the web version of Notion. The desktop application and the mobile applications are not covered, and a team standardised on the desktop client gets none of this. That is a meaningful limit for anyone whose working day is spent in the Notion desktop app.

The third is the trust question, and it is the one people ask about extensions. The code is GPL-3.0 and the source is in the repository, which is a meaningful mitigation, but a browser extension that injects code into a page where you type passwords and company documents is a privileged position, and the honest way to evaluate it is to read the entrypoints and components rather than to trust the store listing.

The project keeps a HELP.md, an .eslintrc.json, a .hintrc and a .prettierignore alongside the code, which is the profile of a project with some tooling discipline but without a build guide aimed at contributors.

How it compares with the alternatives

The realistic alternatives split into two groups, and neither replaces this for the same job.

The first group is doing it inside Notion itself. Notion has a settings panel, and a workspace owner can configure those for the whole team without anyone installing anything. The difference is that the built-in controls are one setting at a time and are not sticky, and a Notion Boost user gets a persistent outline that does not scroll away. If the annoyance is density rather than navigation, the native settings may already be enough.

The second group is a custom script or a user style injection, which is what several Notion power users do with a personal CSS file or a Tampermonkey script. The difference in approach is ownership. A custom style is entirely under your control, it is as small as the handful of rules you need, and it breaks in exactly the same way, since it also targets Notion's markup. What you give up is the twenty-plus features that have already been worked out, and the fact that the fixes are in one maintained place rather than in a config file you have to keep in sync.

The honest summary is that Notion Boost is a packaged answer to a set of specific annoyances, maintained by one person, with the maintenance burden of following a third party's interface. It is a good fit for a Notion-heavy individual or team that has decided those annoyances are worth solving, and a poor fit for an environment where the desktop app is mandatory or where a native Notion setting would do.

Editorial conclusion

Adopt Notion Boost if you spend your day in Notion and want an always-visible outline, denser text and a wider reading area without rebuilding your workspace, since those are the features it exists to add. Do not adopt it if you need something Notion has not shipped, because the extension works against the current Notion interface and breaks when that interface changes. Before you install, read the list of currently added features on the project homepage, and note the last push was on 2026-06-03 with the last tagged release v3.1.2 from 2022.

Frequently asked questions

Official sources

1. GorvGoyl/Notion-Boost-browser-extension on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases