# Min Browser Review: A Minimal Electron Browser With Full-Text History Search

> Min is an Electron-based browser that trades extension ecosystems and sync for a distraction-free interface, built-in ad blocking, reader view and full-text search over visited pages. Here is how it installs, how it is built, and where it stops being the right tool.

**minbrowser/min** — A fast, minimal browser that protects your privacy

- Repository: https://github.com/minbrowser/min
- Website: https://minbrowser.org/
- Stars: 9,192 · Forks: 868
- Language: JavaScript
- License: Apache-2.0
- Published: 2026-09-21 · Updated: 2026-09-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/minbrowser-min

## What Min Solves, and Who It Is Actually For

Most browsers are built to hold you in a session: pinned tabs, a news feed on the new tab page, a profile that syncs everywhere. Min goes the other direction. The README describes it as "a fast, minimal browser that protects your privacy" with "an interface designed to minimize distractions." The feature list that follows is short and specific: full-text search for visited pages, ad and tracker blocking, automatic reader view, tasks (tab groups), bookmark tagging, password manager integration, and a dark theme.

The full-text search is the part that does not exist in most mainstream browsers. Instead of matching only page titles and URLs, Min indexes the text of pages you have visited and lets you search that index. That changes the browser from a place you keep tabs open into a place you query. If you read long documentation during the day and later need the sentence that explained a config key, that is the workflow Min is designed around.

The audience follows from that. Min is for people who treat the browser as a reading and research tool rather than an app platform. It is also for users who want blocking and reader mode on by default instead of installed as add-ons. It is not aimed at someone whose daily work happens inside a dozen Chrome extensions, because Min does not offer that ecosystem. It has userscripts instead, documented in the project wiki.

## Electron, a Local Index, and Userscripts Instead of Extensions

The repository layout and package.json make the architecture legible. Min is an Electron application: package.json pins "electronVersion": "43.4.1", the entry point is main.build.js, and the source is split across main/, js/, pages/, css/, reader/ and ext/. The build step compiles the source into the files Electron loads, which is why development mode runs a build before starting.

The data layer is local. Dexie is a dependency, which is a wrapper around IndexedDB, and the full-text search features are backed by that plus a set of text-processing packages: stemmer, quick-score, and papaparse for CSV import. Nothing in the dependency list is a hosted service. There is no account system in the README, no sync server, and no telemetry dependency. Search over your history happens against data the browser already stores on your machine.

Extensibility is the deliberate trade-off. Min does not advertise Chrome extension support. It supports userscripts, which the wiki documents, and the ext/ directory holds the built-in extensions that provide features like blocking. A userscript can modify pages, but it does not get the same API surface as a Chrome extension, and there is no Chrome Web Store equivalent. That is the cost of the smaller surface area.

Reader mode, translation and PDF handling are also bundled rather than delegated. The dependency list includes pdfjs-dist for PDF rendering and @browsermt/bergamot-translator for on-device translation, which fits the local-first stance: translation runs in the browser rather than sending page text to a server.

## Installing Min on Linux and Running It From Source

The README points to prebuilt binaries on the GitHub releases page rather than a package repository for most platforms. On Linux it gives package-manager commands directly. The .deb install uses dpkg, and the RPM build uses rpm with the --ignoreos flag, which the README includes because the package metadata does not always match the host distribution:

```bash
sudo dpkg -i /path/to/download
sudo rpm -i /path/to/download --ignoreos
```

Arch Linux users are directed to the AUR package min-browser-bin, and Raspberry Pi users to Pi-Apps. There is no apt repository or Homebrew tap in the README, so upgrades on Debian and RPM systems mean downloading a new file and repeating the command.

For development, the README gives a short sequence. Node must be installed first, then dependencies, then the development start script:

```bash
npm install
npm run start
```

After a change, the README says to reload the browser UI with alt+ctrl+r, or opt+cmd+r on macOS. Building distributable binaries uses platform-specific scripts, and the README warns that macOS builds need Xcode and may need the SDK path set explicitly:

```bash
export SDKROOT=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk
npm run buildMacArm
```

The available build scripts are buildWindows, buildMacIntel, buildMacArm, buildDebian, buildRaspi, buildLinuxArm64 and buildRedhat. Windows builds require Visual Studio, and the README notes that you may need to run npm config set msvs_version 2019. One detail worth knowing before you start: package.json defines a postinstall script that runs node ./scripts/setupDevEnv.js, so npm install does more than fetch packages.

## Where Min Is the Wrong Tool

The clearest limitation is the extension model. If your workflow depends on a password manager that ships only as a Chrome extension, a screen reader extension, or a corporate SSO extension, Min will not run it. The README lists password manager integration as a feature, but it does not describe the mechanism, and userscripts are not a drop-in replacement for the Chrome extension API. Verify your specific manager against the wiki before committing.

