A practical angle would be an extension that resizes images locally, using JavaScript for the interface and Rust compiled to Wasm for image processing.

Here’s an opening you can adapt:

Browser extensions can do more than modify pages or add shortcuts. They can also process images, parse documents, and run useful tools directly on your device.

WebAssembly makes this interesting. It lets us compile languages such as Rust and C++ into modules that work alongside JavaScript in the browser. JavaScript handles the interface and browser integration, while Wasm handles a specific computation. MDN explains how the two work together.

In this post, we’ll explore that combination through a small browser extension: select an image, resize it locally, and download the result.

Build the rest of the post around this sequence:

  1. Explain why this example uses Wasm.

    Focus on reusing an image-processing library and keeping processing on the device. Treat performance as something to measure.

  2. Introduce the extension’s parts.

    Show the popup, JavaScript integration, and bundled .wasm module. Explain the flow: select image → decode → resize → encode → download.

  3. Compile the processing module.

    Walk through compiling Rust to Wasm, exporting the resize function, and passing image data between JavaScript and Rust.

  4. Load Wasm inside the extension.

    Explain the Manifest V3 configuration. Chrome extension pages need a CSP that permits Wasm compilation, such as this manifest fragment. Chrome’s CSP documentation covers the requirement.

 { "content_security_policy": { "extension_pages": "script-src 'self' 'wasm-unsafe-eval'; object-src 'self';" } }

Bundle the Wasm module with the extension; Chrome Web Store rules include remotely loaded Wasm under remotely hosted code. Chrome’s packaging guidance explains this.

  1. Show the result and discuss tradeoffs. Include screenshots, module size, initialization time, processing time, and memory use. Compare equivalent implementations before claiming a speed improvement.

A useful closing point:

Wasm adds another tool to extension development. The value comes from choosing a clear task, keeping the JavaScript–Wasm interface small, and measuring whether the extra build complexity pays off.