What is Lightpanda?
Lightpanda is a headless browser built from scratch in Zig rather than forked from Chromium or WebKit. It runs JavaScript on V8, parses HTML with html5ever and fetches with libcurl, but has no graphical rendering engine. It exposes a Chrome DevTools Protocol server so Puppeteer and Playwright scripts connect to it in place of headless Chrome, plus WebDriver BiDi, a native MCP server and a built-in agent mode.
The repo is AGPL-3.0 with about 39,000 GitHub stars. Version 1.0.0 shipped on 2 October 2026 and 1.0.2 on 23 October; contributors must sign a CLA. Lightpanda the company sells a hosted cloud with a free tier of 10 browser hours a month and a $19 Builder plan.
Usage telemetry is on by default and is switched off with LIGHTPANDA_DISABLE_TELEMETRY=true.
Is Lightpanda worth it?
Lightpanda is the most credible attempt yet at a browser built for machines rather than people. Agents and crawlers need JavaScript to run, because most of the web is now single-page apps, but they never look at pixels, so a full Chromium spends most of its memory on work nobody uses. Lightpanda drops the rendering engine and keeps V8, the DOM, XHR and fetch, cookies, proxies and network interception, then speaks the same DevTools Protocol that Puppeteer and Playwright already use. Switching an existing script is mostly a change of browserWSEndpoint.
The headline figures come from the project's own crawler benchmark: 933 real pages on an AWS m5.large, with a peak of 123 MB against 2 GB for headless Chrome over 100 pages, and 5 seconds against 46. Those are self-reported, and they measure page loads, not a click-heavy session, but even a fraction of that gap changes how many concurrent agents fit on one machine. The agent features go further than a bare CDP endpoint: lightpanda mcp serves an MCP server over stdio or HTTP with a separate browsing session per client, and lightpanda agent drives the browser in plain English and exports the session as a PandaScript that replays without a model.
The weakness is the one every new engine has. Compatibility is tracked against Web Platform Tests and published daily, and a site that leans on an API Lightpanda has not implemented will fail where Chrome would not. There is no native Windows build, the Linux binary needs glibc 2.35 or newer (Alpine images fail), and screenshots and PDFs are text-only renders because nothing paints the page. Telemetry is on unless you set an environment variable.
The licence matters more than usual. AGPL-3.0 is fine for running it inside your own pipeline, but a company that modifies it and offers it as a network service owes its changes back, which pushes some buyers towards the hosted cloud or an enterprise agreement. Against obscura, the other from-scratch headless browser on this site, Lightpanda has the larger community, a 1.0 release and the MCP and agent layers; Chrome itself remains the safe fallback for the pages it cannot handle.
Where it earns its place
A data engineer crawling 50,000 JavaScript-rendered product pages a night
Fit more concurrent browsers on the same instances
Point the existing Puppeteer crawler at lightpanda serve instead of headless Chrome and dump pages as Markdown. On the project's benchmark peak memory fell from 2 GB to 123 MB per 100 pages; keep a Chrome pool for pages that fail.
A developer giving Claude Code or Cursor a browser
Let the agent read and click through web pages without launching Chrome
Add lightpanda mcp to the MCP config; the agent gets navigation, extraction and structured-data tools over stdio. Free and local, with telemetry to switch off.
An automation team at a 30-person agency building client scrapers
Prototype a scraping flow with an LLM, then run it cheaply in production
Describe the flow to lightpanda agent, save the session as a PandaScript and replay it with lightpanda run, so production runs spend no tokens. The hosted Builder plan is $19 a month for 300 browser hours.
Before you commit
- Setup
- One static binary from Homebrew, the AUR, Nix, nightly downloads or the lightpanda/browser Docker image; lightpanda serve starts a CDP server on port 9222 in seconds. Windows users run it inside WSL2.
- Integrations
- Chrome DevTools Protocol for Puppeteer and Playwright, WebDriver BiDi, an MCP server over stdio or HTTP, and an agent mode that works with Anthropic, OpenAI, Gemini, Vertex AI, Mistral, OpenRouter or local models through Ollama and llama.cpp.
- Data and privacy
- Sends usage telemetry by default (LIGHTPANDA_DISABLE_TELEMETRY=true turns it off); --obey-robots respects robots.txt. AGPL-3.0, so modifying it and offering it as a network service obliges you to publish your changes.
- Cost at scale
- Self-hosted it costs only the instances, and the memory saving is the point. The hosted cloud is free for 10 browser hours, $19/month for 300 hours then $0.08 an hour, with Enterprise on-premise and volume pricing on request.
- Limits
- Compatibility is partial and tracked on Web Platform Tests; about 104 open issues. No graphical renderer, so PNG and PDF dumps are text-only; no native Windows build; musl-based Linux images do not run the binary.
What’s good
- CDP server: Puppeteer and Playwright scripts connect unchanged
- Self-reported 123 MB vs 2 GB peak memory over 100 pages
- Native MCP server with isolated sessions per client
- Agent mode records replayable, model-free PandaScripts
What’s not
- Sites using unimplemented web APIs break where Chrome works
- AGPL-3.0 and a CLA; network-service changes must be shared
- Telemetry on by default
- No native Windows binary; Linux build needs glibc 2.35+
Best for
Teams running many concurrent scraping or browsing agents who are paying for headless Chrome's memory and can fall back to Chrome for the odd site.
Lightpanda alternatives
Lightpanda: common questions
- Is Lightpanda worth it?
- Headless Chrome's memory bill cut by an order of magnitude for agents and crawlers, as long as the pages you need sit inside what a young engine supports. We rate it 4.2 out of 5.
- How much does Lightpanda cost?
- Free and open source (AGPL-3.0). Hosted cloud: Explorer free (10 browser hours, 5 concurrent sessions); Builder $19/month (300 hours, then $0.08/hour, 30 concurrent); Enterprise on request.
- What are the downsides of Lightpanda?
- Sites using unimplemented web APIs break where Chrome works; aGPL-3.0 and a CLA; network-service changes must be shared; telemetry on by default; no native Windows binary; Linux build needs glibc 2.35+.
- Who is Lightpanda best for?
- Teams running many concurrent scraping or browsing agents who are paying for headless Chrome's memory and can fall back to Chrome for the odd site.
- How much does Lightpanda cost for a team or in production?
- Self-hosted it costs only the instances, and the memory saving is the point. The hosted cloud is free for 10 browser hours, $19/month for 300 hours then $0.08 an hour, with Enterprise on-premise and volume pricing on request.
- Is Lightpanda safe for company data?
- Sends usage telemetry by default (LIGHTPANDA_DISABLE_TELEMETRY=true turns it off); --obey-robots respects robots.txt. AGPL-3.0, so modifying it and offering it as a network service obliges you to publish your changes.
- What are the best Lightpanda alternatives?
- The closest alternatives we have reviewed are Obscura, Browser Use, Stagehand and Crawl4AI.
Answers checked Oct 31, 2026.
Make Lightpanda? Show this rating on your site