Mobile is the second gap. The related searches around "Min browser Android" and "Min Browser APK" suggest people look for it, but the README documents desktop installation and build targets only: Windows, macOS, Debian, Red Hat, and ARM Linux. Nothing in the README describes an Android or iOS build. A browser without a mobile counterpart also means no cross-device history, so the full-text index stays on one machine.

Upgrades are manual on most Linux distributions. Because the README points to downloaded packages rather than a maintained apt or dnf repository, security updates arrive when you notice a new release, not when your package manager runs. On a browser, that matters more than on most software.

The maintenance picture is mixed but not alarming. The repository is not archived, and the last push to master was on 2026-08-30, with v1.35.7 released on 2026-08-23. That is recent activity, but the release cadence visible in the provided list is irregular: v1.35.6 landed on 2026-07-06 and v1.35.5 on 2026-04-12. There is no published security audit in the README, and SECURITY.md exists in the repository root without its contents being reproduced here, so read it yourself if threat model matters.

## Min Compared With Firefox and Chromium-Based Browsers

The honest comparison is not Min versus Chrome on features, because Min loses that on purpose. It is Min versus Firefox with uBlock Origin, or versus a Chromium build with a reader-mode extension.

Firefox gives you the extension ecosystem, a mobile browser, account sync, and a long public track record of security response. To match Min's core feature you would add an extension that indexes page text, and you would manage blocking and reader mode as add-ons. The result is more capable but also more configuration, and the history search depends on a third-party extension with its own data handling.

A Chromium-based browser gives you compatibility with corporate sites and the Chrome extension API. It also gives you a much larger codebase and, in most distributions, the same telemetry defaults you were trying to avoid.

Min's difference is that the useful features are defaults rather than add-ons, and the search index is local. That is a real distinction, not a marketing one, and it is the reason to pick Min. The reason not to pick it is equally concrete: fewer extensions, no mobile build in the README, and no package repository for automatic updates on Debian and RPM systems.

## Licence, Forking and the Cost of Staying Current

Min is licensed under Apache-2.0, stated in package.json and in LICENSE.txt at the repository root. That is a permissive licence: you can use, modify and redistribute the code, including in commercial contexts, provided you keep the licence and notice files and state significant changes. It also includes an explicit patent grant, which the MIT licence does not. None of this is legal advice; read LICENSE.txt and, for a commercial redistribution, get your own review.

The practical implication for a team is that forking is legally straightforward. If a feature you need is missing, the source is available under terms that permit a private fork. The engineering cost is the real constraint: Min is an Electron app with a build pipeline of its own, and keeping a fork current means merging upstream changes across main/, js/ and pages/ while the Electron version pinned in package.json moves.

Upgrade cost for ordinary users is low in effort but manual in timing. There is no auto-update channel described in the README. The release list shows three releases between April and August 2026, so a user who checks quarterly will usually be a version or two behind, and a user who never checks will stay on whatever they installed. On a browser, that is the cost that deserves the most attention.

## Conclusion

Min suits engineers who want a second browser with local full-text history search and no account, and who are comfortable installing from GitHub releases or building with npm. It is the wrong choice if you depend on Chrome extensions, need mobile sync, or want a vendor that publishes a security audit. Before adopting it, check whether the release page lists a build for your platform and whether the last push date on the master branch is recent enough for your risk tolerance; the repository is not archived, and the last push was on 2026-08-30.

## FAQ

### Is Min browser safe?

The README does not make a security claim beyond describing Min as a browser that protects your privacy, and it does not link to an audit. The repository includes a SECURITY.md file, so that is the place to read the project's own reporting process before deciding.

### How to install min browser?

The README directs you to the GitHub releases page for prebuilt binaries. On Linux it gives sudo dpkg -i /path/to/download for the .deb file and sudo rpm -i /path/to/download --ignoreos for the RPM build, with AUR package min-browser-bin on Arch Linux and Pi-Apps on Raspberry Pi.

### Can I download a mini browser app?

Min is distributed as a desktop application, and the README documents downloads for Windows, macOS, Debian, Red Hat and ARM Linux. It does not describe an Android or iOS build, so a phone app is not covered by the documentation.

### What is the best minimal browser for Windows?

The README does not compare Min with other browsers, so it makes no claim about being the best on Windows. It does note that building Min on Windows requires Visual Studio and possibly npm config set msvs_version 2019, while prebuilt binaries are available from the releases page.

## Sources

- [License: Apache-2.0](https://github.com/minbrowser/min/blob/master/LICENSE)
- [minbrowser/min on GitHub](https://github.com/minbrowser/min)
- [Project website](https://minbrowser.org/)
- [README](https://github.com/minbrowser/min/blob/master/README.md)
- [Releases](https://github.com/minbrowser/min/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/minbrowser-min