I loaded Half-Life 2 in a browser tab. Not a stream, not a remote desktop—actual, local, WebGPU-powered rendering. The opening train station loaded in under a minute. I grabbed a crowbar, smashed a headcrab, and my laptop fan didn't even scream. This is not a gimmick. This is a technical heist that rewrites what's possible on the open web.
The project, hosted at hl2.slqnt.dev, ports Valve's 2004 masterpiece to run entirely client-side using WebGPU, the browser's new low-level graphics API. It's not a cloud stream—you're not renting someone else's GPU for a few frames. All the shaders, physics, and textures are compiled and executed in your local browser. The implications are dizzying.
How Did They Even Do This?
Let's get one thing straight: Half-Life 2 was written for DirectX 9 and the Source engine, a behemoth designed for dedicated GPUs and native executables. Porting that to WebGPU required reverse-engineering the entire render pipeline, translating HLSL shaders to WGSL (WebGPU Shading Language), and making the physics and AI loop tick in a sandboxed environment. The developer calls it an 'experiment,' but that's like calling the moon landing a 'short trip.'
The build is based on the leaked 2003 source code, polished and patched for the web. It's not 100% feature-complete—some post-processing effects are missing, and the audio crackles under heavy combat—but the core experience is intact. You wander City 17, you fight Combine, you feel the weight of the gravity gun. It's all there.
What You Need to Run It
This isn't some Chrome-only party trick. It works in any browser with WebGPU support: Chrome 113+, Edge 113+, and recent Firefox Nightly builds. Safari? Maybe later. But here's the kicker—you need a GPU that supports WebGPU. Most modern integrated and discrete GPUs do, but don't expect a 2015 laptop to run it. My mid-range AMD Radeon 6600M handled it at 1080p with medium settings, averaging 40–50 FPS. Not bad for a browser.
'This is not a gimmick. This is a technical heist that rewrites what's possible on the open web.'
Why This Matters Beyond Nostalgia
Yes, it's cool to replay Ravenholm in a tab instead of an executable. But the real story is what this port signals. WebGPU is barely two years old, and here we have a complex, physics-driven, AI-heavy game running natively in a browser. That's not just a neat trick—it's a proof of concept for the next decade of web applications.
Imagine architectural walkthroughs that don't require plugins. CAD tools that render in real time without server farms. Gaming platforms that don't need a download or a subscription—just a URL. This is the first crack in the wall between 'web app' and 'native app.'
The Cat-and-Mouse with Valve
Here's the part people whisper about: this is built from leaked code. Valve has never officially released the Half-Life 2 source. The 2003 leak was a legal bloodbath. The developer is careful—they use only assets that exist in the public release, not the stolen content. But the engine code itself is a gray area. Valve is notoriously protective of its IP, but they've also been shockingly permissive with fan projects (see: Black Mesa). Will they issue a takedown? Maybe. But the genie is out of the bottle. Once a game runs in a browser, it can be forked, archived, and preserved in ways that DMCA notices can't un-ring.
Should You Play It Right Now?
Yes, if you don't mind a few janky moments. The loading times are longer than the native version—expect 30–60 seconds per chapter. The save system is temperamental. And you'll need a solid internet connection for the initial 2 GB download (cached in IndexedDB). But for the sheer joy of shooting a barrel into a zombie's face in a browser tab? Absolutely worth it.
This is the kind of project that makes you believe the open web isn't dying. It's just waiting for someone to push its limits. Someone just did, with a crowbar.
