By ByteBot
Ladybird’s July 2026 newsletter, published July 31, confirms the project has crossed a line most observers assumed was years away. The browser’s style and layout engine has been substantially ported from C++ to Rust, private browsing and full browser profiles now ship, and WebAudio works well enough to run Doom 3. The first alpha for Linux and macOS is next — no date announced, but the feature list looks like a browser, not a prototype. For context: Chromium runs 78.4% of global web traffic. WebKit handles 18.8%. Gecko, which powers Firefox, holds 2.6%. Ladybird is the only new, independent browser engine being built from scratch. That makes every milestone a bigger deal than it appears.
Ladybird’s Rust Engine: What Actually Changed
The July work wasn’t a rewrite teaser — it was the actual port. According to the Ladybird July 2026 newsletter, selector matching, computed styles, cascade, animations, calc() evaluation, layout tree construction, and all layout formatting contexts from block through SVG have moved from C++ to Rust. What remains in C++ is CSS parsing, the DOM, and painting. The core rendering pipeline that runs on every page load is now Rust.
The practical prize is parallelism. Style and layout both do repeated work over large trees — selector matching runs once per element, layout construction once per node. With style now stored as “immutable, shared values that Rust owns,” the system can distribute that work across CPU cores without data races. No major browser does this today. Chrome, Firefox, and Safari all serialize style computation. If Ladybird can make that work in alpha, it has a performance story that matters independent of its independence argument.
The JavaScript engine also gained ground. A new typed interpreter called “flap” replaced the assembly dialect, delivering roughly 5% improvement on compute-heavy benchmarks. WebAssembly call overhead dropped by 20x to 50x after moving to direct execution. Additionally, the ArrayBuffer security model now cages all buffer content and WebAssembly memory in a reserved 4 TiB address space — preventing out-of-bounds exploits from reaching objects and code outside the buffer region.
A Browser, Not Just an Engine
Private browsing arrived in July, and the implementation is stricter than most browsers manage. Cookies, storage, history, caches, downloads, and even address bar suggestions route separately by privacy mode. A page process is either wholly private or wholly normal — there is no mixing. That process isolation by design prevents the kind of data leakage that has tripped up other “private” modes in browsers that share process space more loosely.
Moreover, browser profiles arrived alongside it. Each profile owns settings, bookmarks, history, cookies, and HTTP caches, with sandbox rules generated per profile so each can only reach its own files. Invocation is clean: ladybird --profile work for a named, persistent profile, ladybird --temporary-profile for something that disappears on close. WebAudio real-time and offline rendering now work, enabling Doom 3 and Slow Roads in demos. Geolocation is in, defaulting to deny pending a full permissions system. The list of things a real browser requires is getting short.
Related: Cloudflare Kitesurf: A Rust Browser Built for AI Agents
The AI Code Contradiction
In June 2026, Ladybird closed its external pull request queue. The official reason was AI-generated code. Founder Andreas Kling argued that AI “makes it easier and less costly for bad actors to submit seemingly legitimate code, undermining the trust-building process that open-source relies upon.” A browser processes untrusted internet content — one hidden vulnerability puts users at direct risk. All code changes now go through project maintainers only.
The tension is real: Ladybird uses AI-assisted code translation to port its own C++ to Rust. The JavaScript frontend port took two weeks with LLM help; estimated manual time was several months. However, the team handled this by running C++ and Rust pipelines in parallel on live web traffic — a lockstep mode that triggers an alarm if the two engines produce different output on any page. They used AI, but they built a verification harness that treats AI output as untrusted. That squares the contradiction more carefully than it first appears.
Why Browser Engine Diversity Matters
The last independent browser engine to ship was Opera’s Presto, abandoned in 2013 when Opera switched to Chromium. Since then, “cross-browser compatibility” has collapsed into “does it work in Blink, and does it work in WebKit on iOS?” When Google deprecates an API in Blink, every Chromium-based browser — Edge, Brave, Opera, Samsung Internet — inherits that decision. Banking sites that require Chrome, government portals that break in Firefox, educational tools that mandate Chrome for proctoring: these are the symptoms of a monoculture.
Ladybird cannot fix that alone. Nevertheless, a working alpha changes the conversation. It turns “wouldn’t it be nice” into “here is a browser you can test against.” If it reaches beta in 2027 on target, web developers will have a third meaningful test target for the first time in over a decade — and that matters independently of whether Ladybird ever captures meaningful market share.
Key Takeaways
- Ladybird’s July 2026 update ports selector matching, cascade, animations, and layout tree construction to Rust — unlocking future parallel rendering across CPU cores that no major browser currently does
- Private browsing with process isolation, browser profiles with per-profile sandboxing, and WebAudio now ship — the alpha is close to “real browser” feature completeness
- External pull requests are closed due to AI code risks; the team uses AI internally with parallel verification — a distinction worth adopting in any security-critical open source project
- Chromium-based engines run 78.4% of web traffic; Ladybird’s alpha matters for web standards diversity even if adoption stays small for years
