LadybirdBrowser/ladybird

Ladybird is not a daily driver. It is a pre-alpha browser for people who want a genuinely separate engine to exist and are willing to build it from source.

The problem

Opening a page today means choosing among browsers that depend on a small number of engines. If you want to run or evaluate a web platform sharing no engine lineage with those, the usual route is to read about it. Ladybird changes that: you clone the repository, build the browser, and get a multi-process desktop browser with its own LibWeb rendering engine, LibJS JavaScript engine, and supporting libraries inherited from SerenityOS. The result is something you can run, inspect, and contribute to.

What's different

The engine is written around web standards. Each tab gets its own sandboxed WebContent renderer process, and image decoding and networking run out of process, which the README says is meant to make the browser more resilient against malicious content. JavaScript, WebAssembly, TLS, HTTP, Unicode, graphics, and media playback all come from project libraries rather than an existing browser stack, so the pipeline from network request to paint is open in one C++ codebase.

The trade-off is scale. A young engine will encounter pages it does not render as expected. The out-of-process design also adds IPC boundaries, which is useful structurally but means more moving parts when debugging. A February 2025 Hacker News commenter reported that a progress recap then ranked Ladybird fourth in standards compliance, behind Safari, with Gmail, Google Calendar, and Figma loading but not fully usable; that is a dated thread claim, not a compatibility guarantee. The February 2026 removal of the planned Swift adoption, discussed in a linked commit thread, shows architecture plans can change.

Who should try it

Good fit: a C++ developer or web-platform enthusiast who wants to contribute to an independent engine, learn how rendering and JavaScript execution are implemented, or evaluate standards compliance. Rough edges are part of the work. Poor fit: anyone needing a dependable daily browser, extensions, or broad site compatibility. The pre-alpha warning and developer-only framing are explicit. If you only want to follow progress, the project website and monthly updates are a lighter alternative.

Requirements and limitations

Ladybird runs on Linux, macOS, Windows via WSL2, and many other Unix-like systems, but not natively on Windows according to the README. You must build it yourself using the build instructions; no packaged consumer release is described. Expect a C++ toolchain, a substantial compile, and rebuilds as the project changes. It is pre-alpha, so sites may render incorrectly or break. Contributing requires familiarity with the participation guidelines and issue policy.

HotRepo's take

HotRepo tracked Ladybird on the daily board for two dates: 66,662 stars on 2026-10-24 and 66,663 on 2026-10-25. That two-day sample cannot establish persistence or trend direction. The repository is about 877 days old, and a 994-point Hacker News welcome thread from February 2025 shows attention, not current quality. Before investing time, check the project site and build documentation for your platform, especially whether WSL2 is acceptable for your workflow.