17 - Nov - 2026

WebAssembly is turning Chrome into something closer to an operating system

Imagine opening Chrome on an otherwise ordinary computer to check your email, then staying there to play a PlayStation 2 game, explore Linux, edit a layered image, and chat with an AI model running on your own hardware. Those possibilities already exist through projects including TabStationToo, WebVM, Photopea, and WebLLM. The interesting part isn’t simply that these tools have websites. It’s that the browser can become the place where the work actually happens. That raises a question: if your software lives behind URLs instead of desktop shortcuts, how much does the operating system underneath still define your everyday computing experience?

WebAssembly turned your browser into a runtime

JavaScript does the talking, Wasm does the heavy lifting

A laptop on a wooden table with Chrome open

WebAssembly, usually shortened to Wasm, is a portable compilation target that lets languages such as C, C++, and Rust run in the browser alongside JavaScript. Think of it as a way to bring existing software engines to the web without rebuilding everything in JavaScript.

Its compact, low-level format can deliver near-native performance for demanding workloads, although that isn’t a promise that every browser port matches its desktop counterpart. JavaScript still connects the pieces, while browser APIs provide capabilities such as graphics, storage, and file access. The result feels less like viewing a document and more like launching an application. For everyday computing, that makes the browser feel less like a destination and more like a common workspace.

A PS2 and a Linux box, one tab apart

Yes, the tab eating your RAM is also running a PlayStation 2

TabStationToo brings the PCSX2 PlayStation 2 emulator into a browser using WebAssembly. The project is early and experimental. PCSX2’s own recompilers emit x86 or ARM code a browser can’t run, so it falls back on interpreters and a software renderer, with a WebGPU renderer planned.

You supply your own dumped BIOS and game images, which stay local, and it supports gamepads and memory cards. For an older flavor of computing, js-dos offers DOSBox-based backends and WebAssembly builds for running DOS software in the browser.

Then there’s v86, which emulates an x86 PC and translates machine code into WebAssembly, allowing supported operating systems, including 32-bit Linux, to boot inside a tab. WebVM takes a different route: its CheerpX engine translates x86 instructions and emulates Linux system calls to run unmodified Linux software, with an Alpine Linux graphical desktop among its demonstrations. Neither experience is simply a video stream from somebody else’s computer.

There are boundaries, though. v86 doesn’t support 64-bit kernels or multiple emulated CPU cores, while WebVM’s networking needs extra infrastructure because browsers don’t expose ordinary low-level TCP and UDP sockets. WebVM also fetches disk blocks on demand and caches them locally, a useful reminder that local execution doesn’t necessarily mean everything arrives ready for offline use.

Photopea, Squoosh, and VS Code are already in your tabs

Odds are you’ve used one without installing a thing

Squoosh compressing a photo to AVIF in the browser
Screenshot taken by Yadullah Abidi | No attribution required.

The quieter examples might matter more day to day. Photopea handles raster and vector editing locally and can keep working after you disconnect, once the site has loaded. Its documentation requires both JavaScript and WebAssembly, so calling the entire editor a Wasm application would oversimplify things.

Squoosh offers a clearer example of Wasm’s specific contribution: image encoders and decoders compiled to WebAssembly let you use codecs beyond those built into your browser. Compression happens locally rather than uploading your images to a server. That’s a practical desktop utility delivered through a URL.

Similarly, vscode.dev brings code editing and compatible extensions into the browser, but doesn’t provide an unrestricted local terminal or the full desktop execution environment by default. Microsoft’s WebAssembly work adds another layer, demonstrating Python interpreters and command-line tools running through browser-hosted WASI interfaces. The distinction matters: a familiar interface doesn’t automatically mean every desktop capability comes with it.

WebLLM puts a language model inside your tab

Your prompts stay home, but the model download doesn’t

WebLLM running Llama 3.2 1B in the browser
Screenshot taken by Yadullah Abidi | No attribution required.

WebLLM runs language-model inference inside the browser, downloading model assets rather than requiring a server to generate each response. WebGPU accelerates GPU computation, while WebAssembly handles CPU-side work such as structured-generation logic and runtime management.

That combination makes the browser an AI runtime, not merely a chat window connected to a remote model. There’s still a first-download wait, and a WebGPU-compatible browser is required. Local execution changes where the work happens; it doesn’t make the workload disappear.

The privacy appeal is easy to see: an inference engine that doesn’t need server-side processing offers a different starting point from a cloud chatbot. Still, I’d judge the application around that engine separately. “Runs locally” should prompt questions about a site’s wider data handling, not end them.

The browser still isn’t your operating system

Chrome is not replacing Windows, but it is getting ideas

Chrome isn’t becoming Windows or Linux. WebAssembly still operates inside browser security boundaries, with access to the outside world mediated through permitted APIs. And this isn’t exclusively Chrome’s story: Wasm belongs to the open web platform, not one browser vendor.

The change is more practical than philosophical. When a tab can serve as your console, workshop, editor, or AI interface, installing a separate application stops being the automatic first step. Your operating system remains essential underneath, managing hardware and resources. It just becomes easier to forget which one you’re using while you get something done. That’s the shift worth watching.

Leave a Reply

Your email address will not be published. Required fields are marked *