Ladybird

Independent engine built from scratch Ladybird is a new browser engine written from scratch around web standards, not a fork of Chromium, Gecko, or WebKit. That independence is the project's reason to exist: fewer independently controlled engines means less diversity in how the web renders.[1]

No user monetization by design The project states it takes no default search deals, crypto tokens, or other user monetization. Funding comes from nonprofit backing and sponsors, which removes the incentive to steer readers toward paying search partners.[1]

Monthly public progress reports Development is reported in public monthly posts tracking concrete engine work, most recently September 2026 with security hardening, smoother animation, hardware video decoding, and broader web compatibility. The cadence makes it possible to check whether a missing capability has landed before relying on it.[1]

Everyday browser chrome taking shape Recent reports describe download management, browsing history, session restore, browser profiles, and private browsing landing in the client. These are the table-stakes features that turn an engine demo into something a person could use daily.[1]

Media and web-platform coverage growing The 2026 reports list video on major streaming sites, Media Source Extensions on by default, a WebAssembly JIT with garbage collection, CSS container queries, scope, and subgrid, plus WebAudio and geolocation. Each closes a gap that previously broke real sites.[1]

Developer-facing tooling included JavaScript debugging, DevTools storage inspection, and content blocking ship or are in progress according to the 2026 reports. Website testers get the inspection tools they need to file useful bug reports with reductions.[1]

Security work with outside review The September 2026 report describes security hardening with Trail of Bits, alongside Linux sandboxing and GPU isolation work from June 2026. A pre-alpha browser inviting security review signals the team takes the coming alpha audience seriously.[1]

Open contribution path from day one Anyone can clone the repository and run the browser with a documented build script, then contribute bug reports, website reductions, and security issues through public channels including Discord. Testing websites is listed as a first-class contribution.[1][2]

Engine watchers and standards supporters Readers who want the web to run on more than two or three corporate engines will value following and funding this work. Every monthly report shows where standards compliance stands.[1]

Website testers on Linux and macOS Developers who can build from source and file reductions will find a welcoming contribution path. The project explicitly asks for website testing and bug reports.[1][2]

Privacy-minded experimenters Readers who distrust search-deal funding models will appreciate the nonprofit structure and stated refusal of user monetization. It is worth trying precisely because its incentives differ from mainstream browsers.[1]

Daily-driver seekers should wait There is no stable release or installer, and the alpha is targeted for 2026. Anyone needing reliable everyday browsing today should stay on a released browser.[1][2]

Windows users are outside the alpha target The announced first alpha covers Linux and macOS only. Windows readers have no documented release path to plan around.[1]

Non-builders will find setup heavy Cloning a repository and satisfying OS-specific build dependencies is developer work. Readers who cannot or will not build software should revisit Ladybird after the alpha ships.[1][2]