Opening Scenario
In 2026, Chromium-family engines account for roughly 70% of the browser market, WebKit about 20%, and Firefox less than 10%. Chrome, Edge, Brave, Arc, and Vivaldi are all Chromium underneath. This is no accident—building a browser engine is extremely hard, and building one from scratch is harder still.
Ladybird insists on doing exactly that. Its self-description is a single sentence: "A truly independent web browser, using a novel engine based on web standards." Not a fork, not a wrapper, not a repackage of Chromium. From zero, build one.
Not a Fork—Built from Scratch
"From scratch" carries enormous weight in the browser world. Chromium exceeds 30 million lines of code; Firefox's Gecko is tens of millions more. A new engine must support HTML5, CSS3, ES2025, WebAssembly, WebGL, WebGPU, WebRTC—each a massive engineering effort.
Ladybird's origin is unusual. It began as part of SerenityOS, a Unix-like operating system Andreas Kling started solo in 2019. SerenityOS wrote 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 as an independent browser project, backed by a 501(c)(3) non-profit. Kling's philosophy is clear: no user monetization, no ads, no data collection—just a browser.
Multi-Process Architecture
Ladybird's technical architecture is multi-process:
- Main UI process: windows, tabs, user interaction
- WebContent renderer process: one per tab, isolated from each other
- ImageDecoder process: image decoding runs out-of-process to guard against malicious content
- RequestServer process: network requests run out-of-process
- Lua alongside Python—not a replacement, but a different set of design trade-offs
- FreeBSD alongside Linux—not a replacement, but a different kernel architecture
- ARM/RISC-V alongside x86—not replacements, but different ISA design philosophies
- GitHub: https://github.com/LadybirdBrowser/ladybird
- Website: 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
- Platforms: Linux / macOS / Windows (WSL2) / *Nix
- Organization: 501(c)(3) non-profit
This mirrors Chromium's multi-process design—isolating untrusted-content handling into sandboxed processes. Image decoding and network connections are major attack surfaces; keeping them out-of-process means a compromise cannot directly access the main process.
Ladybird currently inherits a large set of core libraries from SerenityOS:
| Library | Function | |---|---| | LibWeb | Web rendering engine | | LibJS | JavaScript engine | | LibWasm | WebAssembly implementation | | LibCrypto/LibTLS | Crypto primitives and TLS | | LibHTTP | HTTP/1.1 client | | LibGfx | 2D graphics, image decoding and rendering | | LibUnicode | Unicode and locale support | | LibMedia | Audio/video playback | | LibCore | Event loop, OS abstraction layer | | LibIPC | Inter-process communication |
These libraries cover every core component of a browser engine. Inheriting from SerenityOS is not a disadvantage—those libraries have been iterated for over five years, with solid code quality.
Why Build a New Engine in the Chromium Era
This question deserves a serious answer.
First reason: monopoly risk. When the entire web platform has only one engine implementation, that engine's bugs become "the standard." Developers write code against Chromium's behavior, not W3C specs. This is the IE6 problem all over again—one implementation dominating leads to stalled innovation and hollow standards. Firefox/Gecko survives, but its share keeps falling. Ladybird is a resistance to that trend.
Second reason: implementation diversity exposes standard defects. When two independent implementations try to follow the same spec, ambiguities and holes in the standard surface. This is a key driver of web-standard evolution—without independent implementations, standards become "whatever Chromium does."
Third reason: non-profit structure. Chromium is backed by Google (a commercial company); Firefox by Mozilla (non-profit but dependent on Google search revenue). Ladybird is backed by a 501(c)(3) non-profit that explicitly refuses user monetization. This governance structure is new to the browser field.
Fourth reason: technical exploration. LibWeb is a ground-up rendering engine with no legacy burden. It can try new designs that Chromium/Gecko avoid due to compatibility constraints.
Current Status: Pre-Alpha
Ladybird explicitly labels itself pre-alpha, suitable only for developers. This is not modesty—writing a browser engine from scratch, supporting all modern web standards, is a huge undertaking. Ladybird can render many pages, but is far from "daily-usable."
It runs on Linux, macOS, Windows (WSL2), and various *Nix systems, under a 2-clause BSD license friendly to commercial use.
Analogy: The Value of Independent Implementations
Ladybird's existence recalls a recurring pattern: the value of an independent implementation lies not in replacing the mainstream, but in providing a reference point.
Ladybird plays the same role relative to Chromium. It doesn't need to win—its existence itself has value. When the web platform has only one engine, "the standard" becomes "the implementation." With another independent implementation, standards regain meaning.
Data
Why It Deserves Attention
Ladybird is the only browser engine project in 2026 that is from scratch, non-fork, and non-profit. Its engineering burden is enormous, and it may never "beat" Chromium. But its existence itself is valuable—an independent reference implementation for the web platform, new design space for browser architecture, and a model of non-commercial governance for the open-source community.
In an era when every browser increasingly resembles Chromium, a truly independent engine deserves attention. Even if you never use it, its existence makes web standards more meaningful.