Ladybird Is Building the First New Browser Engine in Years, GENZ TECH

The web runs on a shrinking number of engines, and Ladybird is trying to add a genuinely new one. Ladybird is an open-source browser built entirely from scratch, with its own rendering engine and its own JavaScript engine, borrowing no code from Chromium, WebKit, or Gecko, the three engines that power essentially every browser you use today. Governed by a nonprofit and funded by unrestricted donations from sponsors including Cloudflare, Shopify, FUTO, and 37signals, the project is targeting its first alpha release in 2026 on Linux and macOS, aimed at developers and early adopters. In a browser world that looks crowded but is remarkably narrow underneath, with many brands sharing a handful of engines, Ladybird is the most credible attempt at true engine independence since Servo.

Ladybird is a from-scratch browser engine, not a fork, using its own LibWeb renderer and LibJS JavaScript engine.
It is run by the nonprofit Ladybird Browser Initiative and funded by unrestricted donations, with no search deals or crypto tokens.
A first alpha is targeted for 2026 on Linux and macOS for developers, with beta in 2027 and a stable release aimed at 2028.
As of October 2025 the engine passed about 90% of the official web platform tests.

What actually happened

Ladybird began as part of SerenityOS, a hobby operating system, and grew into a standalone browser project under its own nonprofit, the Ladybird Browser Initiative. Its architecture is deliberately independent: LibWeb is a brand-new rendering engine, and LibJS is a brand-new JavaScript engine with its own parser, interpreter, and bytecode execution. It uses a security-focused multi-process design, with separate processes for web content, network requests, image decoding, and compositing per tab, so a crash in one renderer does not take down the whole browser. The codebase started in modern C++, and the team has since adopted Rust as a successor language, beginning in February 2026 to port the JavaScript parser and bytecode generator from C++ to Rust. The roadmap is multi-year: a developer-focused alpha in 2026 on Linux and macOS, a beta in 2027, and a public stable release targeted for 2028, with Windows and mobile support coming later.

Why does a new engine matter when browsers already exist?

Because the browser is the most important application in computing, and almost all of them are built on engines controlled by a few large companies with their own commercial agendas. Chrome, Edge, Brave, Opera, and many others are built on Chromium, Google's engine. Safari uses WebKit, Apple's engine. Firefox uses Gecko, Mozilla's. That means the rules of the web, what is possible, what is prioritized, what is deprecated, are effectively set by a handful of corporations whose incentives do not always align with users or the open web. When Google can shape web standards through Chromium's dominance, or when a privacy-hostile change ships because the engine owner wants it, there is no independent alternative to push back. Ladybird matters because an engine with no ads business, no search deal, and no platform to protect can make different choices, and its mere existence gives the web a check against the monoculture that a purely brand-level browser choice cannot provide.

The context most coverage skips

The hardest and most interesting part of Ladybird is its refusal to monetize the user, and a recent governance change shows how seriously it takes independence. The project has committed to no default search deals, no crypto tokens, and no user monetization of any kind, funding itself purely through unrestricted donations where sponsors get no say in the technical roadmap and no board seats for sale. That is a direct rejection of the model that funds every major browser, where the search default is the revenue engine and the user is, in effect, the product being sold to an advertiser. On June 5, 2026, the project made a notable move: it stopped accepting public pull requests from non-maintainers, citing quality and security concerns as it approaches alpha. Founder Andreas Kling framed it as a reluctant response to AI tooling flooding the project with lower-quality contributions, a small but telling sign of how AI is reshaping even open-source development. The engine already passes about 90% of the official web platform tests, so the technical foundation is real, not aspirational.

Who this affects

Developers and early adopters are the immediate audience for the 2026 alpha, and their testing will shape whether Ladybird can eventually handle real-world browsing. The broader web ecosystem benefits from any credible independent engine, because engine diversity is what keeps web standards genuinely open rather than dictated by whoever controls the dominant renderer. Privacy-conscious users have a long-term reason to watch, since a browser with no advertising incentive can make choices the incumbents will not. And the incumbent engine owners, Google, Apple, and Mozilla, face at least a symbolic challenge to the idea that building a new engine from scratch is impossible, a belief that has helped entrench the current monoculture. The caveat is timeline: this is a developer alpha, not a daily driver, and ambitious browser timelines have a long history of slipping.

What is next?

Watch the 2026 alpha closely, because a shippable, if rough, independent browser would be a genuine milestone and the first real test of whether the from-scratch approach can reach everyday usability. Watch the Rust migration, since porting core subsystems from C++ to Rust is both a security investment and a signal of long-term seriousness. Watch how the closed-contribution model affects development velocity, because cutting off public pull requests trades openness for control at a delicate moment. And watch the funding, since the entire independence pitch rests on donations holding up without the search-deal revenue that sustains every rival.

Our take

Ladybird is the most important browser project almost nobody is using yet, and that is exactly why it deserves attention. The web's engine monoculture is a real structural problem, and a genuinely independent engine, funded without ads or search deals, is the only kind of answer that actually addresses the root cause rather than reskinning someone else's engine and calling it an alternative. The 90% web-platform-test score proves this is engineering, not vaporware, and the refusal to monetize users is a principled stance that the incumbents structurally cannot match. The risks are honest ones: timelines slip, donations are harder than search revenue, and the closed-contribution turn is a gamble. But the web needs this to exist, and Ladybird is the closest anyone has come in years. A 2026 alpha will not dethrone Chrome. It will prove that a different kind of browser is still possible, and right now that proof is worth a great deal.

Reporting via Cloudflare, analysis by GenZTech.

Ladybird Is Building the First New Browser Engine in Years