How to Play PS2 Games in Your Browser: The Walkthrough

Playing a PlayStation 2 game in a browser tab is now a real thing you can do this afternoon. The PS2 Web Recomp scene has produced working browser ports of real commercial games, led by God of War II. This walkthrough takes you from zero to first session: the browser check, where ports live, how controls and saves work, and what honestly differs from playing on native hardware.

Step One: Pass the Browser Check

WebGPU is the hard gate. Every PS2 Web Recomp port depends on it, because the hardware recreation renders through that API. Current desktop Chrome, Edge and Firefox all ship WebGPU support, but support being shipped and support being enabled are different things on some machines.

The two-minute check: open your browser's internal GPU page (chrome://gpu in Chrome and Edge, about:support in Firefox) and look for WebGPU in the graphics feature status. It should read Hardware Accelerated. If it reads Software only or Disabled, the requirements guide on this site walks through the fixes — hardware acceleration enabled in settings, an up-to-date browser version, and on some laptops, forcing the discrete GPU for the browser.

What does not work yet: most mobile browsers. WebGPU on phones is arriving but immature, and a PS2 title assumes far more memory bandwidth than a mid-range phone delivers comfortably. Treat PS2 Web Recomp as a desktop experience for now.

Step Two: Find the Hosted Ports

The PS2 Web Recomp ports are published on the web — pages that load the WebAssembly build and the runtime, then ask you for the game data. The canonical sources are the project's own GitHub releases and the pages the community links from them. The playable games list on this tracker carries the current state of what is hosted where, with status for each title.

Apply normal web hygiene, the same as any emulation scene: official repositories first, community-verified mirrors second, and sites that ask you to install something or disable your antivirus never. A real PS2 Web Recomp port needs nothing but the browser you already checked.

Step Three: Bring Your Game Data

This is the legal step and there are no shortcuts. The port expects the game image you have the right to use — in practice, an ISO dumped from a disc you own. The recompilation pipeline that produced the port translates the game's code; it does not include the game. When the hosted page offers a file picker for the game data, that is the moment your own dump goes in.

The FAQ page covers the legal frame in depth. The operating rule: own the disc, dump the disc, use the dump. Communities around the scene can point you to dumping tools and guides for reading PS2 discs on modern drives.

Step Four: Play

Loading a PS2 Web Recomp port feels like loading any heavy web application: a progress bar while multi-hundred-megabyte assets stream in, then the game's own boot sequence. From there you are playing. Keyboard mapping follows the classic layout the scene has converged on — arrows or WASD for the left stick, the home-row cluster for face buttons, shoulder keys above — and the better ports expose a remapping panel or accept gamepad input through the browser's standard Gamepad API, so a USB or Bluetooth controller usually just works.

Performance expectations, honestly stated: ports built on the current runtime run lighter titles at full speed on ordinary hardware, and the flagship God of War II port performs strikingly well. Heavier special-effect sequences can dip, because the hardware recreation is young. The scene's trajectory is upward — every runtime release widens the comfort zone — but today's reality is per-title, per-scene variance, and the games list tracks exactly that.

How Saves Work

Browser ports persist saves in browser storage — localStorage or the Origin Private File System depending on the port. Two practical consequences. First, saves survive page closes and browser restarts on the same browser profile. Second, storage belongs to the profile: a different machine, a different browser, or an aggressive privacy extension that clears site data on exit will each eat your progress. If a PS2 Web Recomp port offers an export-save feature, use it after meaningful sessions.

What Differs from Native or Emulated Play

Compared with a traditional emulator setup, the differences are mostly pleasant: nothing to install, nothing to configure beyond the browser itself, and updates to a port arrive as simply as any website update. Compared with playing on real hardware, the differences are the ones you would expect — display scaling rather than a CRT, remappable input rather than a DualShock port, and a young hardware recreation rather than twenty-five-year-old silicon with its exact behaviors.

Controls in Detail

The mapping the scene has converged on deserves its own paragraph, because it is the first ten minutes of everyone's experience. The DualShock 2 layout translates naturally to a keyboard: the left stick lands on WASD or the arrow cluster, the face buttons — cross, circle, square, triangle — map to keys within reach of the right hand, and the shoulder buttons take the row above. Games with heavy button timing, fighting games especially, reward the few minutes spent in a port's remapping panel aligning the layout to your muscle memory.

Physical controllers change the experience entirely, and this is where the browser platform quietly shines. The standard Gamepad API means a USB or Bluetooth controller — an Xbox pad, a PlayStation controller, most third-party gamepads — is detected by the browser itself, and well-built ports pass that input through with no configuration beyond pressing a button to wake the connection. Playing God of War II with an actual controller in front of a browser window is the moment the whole thing stops feeling like a demo and starts feeling like just playing the game.

Performance Tuning That Actually Matters

Three levers move the experience, in order of impact. First, the browser version — WebGPU performance work is landing release by release, so current means faster, full stop. Second, closing the tab's competition: a browser window full of other GPU-using pages competes for the same resources, and a clean window measurably smooths heavy scenes. Third, display scaling — running the browser window at the display's native resolution rather than a scaled mode keeps the render path simple. What does not matter, pleasantly, is nearly everything else; there are no per-game graphics settings labyrinths to master, because the runtime handles the console-side decisions itself.

Troubleshooting the First Session

The failures newcomers actually hit, with their fixes. Nothing renders — WebGPU fell back to software; the requirements page's check applies. The page loads but rejects the game data — the dump format or hash does not match what the PS2 Web Recomp port expects; re-dump from the disc with a verified tool. Input feels dead — the browser tab lost focus or a controller needs its wake-button press. Saves vanished — browser storage was cleared by an extension or profile switch; export after meaningful sessions going forward. Every one of these has a forum-documented resolution; the scene's discussions are unusually helpful to newcomers precisely because everyone in them was new last week.

Where to Go From Here

The path from here is short: requirements confirmed, walkthrough followed, first title played. The natural next stops are the playable games list for what to try second, the God of War II profile for the flagship experience in depth, and the technology pages for the machinery that made the session you just had possible. The scene's ports will keep arriving; the habits from this page — current browser, own dumps, exported saves — are the complete maintenance schedule.