nerdyslacker/desktop-web-browsers: A Curated Index of 280 Desktop Browsers

Developers, security researchers, and browser enthusiasts often struggle to keep track of the rapidly expanding landscape of desktop web browsers. With new entrants built on Chromium, Gecko, WebKit, and custom engines appearing regularly, finding authoritative, structured information about what's available—and what's worth evaluating—becomes a research project in itself. The nerdyslacker/desktop-web-browsers repository addresses this gap directly: it's a meticulously maintained, alphabetically organized catalog of 280 desktop web browsers, complete with technical specifications, engine details, platform support, and critical status annotations like [Archived], [Discontinued], and [Coming Soon].

This article examines what makes this curation valuable, how to navigate its structure, and why it serves as an essential reference for anyone making browser-related technical decisions.

What is nerdyslacker/desktop-web-browsers?

nerdyslacker/desktop-web-browsers is an open-source reference repository maintained by GitHub user nerdyslacker with contributions from norafroud, CostcoFanboy, anuragrao04, niutech, and harys722. As of the latest commit on 2026-07-08, the repository has accumulated 578 stars and 49 forks, with HTML as its primary language—reflecting its nature as a structured document rather than executable software.

The repository's core value proposition is completeness with curation. Unlike automated scrapers or wiki pages prone to stale information, this list combines breadth (280 entries spanning numerals A-Z) with editorial judgment. Each browser entry includes four standardized data points: Browser Name (with hyperlink), Engine, Operating System, and Description. Status flags warn users about discontinued projects, archived codebases, or unreleased software—critical context for developers evaluating dependencies or researching browser diversity.

The repository's relevance stems from several industry trends: the fragmentation of browser engines beyond the Chromium/Blink monoculture; renewed interest in privacy-focused and minimal browsers; the emergence of AI-integrated browsing experiences; and ongoing maintenance of legacy systems requiring specialized browsers like K-Meleon (Windows) or r3dfox (Windows XP/7/8). For developers building cross-browser testing pipelines, security researchers analyzing fingerprinting surface area, or system administrators selecting deployment candidates, this single reference eliminates hours of scattered research.

Key Features

Structured Alphabetical Organization The repository divides browsers into 27 sections: [0-9] for numerically named entries, followed by A through Z. Each section begins with an anchor-linked navigation header, enabling rapid jumps without scrolling through hundreds of entries. The alphabetical index repeats at the bottom of the document for bidirectional navigation.

Standardized Technical Metadata Every entry follows a consistent four-column table format:

• Engine: Specifies core rendering engines—Blink, Gecko, WebKit, Chromium (the full browser project), Electron (Chromium-based framework), QtWebEngine, Goanna, Servo, Custom, or proprietary engines. This granularity matters: "Chromium" indicates a full-fork relationship, while "Blink" may indicate a slimmer derivative.
• Operating System: Documents platform support precisely, including niche targets like BSD, Haiku, RISC OS, ChromeOS, and legacy Windows versions.
• Description: Provides concise characterizations, often quoting project taglines directly.

Status Annotations Critical editorial flags appear inline:

• [Archived]: Codebase preserved but inactive (Beaker Browser, Kaktus, Turbo)
• [Discontinued]: Project terminated (Camino, Ghostery Browser, Opera Crypto Browser)
• [Coming Soon]: Announced but unreleased (Bushido Browser, Dia, Quetta Browser)
• [Experimental]: Early-stage, unstable (Helix)

