Ladybird: A 100% Self‑Developed Browser Engine with Five Isolated Processes

While more than 99% of browsers on the market rely on Chromium or Firefox’s Gecko engine, the browser‑kernel landscape is heavily monopolized.

Ladybird emerges as a completely self‑developed, open‑source browser built on SerenityOS libraries. It is currently in a Pre‑Alpha internal testing phase and is intended for developers rather than everyday users.

Security architecture : Ladybird isolates its functionality into five separate processes – the main UI process, a per‑tab WebContent rendering process, an ImageDecoder process, a RequestServer network process, and an SQLServer process for cookie and local‑storage handling. This strict sandboxing minimizes the attack surface compared with traditional single‑process or partially multi‑process browsers.

Self‑developed core libraries : The browser relies exclusively on SerenityOS components, avoiding external heavy dependencies such as OpenSSL, Skia, or V8. The key libraries include LibWeb (HTML/CSS/DOM/SVG rendering), LibJS (ECMAScript engine), LibWasm (WebAssembly interpreter), LibCrypto/LibTLS (cryptography and TLS stack), LibHTTP (HTTP/1.1 client), LibGfx (2D graphics), LibUnicode, LibMedia, LibCore, and LibIPC.

Platform support : Officially supported on all Linux distributions, macOS, and Windows via WSL2. There is no native Windows client; earlier claims of such support have been removed from the official FAQ.

Comparative overview : Compared with Chrome/Edge (Blink, Google‑centric, mixed BSD + proprietary license, >70% market share) and Firefox (Gecko, Mozilla‑run, MPL license), Ladybird offers a completely independent implementation, a community‑driven non‑profit governance model, and a permissive 2‑clause BSD license.

Cross‑platform compilation guide

Linux (Ubuntu/Debian) :

sudo apt update && sudo apt upgrade -y
# Install full set of dependencies, including missing Qt6 multimedia components
sudo apt install build-essential cmake ninja-build qt6-base-dev qt6-multimedia-dev libgl1-mesa-dev clang-18

git clone https://github.com/LadybirdBrowser/ladybird.git
cd ladybird
cmake -B build -G Ninja
ninja -C build
./build/Ladybird

macOS (via Homebrew): brew install cmake ninja qt6 llvm After installing dependencies, repeat the same clone, cmake, and ninja steps as on Linux.

Windows (WSL2) :

Install Ubuntu under WSL2 and enable graphical forwarding (WSLg).

Follow the Linux compilation commands verbatim; native Windows builds are not officially supported and community‑provided installers may pose security risks.

Common pitfalls and solutions

C++23 not supported : downgrade cmake or install clang‑18/gcc‑13 or newer.

Black screen / no UI : ensure Qt6 multimedia and graphics drivers are installed; enable WSLg for graphical output.

Cloudflare Turnstile blocked : older versions lack support; update to the May 2026 source to obtain the fix.

Image loading failures : caused by ImageDecoder process issues; rebuild without skipping LibGfx.

JS interaction failures : advanced ES features are still under development; complex Vue/React pages may not render correctly.

Kernel internals

Why multi‑process sandbox improves security : mainstream browsers combine rendering, networking, and image decoding in a single process, allowing a malicious page that gains memory access to read cookies, passwords, and other sensitive data. Ladybird’s strict process separation ensures that a compromise in one module (e.g., ImageDecoder) cannot reach the rendering or network processes.

LibWeb rendering pipeline : RequestServer fetches the page source → LibWeb parses HTML into a DOM tree → CSS is parsed into a style tree → a layout tree is built → LibGfx draws the final bitmap. The entire pipeline is self‑implemented without borrowing external rendering logic.

LibJS engine highlights : Built from scratch without V8, it implements the ECMAScript standard, offering a lightweight codebase suitable for studying lexical analysis, AST construction, and bytecode interpretation. Future plans include rewriting memory‑safety‑critical parts in Rust and using AI assistance for iterative improvements.

2026 official features

Separate compositor process for asynchronous scrolling, keeping the UI responsive.

Native support for Cloudflare Turnstile human verification.

Improved WebAssembly support with runnable examples.

Full developer tools (F12) including DOM inspection, network monitoring, JS debugging, and memory analysis.

Isolated cookie storage process, preventing third‑party scripts from accessing local storage.

2‑clause BSD license allowing unrestricted commercial use and modification.

Target audience

Front‑end and browser‑engine researchers who want to understand rendering, JS engine, and IPC internals.

Security reverse‑engineers seeking a clean multi‑process sandbox for exploitation studies.

Web‑standard contributors testing compatibility and filing spec bugs.

Open‑source enthusiasts interested in contributing to an independent browser ecosystem.

Not suitable for

Casual users needing a stable daily‑driver browser for video, shopping, or complex web apps.

Heavy‑usage users who rely on a mature extension ecosystem.

Users expecting a native Windows client, which is currently unavailable.

In summary, Ladybird provides a unique, fully self‑contained browser engine that breaks the existing kernel monopoly, offers strong security through process isolation, and serves as an excellent learning platform for developers, while it remains unsuitable for mainstream daily browsing.