Natsumi Browser skins Firefox from the inside with chrome CSS

Natsumi is a skin for Firefox, not a browser of its own

The README is explicit about this and the distinction decides whether the project is useful to you. Natsumi is a skin made for Firefox and its forks that adds polish to the design and new features to the browsing experience. It is not a standalone browser. It is meant to be applied on top of your favourite Firefox-based browser.

That means there is no executable to download and no engine of its own. The repository is mostly stylesheets and a theme descriptor: userChrome.css and userContent.css at the top level, a natsumi-config.css for configuration, a theme.json, a natsumi directory with the rest of the assets, and an installer folder with platform specific helpers. The primary language of the repository is CSS.

The audience is a Firefox user who wants a different looking browser without leaving the browser they already have, plus its profile, extensions and history. If you were hoping for a fork with a new engine feature, this is the wrong shape of project.

The line between CSS-only and the JavaScript add-on

Some Natsumi features work with pure CSS. Others need a companion piece called Natsumi Append, and the README publishes a table that separates the two columns. The URL bar and findbar, the PDF viewer and the theming engine work in CSS-only mode. Picture-in-picture works, but the table marks it as limited there.

The features that do not survive without JavaScript are the Miniplayer, the customize page for Natsumi preferences, custom themes, Single Toolbar, Compact Mode, the Natsumi toolbars and the Natsumi shortcuts.

That is a large share of the headline features, and it changes what installation means in practice. A CSS-only install gives you a repainted browser; a full install adds an append layer that enables the layout features and the preferences pane. The README states that you can use Natsumi without JS support at the cost of losing some features, and the table is the exact list of what that costs.

One line in the README also draws a line in the sand for CSS-only users: there are no best practices or authoritarian design ideologies, in the words of the project, and the customisation options are meant to be taken apart.

Installing means copying files into the profile chrome folder

The documented install method is manual in the sense that you place the files yourself in the chrome folder of your browser profile. Automatic installers exist for the platforms that need them.

From version 5 onwards, every release ships an installer binary that can install Natsumi Browser, Natsumi Browser Pages and Natsumi Append into the browser and profile of your choice. On macOS and Linux the binary may need execute permission before it runs:

chmod +x /path/to/installer

macOS users may also have to override the unsigned binary warning through System Preferences, Security & Privacy, and the README flags Flatpak installations as a special case: they need a manual install for Natsumi to be functional, which points back to copying the files into the profile.

Windows is handled by a batch file called windows-installer.bat, taken from the Installers folder in the repository. It has to run as Admin because it copies files to system locations, and updating means running it again with the browser closed. A Sine installation path is also mentioned in the README, though the visible documentation for it is cut off in the part available here.

The URL bar and the preferences pane define the customisation surface

Two features carry the design work. The URL bar gets a new treatment in which the current address stands out and the colours change dynamically depending on context. The second is a dedicated preferences pane where almost all customisation options live, so you do not have to edit advanced preferences by hand.

The theming engine is listed as working in CSS-only mode, and custom themes are not, which is an odd split: the mechanism that applies a theme is available without JavaScript, while shipping your own theme is a full-install feature.

The file layout explains the mechanics. userChrome.css styles the browser interface, userContent.css styles the pages, natsumi-config.css holds configuration, and theme.json is the theme descriptor. The installation step is the part that matters: copying these files into a profile's chrome folder means your changes live in the profile, so a profile reset removes them and a browser update may overwrite them depending on how you installed.

For users of browsers with their own extras, the README shows browser specific goodies on top of the shared skin.

Single Toolbar and Miniplayer are the features you lose without JavaScript

Single Toolbar merges the navigation bar into one unified sidebar to reclaim vertical space, and the README states that the Multiple Toolbars layout stays available if you prefer it. That is a layout choice you would otherwise get from a browser that ships vertical tabs natively, and Natsumi implements it as a skin instead.

The Miniplayer moves media control to the sidebar, and the README says it supports several websites at once so tabs do not compete for a spot. Picture-in-picture is restyled to match the rest of the interface, and you can scroll to reposition the PiP window.

The PDF viewer is refreshed, including a compact view for focusing on the document without the extra tools. Shortcuts can be customised, including how conflicts between browser shortcuts and website shortcuts are handled, which the README presents as removing the need to defer to websites.

All of these except the PiP restyling sit on the JavaScript side of the table. Single Toolbar, the Miniplayer, the shortcuts and Compact Mode are the reasons a CSS-only copy of Natsumi will feel like a different, thinner product.

Maintenance mode runs from August 2026 to June 2028

The most important line for anyone planning to use this as a daily driver is the notice at the top of the README. The project states it is in maintenance mode from 2026-08-30 to 2028-06-01, that the author's best effort will keep Natsumi stable and alive, and that features released may be infrequent or entirely halted during that period. The README adds that the project is not dead and will stay alive for the foreseeable future.

The release history is consistent with a maintenance posture rather than a shutdown. Version 6.12.2 was published on 2026-08-29, 6.12.3 on 2026-10-02 and 6.12.4 on 2026-10-09, and the last push to the default branch was on 2026-10-09. So bug fixes and adjustments are still arriving on a patch cadence, while the feature roadmap is explicitly paused.

For a user this is a reasonable trade: the skin keeps working, and the risk is that a future Firefox release changes the internal interface the stylesheets target. That risk is real for any chrome CSS project, and the maintenance window means you should not wait for a feature you are planning around.

What a skin cannot change, and what the licence requires

The boundary of this approach is worth stating plainly. Natsumi restyles the interface of a browser you already run. It does not change how pages load, how JavaScript executes, or what the browser does with permissions. Any feature that needs a different engine or a different extension API is out of reach, which is exactly why the Miniplayer and the shortcut conflict handling need an append layer.

There is also a practical upgrade cost. Since the files sit in a profile, you reapply them on every update, and the Windows path makes that explicit by asking you to run the batch file again with the browser closed. Flatpak users do it by hand. The README does not describe a rollback procedure, so keep your own copy of the files if you care about reverting.

The repository is licensed GPL-3.0, and it ships a SECURITY.md alongside a code of conduct. The licence terms matter for redistribution: a copy of the skin that you distribute to others is a derived work of GPL-licensed code, which carries source availability obligations. That is a licensing fact rather than legal advice, and it applies in particular if you plan to publish your own theme built on top of the stylesheets.

Editorial conclusion

Natsumi suits a Firefox user who wants a different looking browser, a single toolbar layout and a URL bar that highlights the current address, and who is willing to keep the profile chrome folder in sync with releases. It does not suit anyone who wants a separate browser, offline behaviour in the miniplayer or the preferences page, or a guarantee that a Firefox update will not break the layout. Before installing, read the maintenance notice, because the project states it is in maintenance mode from 2026-08-30 to 2028-06-01 and that features may be infrequent or halted, then check the table of CSS-only features so you know which parts of the skin will stay with you if you skip Natsumi Append.

Frequently asked questions

Official sources

1. greeeen-dev/natsumi-browser on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases