Zebkit Packages Chromium as Native Library
Zebkit packages Chromium’s Blink, V8, PDFium, and FFmpeg stack as a linkable library for native applications, preserving the host app’s event loop, windows, and toolkit. It supports C/C++, Rust, Python, and JavaScript, with native Playwright, CDP, and MCP support for automation and agents. [GitHub](https://github.com/ikey4u/zebkit)
Zebkit’s compelling idea is not merely embedding Chromium—CEF already does that—but making the browser engine feel like a native dependency rather than an application runtime. [CEF documentation](https://chromiumembedded.github.io/cef/)
- –Project benchmarks report a 34% smaller package, faster cold starts, and 29% lower blank-page memory usage than Electron.
- –Native Playwright execution and MCP support make Zebkit unusually relevant for browser-based AI agents.
- –Built-in PDF, media, compression, crypto, and graphics APIs could eliminate duplicated dependencies in desktop software.
- –The tradeoff is substantial integration complexity: Chromium builds require roughly 30 GB, platform support is still evolving, and sandboxing, signing, and licensing remain deployment concerns.
- –CEF remains the more established choice, while Zebkit’s differentiation is its slimmer host model, broader language bindings, and in-process automation.
DISCOVERED
2h ago
2026-11-09
PUBLISHED
4h ago
2026-11-09
RELEVANCE
AUTHOR
Riiiiichard