Ladybird is a browser written from nothing. Not a fork, not a fresh coat of paint over somebody else engine, not a project that took an existing code base and changed the colours: a new engine, with its own parser, its own layout, its own JavaScript runtime and its own renderer. It was started by a developer who had already built a complete desktop operating system from scratch as a hobby, and it is funded by a non-profit organisation set up for the purpose. As of 2026-09 the work is in active development, with a first Alpha preview for Linux and macOS planned inside 2026, aimed at developers and early adopters.

That independence is the whole point. Most desktop browsers today sit on a very small number of engines, which means the direction of the web gets decided in a handful of rooms. Ladybird starts from the standards instead and writes the entire stack itself: HTML parsing, CSS layout, a JavaScript engine, graphics rendering. The project began in C++ and has announced a gradual move of subsystems to Rust for memory safety, one piece at a time rather than as a single rewrite.

A non-profit that does not have to sell the user

The project is run by an initiative registered as a 501(c)(3) organisation. Money comes from donations and from corporate sponsors, several of them well known, and the sponsorship is unconditional: it does not buy influence over the technical direction. The commitments are explicit. No default search deal. No advertising. No crypto tokens. No collection of user data. A browser that does not have to earn from the person using it can afford to say that, and saying it is a large part of why the project drew attention in the first place.

What 2026 has actually produced

The team publishes a progress report every month, and the run of them this year has been dense. On the ordinary side, private browsing, browser profiles, bookmarks and history, download management, undo and redo and session restore have all landed, which is the unglamorous work that turns an engine into something a person can live in. On compatibility, the browser now passes the mainstream human-verification challenges, media playback keeps improving, and WebAssembly performance has moved. On speed, a new compositor and style engine, out-of-process asynchronous scrolling and an on-disk cache for JavaScript bytecode have arrived. On security, sandboxing and GPU isolation are being rolled out, and content blocking is built in rather than supplied by an extension.

What the preview actually is

It is worth being clear about the stage. Ladybird is still a developer preview and no release version exists. The coming Alpha is aimed at developers and early adopters, not at anyone who needs a daily browser; that waits for the Beta and the stable release, which the roadmap places in 2027 and 2028. The first Alpha covers Linux and macOS, Windows is planned for a later stage, and mobile sits further out again. Anyone who wants the newest state today builds the source, which is public.

How people take part

The project is open source and accepts contributions in more forms than code. Bug reports matter. So do minimal reproductions of a page that behaves wrongly, testing against real sites, security reports and plain technical feedback. The model is a small full-time team working with community contributors, and the monthly report lists what the community contributed, which is a more honest accounting than most projects manage.

Why it is worth following

A browser engine is one of the largest pieces of software a small team can attempt, and doing it without leaning on an existing one is rarer now than it was twenty years ago. Whether Ladybird reaches a stable release on schedule remains an open question. That a non-profit is paying a full-time team to build the whole stack from the standards, and publishing the work every month while it happens, is already the interesting part.