hn.today

Zebkit – Chromium's engine as a library you link, not a runtime you live in

github.com117 points46 comments
Screenshot of Zebkit – Chromium's engine as a library you link, not a runtime you live in

Zebkit packages Chromium’s content layer, Blink, V8, PDFium, and other engine components as a library that applications link rather than a standalone browser runtime. The host application keeps its own process, event loop, windows, toolkit, and shipping model; web pages run in sandboxed helper processes, while Zebkit renders into windows supplied by the application or off-screen for custom drawing. It supports C, C++, Rust, Python, and JavaScript, and runs on Linux, macOS, and Windows. The project positions this as an alternative to Electron: it claims a 34% smaller footprint, 2.3-second cold starts versus 6.6 seconds, and 29% less memory per page than Electron 45.2.1.

Beyond web views, Zebkit exposes PDF rendering and editing, including search, forms, annotations, redaction, page operations, and signatures; drawing and text shaping; and media capture to MP4 or WebM without re-encoding. Applications can define URL schemes, control permissions and network behavior, and expose native capabilities to pages selectively. Built-in automation offers Playwright’s API without a Node driver, and an MCP tool supports agent access to pages, PDFs, media, and windows. The engine incorporates 17 libraries, including SQLite, FFmpeg, and PDFium, through a shared C API. Version 0.4.0 uses Chromium 157; prebuilt packages are available, while building Chromium requires about 30 GB of source space and can take hours initially.

Read on github.com46 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Programming

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.