ZeroWeb Rust browser architecture: from request to pixels

Follow the page pipeline and the boundaries between the browser application, embeddable WebView, engine and rendering infrastructure.

Two product entrypoints

ZeroBrowser is the browser application. ZeroWebView is the embedding API for host applications. Both use the same project foundations, but desktop browser execution can cross process boundaries; an in-process demo alone does not validate that path.

The page pipeline

  1. net handles resources and navigation.
  2. dom parses HTML with html5ever, while css-parser parses style rules.
  3. style-system computes styles from matching rules, inheritance and the cascade.
  4. layout-engine produces geometry using Taffy and project layout logic.
  5. engine coordinates the page pipeline and painting; render-foundation supplies GPU/CPU primitives and font infrastructure.

Host and process boundaries

host-runtime handles platform windows and input. The browser application integrates product state with the WebView. protocol defines messages between process roles such as the browser and renderer. The shared page-runtime connects page execution to different hosts.

Where to start reading

Start at crates/webview/src/webview.rs for the public embedding surface, apps/browser/src/main.rs for the desktop host, or crates/engine/src/pipeline for page processing. Read the current source together with the architecture guide: module presence does not imply complete standards support.

Sources: architecture guide, WebView source, renderer source.