Setting the Scene
In 2026, Chromium-based browsers hold roughly 70% of the browser market, WebKit about 20%, and Firefox under 10%. Chrome, Edge, Brave, Arc, and Vivaldi all share Chromium underneath. Building a browser engine is hard; building one from scratch is harder. Ladybird deliberately takes that harder path. Its self-description is one sentence: *"A truly independent web browser, using a novel engine based on web standards."* It is not a fork, not a wrapper, not a repackaging of Chromium.
Not a Fork, Built from Scratch
"From scratch" carries serious weight in the browser world. Chromium exceeds 30 million lines of code; Firefox's Gecko also runs into the tens of millions. A new engine must implement HTML5, CSS3, ES2025, WebAssembly, WebGL, WebGPU, WebRTC, and more — each a massive engineering effort.
Ladybird originated inside SerenityOS, a Unix-like operating system that Andreas Kling has been developing solo since 2019. SerenityOS built its own web rendering engine (LibWeb), JavaScript engine (LibJS), and WebAssembly implementation (LibWasm) because the OS needed a browser, so it wrote one.
In 2024, Ladybird separated from SerenityOS and became an independent browser project backed by a 501(c)(3) nonprofit. Kling's philosophy is explicit: no user monetization, no advertising, no data collection — just a browser.
Multi-Process Architecture
Ladybird uses a multi-process design:
- Main UI process: windows, tabs, user interaction
- WebContent renderer process: one per tab, isolated from each other
- ImageDecoder process: image decoding outside the renderer, to contain malicious content
- RequestServer process: network requests handled outside the renderer
- Lua beside Python — different design trade-offs
- FreeBSD beside Linux — a different kernel architecture
- ARM and RISC-V beside x86 — different instruction-set philosophies
- GitHub: https://github.com/LadybirdBrowser/ladybird
- Official site: https://ladybird.org
- Status: pre-alpha
- Architecture: multi-process (UI + WebContent + ImageDecoder + RequestServer)
- Core libraries: LibWeb / LibJS / LibWasm / LibCrypto / LibTLS / LibHTTP / LibGfx / LibUnicode / LibMedia / LibCore / LibIPC
- License: 2-clause BSD
- Supported platforms: Linux / macOS / Windows (WSL2) / *Nix
- Governing organization: 501(c)(3) nonprofit
This mirrors Chromium's sandboxing philosophy — isolating untrusted content into separate processes. Image decoding and network access are the largest attack surfaces; moving them out means a compromise cannot reach the main process directly.
Ladybird inherits a large set of core libraries from SerenityOS:
| Library | Role | |---|---| | LibWeb | Web rendering engine | | LibJS | JavaScript engine | | LibWasm | WebAssembly implementation | | LibCrypto / LibTLS | Cryptographic primitives and TLS | | LibHTTP | HTTP/1.1 client | | LibGfx | 2D graphics, image decoding and rendering | | LibUnicode | Unicode and locale support | | LibMedia | Audio and video playback | | LibCore | Event loop, OS abstraction layer | | LibIPC | Inter-process communication |
Inheritance from SerenityOS is a strength, not a weakness: those libraries have been iterated on for over five years.
Why Build a New Engine in the Chromium Era?
1. Monoculture risk. When only one engine implements the web, its bugs become "the standard." Developers start coding to Chromium behavior rather than to W3C specs — the same IE6-era problem recurring. Ladybird is a resistance to that trend. 2. Implementation diversity exposes spec defects. Two independent implementations attempting the same spec will surface ambiguities and gaps. Without independent engines, the spec degenerates into "whatever Chromium does." 3. Nonprofit governance. Chromium is backed by Google (commercial); Firefox is backed by Mozilla (nonprofit but historically dependent on Google search-revenue share). Ladybird is backed by a 501(c)(3) that explicitly rejects user monetization — a novel governance model for browsers. 4. Technical exploration. Because LibWeb has no legacy compatibility baggage, it can experiment with designs that Chromium and Gecko cannot easily try.
Current Status: Pre-Alpha
Ladybird is explicitly labeled pre-alpha, suitable only for developers. From-scratch support for the modern web is a vast engineering effort. Ladybird can render many pages but is far from everyday-use ready.
It runs on Linux, macOS, Windows (WSL2), and various *Nix systems, under a 2-clause BSD license.
Analogy: The Value of Independent Implementations
Independent implementations matter not by replacing the mainstream, but by providing a reference point:
Ladybird plays a similar role against Chromium. It does not need to "win"; its existence has value. When only one engine implements the web, "standard" collapses into "implementation."
Key Facts
Why It Matters
Ladybird is the only from-scratch, non-fork, nonprofit browser engine project active in 2026. Its engineering scope is enormous, and it may never "beat" Chromium. But by existing it preserves implementation diversity for the web platform, opens space for new browser-architecture ideas, and offers the open-source community a nonprofit-governance template. In an era where every browser increasingly looks like Chromium, a genuinely independent engine is worth watching — even if you never run it.