lightpanda-io/browser
Lightpanda Browser
The headless browser built from scratch for AI agents and automation.
Not a Chromium fork. Not a WebKit patch. A new browser, written in Zig.
The headless browser built from scratch for AI agents and automation.
Not a Chromium fork. Not a WebKit patch. A new browser, written in Zig.
Puppeteer requesting 100 pages from a local website on a AWS EC2 m5.large instance. See benchmark details.
Lightpanda is the open-source browser made for headless usage:
Fast web automation for AI agents, LLM training, scraping and testing:
Install from the nightly builds
You can download the last binary from the nightly builds for Linux x86_64 and MacOS aarch64.
For Linux
|
|
For MacOS
|
|
For Windows + WSL2
The Lightpanda browser is compatible to run on windows inside WSL. Follow the Linux instruction for installation from a WSL terminal. It is recommended to install clients like Puppeteer on the Windows host.
Install from Docker
Lightpanda provides official Docker
images for both Linux amd64 and
arm64 architectures.
The following command fetches the Docker image and starts a new container exposing Lightpanda’s CDP server on port 9222.
|
|
|
|
|
|
|
|
|
|
Once the CDP server started, you can run a Puppeteer script by configuring the
browserWSEndpoint.
|
|
By default, Lightpanda collects and sends usage telemetry. This can be disabled by setting an environment variable LIGHTPANDA_DISABLE_TELEMETRY=true. You can read Lightpanda’s privacy policy at: https://lightpanda.io/privacy-policy.
Lightpanda is in Beta and currently a work in progress. Stability and coverage are improving and many websites now work. You may still encounter errors or crashes. Please open an issue with specifics if so.
Here are the key features we have implemented:
robots.txt with option --obey_robotsNOTE: There are hundreds of Web APIs. Developing a browser (even just for headless mode) is a huge task. Coverage will increase over time.
You can also follow the progress of our Javascript support in our dedicated zig-js-runtime project.
Lightpanda is written with Zig 0.15.2. You have to
install it with the right version in order to build the project.
Lightpanda also depends on zig-js-runtime (with v8), Libcurl and html5ever.
To be able to build the v8 engine for zig-js-runtime, you have to install some libs:
For Debian/Ubuntu based Linux:
|
|
You also need to install Rust.
For systems with Nix, you can use the devShell:
|
|
For MacOS, you need cmake and Rust.
|
|
You an build the entire browser with make build or make build-dev for debug
env.
But you can directly use the zig command: zig build run.
Lighpanda uses v8 snapshot. By default, it is created on startup but you can embed it by using the following commands:
Generate the snapshot.
|
|
Build using the snapshot binary.
|
|
See #1279 for more details.
You can test Lightpanda by running make test.
To run end to end tests, you need to clone the demo
repository into ../demo dir.
You have to install the demo’s node requirements
You also need to install Go > v1.24.
|
|
Lightpanda is tested against the standardized Web Platform Tests.
We use a fork including a custom
testharnessreport.js.
For reference, you can easily execute a WPT test case with your browser via wpt.live.
To run the test, you must clone the repository, configure the custom hosts and generate the
MANIFEST.json file.
Clone the repository with the fork branch.
|
|
Enter into the wpt/ dir.
Install custom domains in your /etc/hosts
|
|
Generate MANIFEST.json
|
|
Use the WPT’s setup guide for details.
An external Go runner is provided by
github.com/lightpanda-io/demo/
repository, located into wptrunner/ dir.
You need to clone the project first.
First start the WPT’s HTTP server from your wpt/ clone dir.
|
|
Run a Lightpanda browser
|
|
Then you can start the wptrunner from the Demo’s clone dir:
|
|
Or one specific test:
|
|
wptrunner command accepts --summary and --json options modifying output.
Also --concurrency define the concurrency limit.
:warning: Running the whole test suite will take a long time. In this case,
it’s useful to build in releaseFast mode to make tests faster.
|
|
Lightpanda accepts pull requests through GitHub.
You have to sign our CLA during the pull request process otherwise we’re not able to accept your contributions.
In the good old days, scraping a webpage was as easy as making an HTTP request, cURL-like. It’s not possible anymore, because Javascript is everywhere, like it or not:
If we need Javascript, why not use a real web browser? Take a huge desktop application, hack it, and run it on the server. Hundreds or thousands of instances of Chrome if you use it at scale. Are you sure it’s such a good idea?
If we want both Javascript and performance in a true headless browser, we need to start from scratch. Not another iteration of Chromium, really from a blank page. Crazy right? But that’s what we did:
Playwright support disclaimer: Due to the nature of Playwright, a script that works with the current version of the browser may not function correctly with a future version. Playwright uses an intermediate JavaScript layer that selects an execution strategy based on the browser’s available features. If Lightpanda adds a new Web API, Playwright may choose to execute different code for the same script. This new code path could attempt to use features that are not yet implemented. Lightpanda makes an effort to add compatibility tests, but we can’t cover all scenarios. If you encounter an issue, please create a GitHub issue and include the last known working version of the script. ↩︎