Engine Diversity Coverage The catalog deliberately includes non-mainstream engines: Ladybird (SerenityOS's LibWeb/LibJS), NetSurf (own engine for retro platforms), Chawan (terminal custom engine), FixBrowser (scratch-built for Windows/Linux/HaikuOS), and Mozilla's Servo research engine (Servo Tech Demo, Verso).

Supplementary Tools Section Beyond browsers, the repository lists related utilities: Browser Tamer (Windows proxy for routing links to specific browser profiles) and OneLaunch (Windows 11 desktop integration).

Use Cases

Cross-Browser Testing and Compatibility Research QA engineers and frontend developers can identify browsers representing specific engine families for test matrix expansion. Need to verify behavior on a non-Blink Chromium derivative? Check Ungoogled Chromium, Brave, or Thorium. Testing WebKit outside Safari? Evaluate Orion Browser, Midori, or GNOME Epiphany.

Privacy and Security Tool Selection The engine and description columns enable rapid filtering for privacy-focused candidates. LibreWolf and Mullvad Browser (Gecko-based), Brave (Blink with tracker blocking), BadWolf (WebKitGTK+ minimalist), and Ghostery Browser (discontinued but historically significant) are identifiable at a glance. Security researchers can trace the proliferation of anti-detection browsers (Cloak Browser, Sphere Browser, Ultimatum) or evaluate terminal-based options (Browsh, Carbonyl, w3m) for reduced attack surface.

Legacy System Maintenance Organizations maintaining older hardware find explicit support annotations: Mypal Browser and K-Meleon for Windows XP, r3dfox for Windows 7/8, Arctic Fox for Mac OS X 10.6+, and PowerFox Browser for Mac OS X 10.4-10.6 PowerPC/Intel. This prevents wasted evaluation time on incompatible candidates.

AI-Integrated Browser Evaluation The 2024-2025 wave of AI browsers is documented: Arc Browser (user-centric redesign), Dia ("entirely new environment"), ChatGPT Atlas, Comet (Perplexity's "agentic search"), Fellou ("world's first agentic AI browser"), Genspark AI Browser, Neo (Norton), Sigma AI Browser, Synth, and Taktak. Researchers tracking this segment can compare claims and engine choices systematically.

Decentralized and Web3 Browser Research Specialized entries cover peer-to-peer and blockchain browsing: Agregore (distributed web), Beacon Browser (decentralized internet), dBrowser and Decentr (Web3), PeerSky (peer-to-peer, local-first), and Unstoppable Blockchain Browser (decentralized web domains).

Installation & Setup

The nerdyslacker/desktop-web-browsers repository requires no installation—it functions as a reference document accessible directly through GitHub's web interface or via local clone for offline use.

View Online (Recommended) Navigate directly to the rendered README:

# No commands needed; open in browser
https://github.com/nerdyslacker/desktop-web-browsers

Clone for Offline Reference

# Clone the repository locally
git clone https://github.com/nerdyslacker/desktop-web-browsers.git

# Enter directory
cd desktop-web-browsers

# Open README in default viewer (Linux/macOS)
open README.md

# Or use any Markdown↗ Smart Converter viewer/editor

Fork for Custom Curation

# Fork via GitHub web interface, then clone your copy
git clone https://github.com/YOUR_USERNAME/desktop-web-browsers.git

The repository contains no build system, dependencies, or executable code. Its HTML classification reflects GitHub's linguist detection of the Markdown-rendered output rather than actual HTML source complexity. Contributors submit changes via standard GitHub pull request workflow against the single README.md file.

Real Code Examples

The repository contains no executable code or configuration examples—by design, it is a structured data reference rather than a software package. However, the Markdown source demonstrates effective patterns for maintainable technical documentation that developers can adapt.

Anchor Link Navigation Pattern The README implements bidirectional alphabetical jumping using HTML anchor tags within Markdown:

[0-9](#0-9) | [A](#A) | [B](#B) | ... | [Z](#Z)

## 0-9 — Numerically Named Browsers

| Browser Name | Engine | Operating System | Description |
|--------------|--------|-------------------|-------------|
| <a id="0-9"></a> [115 Browser](https://pc.115.com/browser.html) | Blink, WebKit | Windows, macOS | Developed by 115.com |

The <a id="0-9"></a> anchor enables the table-of-contents links to scroll precisely to section headers, even within GitHub's rendered Markdown where native header anchors can conflict with special characters.

Status Flag Inline Annotation

| [Beaker Browser](https://github.com/beakerbrowser/beaker) | Blink | Linux, Windows, macOS | Experimental peer-to-peer Web browser **[Archived]** |

The [Archived] flag appears directly in the description cell, ensuring status visibility without requiring additional columns that would widen tables excessively on mobile displays.

Multi-Engine Notation

| [Lunascape Browser](https://www.lunascape.org/browser/phoebe) | Trident, Gecko, WebKit | Windows | Supports three different web engines |

Engine entries use comma-separated values when browsers support multiple rendering engines, either natively or through compatibility modes—critical information for testing scenarios.

These patterns reflect pragmatic documentation engineering: maximizing information density while preserving scannability across device sizes.

Advanced Usage & Best Practices

Filtering by Engine for Research Cohorts Use browser find (Ctrl+F / Cmd+F) with engine keywords to rapidly isolate comparison groups. Searching "Gecko" surfaces Firefox derivatives and independent implementations; "Electron" identifies Chromium-based wrappers that may carry higher memory overhead; "Custom" or "Proprietary" flags engines requiring specialized compatibility testing.

Evaluating Status Flags Before Dependencies Treat [Discontinued] and [Archived] entries as historical references only—do not integrate into production workflows. [Coming Soon] entries warrant monitoring but not planning. The [Experimental] label (currently Helix) indicates APIs and behaviors may change unpredictably.

Cross-Referencing with Security Advisories The repository does not track CVEs or update cadence. After identifying candidate browsers, verify maintenance status through:

• Commit frequency on linked repositories
• Release date of latest version
• Security advisory pages for engine families (Chromium security tracker, Mozilla security advisories)

Contributing Corrections or Additions The repository accepts contributions via GitHub pull requests. Given the maintainer's active update pattern (latest commit July 2026), submissions for new browser launches or status changes are likely to be reviewed promptly. Include primary source links in descriptions to accelerate verification.

Comparison with Alternatives

Trade-offs: Wikipedia offers broader platform coverage but lacks the editorial rigor of per-entry status flags and engine granularity. AlternativeTo.net emphasizes user reviews over technical specifications. Can I Use and Browserslist serve different purposes entirely—feature detection rather than browser discovery. The nerdyslacker/desktop-web-browsers repository occupies a specific niche: comprehensive, technically detailed, actively maintained desktop browser reference with explicit lifecycle annotations.

FAQ

Is this a software package I can install? No. It is a curated reference document listing 280 desktop web browsers with technical metadata. There is no executable code.

How current is the information? The last commit was 2026-07-08. Browsers marked with dates or version numbers in descriptions may have newer releases; verify through linked project pages.

Can I use this for commercial browser selection? Yes, but treat [Discontinued] and [Archived] entries as excluded, and independently verify security update policies for any candidate.

Why are some entries marked "considered as malware"? The Citrio Browser entry carries this editorial warning based on community-reported behavior. This reflects maintainer judgment, not automated detection.

Does the repository include mobile browsers? No. The scope is explicitly desktop web browsers. Some entries note iOS engine variants (WebKit on iOS for Brave, Opera) where relevant to desktop development.

What license covers this list? The repository specifies "Not specified" in its GitHub metadata. Treat content as all-rights-reserved unless the maintainer clarifies otherwise.

How can I contribute a missing browser? Submit a pull request to the GitHub repository with the standard four-column table format and verified primary source link.

Conclusion

nerdyslacker/desktop-web-browsers fills a genuine need in the developer tooling landscape: a single, authoritative, technically detailed reference for desktop browser diversity. Its 578 stars and 49 forks reflect organic utility rather than marketing momentum. The alphabetical organization, standardized metadata, and explicit status annotations transform what could be an overwhelming data dump into a genuinely navigable research tool.

This resource best serves: frontend developers expanding test matrices; security and privacy researchers tracking browser fragmentation; DevOps^{↗ Bright Coding Blog} engineers selecting deployment candidates; and technology historians documenting the post-Chromium-expansion era. It does not replace hands-on testing or security audit workflows, but it eliminates the preliminary research phase that too often consumes disproportionate effort.

Browse the complete, actively maintained index at https://github.com/nerdyslacker/desktop-web-browsers. For related browser automation and testing workflows, see [INTERNAL_LINK: cross-browser testing strategies].