Browser Requirements for PS2 Web Recomp: The Two-Minute Check

PS2 Web Recomp ports ask exactly one hard thing of your machine: a browser with working WebGPU. Everything else — the WebAssembly engine, the memory, the gamepad support — is table stakes in any current browser. This page is the two-minute check that confirms you are ready for PS2 Web Recomp, plus the settings that quietly break WebGPU and the platforms where this does not yet work.

The Hard Gate: WebGPU

WebGPU is the modern browser graphics API that the PS2 Web Recomp runtime uses to recreate the PlayStation 2's Graphics Synthesizer on your actual GPU. It is the successor to WebGL, designed to map onto Vulkan, Metal and DirectX 12, and it exposes the modern GPU features the PS2 Web Recomp renderer relies on. No WebGPU, no port — there is no WebGL fallback.

The browser landscape at a glance. Chrome and Edge ship WebGPU enabled by default on current versions, on Windows, macOS and ChromeOS, with Linux support current as well. Firefox ships WebGPU on Windows in current releases, with other platforms rolling out through the release train. Safari has been bringing WebGPU up on macOS and iOS. The practical rule: use a current-version browser, not a year-old one, and verify rather than assume — the check below takes less time than reading this paragraph did.

The Two-Minute Check

In Chrome or Edge, open chrome://gpu. Find the Graphics Feature Status section and locate WebGPU. The status you want is Hardware accelerated — that single line is the whole gate, and everything else on this page is either explanation or repair. In Firefox, open about:support and check the WebGPU row in the graphics table. If either shows Software only, Disabled, or the feature is absent, something below is the reason.

One further check some ports recommend: a WebGPU-capable browser also needs the feature enabled at the OS driver level. On Windows, an up-to-date graphics driver matters; on macOS, staying current on OS updates matters. Browsers deliberately disable WebGPU on known-bad driver versions, so a failing check sometimes means update the driver, not buy hardware.

The Settings That Quietly Break It

Three settings account for nearly every failed check on an otherwise-capable machine. First, hardware acceleration disabled in browser settings — often turned off years ago to fix an unrelated stutter, and fatal for WebGPU, which falls back to software or vanishes. Second, battery-saver modes on laptops that force integrated graphics or throttle the GPU — the browser silently lands on a configuration with no WebGPU path. Third, remote desktop connections and virtual machines, where no real GPU is exposed to the browser at all.

On dual-GPU laptops, make sure the browser runs on the discrete card if the integrated one lacks support — the OS graphics settings per-application control handles this on Windows and macOS.

What Hardware You Actually Need

The pleasant surprise of the PS2 Web Recomp approach is how modest the requirements are. The PlayStation 2 shipped in 2000 with hardware that a modern laptop exceeds by two orders of magnitude. Because the PS2 Web Recomp pipeline translates the game code into WebAssembly rather than interpreting console code, the CPU burden is far below traditional emulation; because rendering goes through WebGPU to your real GPU, the graphics side has genuine headroom.

Practical floor: any mid-2010s-or-later laptop with an integrated GPU from the current driver generation, 8GB of RAM, and a current browser. Comfortable zone: anything sold as a modern machine with discrete or recent integrated graphics and 16GB of RAM. The flagship God of War II port performs well on ordinary modern hardware, and lighter titles run comfortably below that bar. The heavier caveat is per-title special effects in young ports, not the hardware floor.

The Mobile Reality

Phones and tablets are the next frontier, not the current one. WebGPU support on mobile browsers is arriving — iOS and Android release trains are both bringing it up — but a PS2 title also assumes memory bandwidth and thermal headroom that mid-range phones do not have. Early PS2 Web Recomp experiments on flagship phones exist; a comfortable mobile experience does not yet. Plan on desktop for PS2 Web Recomp play today, and watch this page as the mobile story develops.

When Something Still Fails

If the check passes and a PS2 Web Recomp port still refuses to start, the failure is almost always one of: an old cached version of the page (hard-refresh), an aggressive privacy extension blocking WebGPU initialization or storage access, or a corporate-managed browser policy disabling GPU APIs. Test in a clean profile to isolate the second and third. Failing all that, the project's issue tracker is where the community diagnoses genuinely broken configurations — bring your chrome://gpu output when you go.

Browser-by-Browser Notes

The landscape in detail, for those who want more than the headline. Chrome is the reference implementation — WebGPU shipped first and performs best here, and the project's demonstrations were primarily developed and tested against it. Edge inherits the same engine and behaves equivalently; nothing about a port distinguishes the two in practice. Firefox brought WebGPU to Windows first in its release train with other platforms following; support is solid where enabled, and the community reports ports running well, with occasional per-release variance worth remembering when comparing notes. Safari on macOS has been maturing its WebGPU implementation through the OS release cycle — current versions are arriving at support, but verifying before expecting is the wise order on Apple browsers.

One versioning note that prevents most confusion: WebGPU improvements ship with browser releases, so a browser six months behind current is meaningfully behind on WebGPU. If a PS2 Web Recomp port misbehaves, updating the browser is the first move, ahead of every other troubleshooting step — it is free, takes a minute, and quietly resolves a surprising share of launch-week issues on its own.

Troubleshooting the Common Failures

The failure signatures players actually report, matched to their fixes. A port that loads but renders nothing usually means WebGPU fell back to software — recheck the internal GPU page and the hardware acceleration setting. A port that refuses to start with a WebGPU-not-available message on a machine that should support it almost always has an outdated browser version or a driver on the browser's blocklist; update both. A port that ran yesterday and fails today typically lost its storage to a cleaner extension or a profile change — a clean-profile test isolates it in seconds. And a port that stutters on a capable machine is usually running on the integrated GPU of a dual-GPU laptop — the per-application graphics setting in the OS fixes it permanently.

None of these are exotic. They are the same five failures every browser-GPU application collects, and each has a two-minute resolution once named.

The Bottom Line

The requirements story for browser-played PS2 games is the friendliest in all of retro gaming: a current browser, hardware acceleration on, and any ordinary modern computer. There is no install stack to assemble, no per-game configuration to tune, no compatibility lottery to win before playing — the PS2 Web Recomp philosophy is that the tab does the work. Pass the two-minute check, keep the browser current, and everything else on this tracker is one link away.

One closing perspective for readers who remember the old days of making emulation work: the entire ritual this page describes replaces — the downloads, the BIOS hunt, the plugin configuration, the per-game settings archaeology — has collapsed into keeping a browser updated. That is not a small convenience; it is the difference between a hobbyist pursuit and something anyone can do on the laptop they already own. The check is two minutes because the machinery behind it did the rest.