Truly independent web browser
Find a file
Timothy Flynn 695bbcb991
Some checks are pending
CI / macOS, arm64, Sanitizer, Clang (push) Waiting to run
CI / Linux, x86_64, Fuzzers, Clang (push) Waiting to run
CI / Linux, x86_64, Sanitizer, GNU (push) Waiting to run
CI / Linux, x86_64, Sanitizer, Clang (push) Waiting to run
Package the js repl as a binary artifact / Linux, arm64 (push) Waiting to run
Package the js repl as a binary artifact / macOS, arm64 (push) Waiting to run
Package the js repl as a binary artifact / Linux, x86_64 (push) Waiting to run
Run test262 and test-wasm / run_and_update_results (push) Waiting to run
Lint Code / lint (push) Waiting to run
Label PRs with merge conflicts / auto-labeler (push) Waiting to run
Push notes / build (push) Waiting to run
LibJS: Revert common error types to only hold a single string
Before porting to UTF-16, these instances held a String. The port to
UTF-16 changed them to hold the original string as a StringView, and
lazily allocated the UTF-16 message as needed. This somehow negatively
impacting the zlib.js benchmark in the Octane suite.
2025-08-18 01:43:45 +02:00
.devcontainer Devcontainer: Set dynamic triplets for vcpkg cache feature 2025-07-16 08:36:50 +02:00
.github CI: Create wasm artifact and use it in the js-benchmarks workflow 2025-08-14 10:02:35 +02:00
AK AK/Time+LibWeb/HTML: Fix ISO8601 week conversions 2025-08-14 11:05:28 -04:00
Base/res UI/Qt: Add "Dump CSS Errors" menu item 2025-08-04 10:50:09 +01:00
Documentation Meta: Replace lint-clang-format.sh with lint-clang-format.py 2025-08-14 10:57:31 +02:00
Libraries LibJS: Revert common error types to only hold a single string 2025-08-18 01:43:45 +02:00
Meta Meta: Pass ladybird.py extra arguments to the target process 2025-08-18 01:43:45 +02:00
Services RequestServer: Don't set CURLOPT_HTTPGET _and_ CURLOPT_CUSTOMREQUEST 2025-08-13 10:30:04 -04:00
Tests LibWeb/HTML: Check all radio buttons in group for required attribute 2025-08-17 22:27:14 +02:00
Toolchain
UI LibCore: Remove unused "visible for timer purposes" concept 2025-08-11 16:55:25 +02:00
Utilities CI: Create wasm artifact and use it in the js-benchmarks workflow 2025-08-14 10:02:35 +02:00
.clang-format
.clang-tidy Meta: Disable clang-tidy's const correctness checks 2025-07-08 11:04:15 -04:00
.clangd
.editorconfig
.gitattributes
.gitignore CMake: Add a flatpak build for org.ladybird.Ladybird 2025-07-08 11:45:32 -06:00
.gn
.mailmap
.pre-commit-config.yaml
.prettierignore
.prettierrc
.swift-format
.swift-version Meta: Update swift version to 2025-06-22 2025-07-09 16:26:49 -06:00
.ycm_extra_conf.py
CMakeLists.txt
CMakePresets.json CMake: Improve preset display names and descriptions 2025-07-09 16:26:59 -06:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
ISSUES.md
LICENSE
pyproject.toml
README.md
SECURITY.md
vcpkg-configuration.json
vcpkg.json Meta/curl: Update to 8.15.0 2025-07-21 15:09:35 +02:00

Ladybird

Ladybird is a truly independent web browser, using a novel engine based on web standards.

Important

Ladybird is in a pre-alpha state, and only suitable for use by developers

Features

We aim to build a complete, usable browser for the modern web.

Ladybird uses a multi-process architecture with a main UI process, several WebContent renderer processes, an ImageDecoder process, and a RequestServer process.

Image decoding and network connections are done out of process to be more robust against malicious content. Each tab has its own renderer process, which is sandboxed from the rest of the system.

At the moment, many core library support components are inherited from SerenityOS:

  • LibWeb: Web rendering engine
  • LibJS: JavaScript engine
  • LibWasm: WebAssembly implementation
  • LibCrypto/LibTLS: Cryptography primitives and Transport Layer Security
  • LibHTTP: HTTP/1.1 client
  • LibGfx: 2D Graphics Library, Image Decoding and Rendering
  • LibUnicode: Unicode and locale support
  • LibMedia: Audio and video playback
  • LibCore: Event loop, OS abstraction layer
  • LibIPC: Inter-process communication

How do I build and run this?

See build instructions for information on how to build Ladybird.

Ladybird runs on Linux, macOS, Windows (with WSL2), and many other *Nixes.

How do I read the documentation?

Code-related documentation can be found in the documentation folder.

Get in touch and participate!

Join our Discord server to participate in development discussion.

Please read Getting started contributing if you plan to contribute to Ladybird for the first time.

Before opening an issue, please see the issue policy and the detailed issue-reporting guidelines.

The full contribution guidelines can be found in CONTRIBUTING.md.

License

Ladybird is licensed under a 2-clause BSD license.