PS2 Recompilation in 2026

Why the PlayStation 2 is hard to recompile

The PlayStation 2 is not a single processor with a simple memory map. Its main CPU, the Emotion Engine, runs MIPS R5900 code with vector units that developers used for everything from geometry to audio. Its Graphics Synthesizer has an unusual fixed-function pipeline and a small, fast embedded memory. Games were written around those constraints, often in assembly, and often with timing assumptions that only make sense on the original hardware.

That shape makes PS2 recompilation harder than N64 or GameCube work. The CPU side can be translated, but the vector units, the DMA paths and the graphics pipeline each need a runtime that behaves like the console. A project can produce a native executable and still fail on a specific effect, a timing-sensitive minigame or a game that depends on the Graphics Synthesizer's fill rate.

By late 2026 three routes are visible in the catalogue. Static recompilation translates the game's machine code ahead of time into a native program. Decompilation projects reconstruct readable source that ports can build on. Browser builds compile translated code to WebAssembly and draw with WebGPU. Each route has a different maturity curve, and each one produces a different kind of artefact for the player.

Route one: PS2Recomp and native ports

PS2Recomp is the tool most native PS2 ports are built with. It translates MIPS R5900 code into C++ and links the result against a runtime that reimplements the console's services. The output is a desktop program that reads assets from the player's own disc image. It is not an emulator: the game's logic runs as compiled code, and the runtime provides the pieces the original console would have provided.

The catalogue currently lists several projects on this route. Urban Reign is the clearest example: urban-reign-recomp is marked Playable and has reached v1.4.1, with the project documenting a 64-bit Windows build and DirectX 11 requirements. Def Jam Vendetta Recomp is marked In Progress and has moved through a rapid series of releases to v0.6.2, which is a reminder that release numbers and status labels measure different things.

Killzone, Burnout 3: Takedown and Dragon Quest VIII are also listed with PS2Recomp-based projects, all marked In Progress at the last check. Their repositories are active, but activity is not the same as a verified full playthrough. Some builds reach menus and early gameplay, some are further along, and the project README is the only reliable description of where each one stands.

God of War has more than one project, including a native PC build marked Playable and a recompilation marked In Progress. That pattern is common on the PS2: a game attracts several teams using different approaches, and the catalogue groups them on one page so the statuses can be compared.

Route two: PS2 Web Recomp and the browser

PS2 Web Recomp is the project that made PS2 recompilation visible outside the desktop-port community. It translates the game's code to C++, compiles that to WebAssembly, and draws the Graphics Synthesizer with WebGPU compute shaders. The main CPU is not interpreted; the translation happens ahead of time. Gran Turismo 4 was the first title brought up this way, and God of War II followed through the same tooling.

The browser route has unusually specific requirements. The page needs WebGPU, so current Chrome or Edge on Windows and macOS work out of the box while Linux usually needs flags enabled. The build uses SharedArrayBuffer for threading, which means it must be served cross-origin isolated; the project includes a server script that sets the required headers. The page is built on the player's machine from their own disc image, not hosted by the project.

Both Gran Turismo 4 and God of War II are marked In Progress in the catalogue rather than Playable. The project's own documentation describes substantial progress, including the move from a software rasteriser to WebGPU compute shaders and a large gain in frame rate, but a browser build that runs a race is not the same claim as a full game verified end to end. The distinction matters when you are deciding whether to spend an evening on setup.

The browser route is also the clearest illustration of why these projects cannot ship game data. The generated WebAssembly and the page shell are project output; the disc image is the player's. A hosted build that worked without your own disc would be distributing the game, which is exactly what the project avoids.

Route three: decompilations and the ports built on them

Decompilation is the slow route, and on the PS2 it often starts with the game's executable rather than a cartridge. Projects rebuild the original machine code as C or C++, function by function, and measure progress as the share of code that compiles back to a byte-identical result. That percentage is a code-matching metric, not a gameplay metric.

Gran Turismo 4's decompilation is the most closely watched example. Its official objdiff report recorded 89.6% matched code at the last check in November 2026, up from 89.3% a few days earlier. That figure describes how much of the executable has been reconstructed, not how much of the game is playable. The separate PS2 Web Recomp project is a different codebase with its own status.

OpenGOAL is the best-known decompilation-derived project on the platform. It covers the Jak and Daxter trilogy from one repository: Jak and Daxter and Jak II are marked Playable, while Jak III remains In Progress. The project decompiles Naughty Dog's GOAL code and recompiles it for x86-64 with its own compiler, which is why its releases behave like native ports rather than emulator sessions.

Ratchet & Clank has the most crowded page in the catalogue. OpenRAC maintains a decompilation, Lombyte is a separate project, and several native builds exist, including one marked Playable at v0.6.0 and another listed as rac-rs. ICO is covered by ico-pc, which has reached v0.11.6 and remains In Progress, and by a matching decompilation. Kingdom Hearts has a decompilation that rebuilds the Japanese and Final Mix executables. Sly Cooper has ProjectCane marked Playable alongside other decompilation work. Resident Evil Code: Veronica X has a decompilation marked Playable, with a separate recompilation still In Progress.

The pattern is consistent: decompilation projects are the long game, and the ports built on top of them inherit both the strengths and the limits of the reconstruction. A decompilation that is 100% matched is not automatically a good port, and a port that runs well does not mean the decompilation is complete.

What “Playable” means on this site

The catalogue uses four status labels. Playable generally means the project itself states that the game can be played through. In Progress means work is active and the project does not claim completion. Announced means support has been stated but not released. Unknown means the current state could not be confirmed from the project's own material.

Those labels come from project repositories and release notes, not from independent testing. A Playable label does not guarantee that every level, cutscene or save file works on every machine. It means the project's own documentation supports the claim. When the catalogue and the project disagree, the project wins.

The PS2 pages also record release tags where a project publishes them. A tagged release is evidence that the project is active and that a build exists; it is not a statement about completion. Def Jam Vendetta's move from v0.4.x to v0.6.x in a short period is a good example of how quickly release numbers can change while the status label stays In Progress.

Reading progress percentages

Decompilation progress is usually reported as a percentage of matched code. On the PS2 that number is produced by comparing rebuilt functions against the original executable. A higher percentage means more of the binary has been reconstructed; it does not mean the game is more playable, because the remaining functions can include critical systems and because the porting work sits on top of the reconstruction.

For recompilation projects, progress is rarely reported as a single percentage. Projects describe milestones instead: boot, menus, first level, save support, audio, specific bosses. Those milestones are more useful than a number, but they are harder to compare across projects.

When a project publishes both a percentage and a release, treat them as separate facts. The percentage describes the reconstruction; the release describes what the maintainer chose to ship. Neither one replaces reading the project's own notes about known issues.

How to choose a PS2 project to try

Start with the version of the game you own. Many PS2 projects target a specific region and revision, and some check a serial or hash before they run. A project that accepts only one disc is not being difficult; it is built around one executable. Check the catalogue entry for the required version, then check the project README for the exact file it expects.

Prefer a project whose status and documentation agree. A Playable project with a narrow target and clear setup notes is usually a better first experience than an In Progress project that claims broad support. If a project publishes a ready-made build, start there rather than building from source; if it publishes only source, read the toolchain requirements before you begin.

Expect the setup to take longer than a modern game install. Dumping a disc, checking a hash, extracting assets and configuring a launcher are all part of the workflow. The how-to-play guide on this site covers the common sequence, and the legality guide explains why the game files have to come from your own copy.

What to expect next

The PS2 scene is moving on three fronts at once. Static recompilation keeps adding games as PS2Recomp matures. Decompilation projects keep climbing toward complete matching, with Gran Turismo 4 the most visible example. Browser builds are experimenting with WebGPU and WebAssembly, which could eventually make a PS2 game run in a tab without a native install.

None of those routes removes the ownership requirement. Every project listed here expects a copy of the game, and every one of them ships code rather than assets. That boundary is what makes the scene defensible, and it is the reason this catalogue links to repositories instead of downloads.

Where an emulator still makes sense

Recompilation is not a replacement for emulation across the whole library. Emulators run any disc, including games no project has touched, and they are the practical way to play most of the PS2 catalogue. Recompiled ports exist for a small number of games, and they exist because someone was willing to spend months on that specific executable.

The trade-off is different too. An emulator can be tuned per game with resolution scaling, texture replacement and input latency options, but it carries the overhead of emulating the console. A recompiled port runs natively and can be shaped around modern hardware, but it only works for the game it was built for and it inherits whatever the project has and has not implemented.

For preservation, both matter. Emulation keeps the broad library accessible; recompilation and decompilation keep specific games alive in a form that can be maintained and improved. A catalogue that lists only one of those routes would misrepresent how people actually play PS2 games in 2026.

Hardware and settings that matter

PS2 ports vary in what they demand. Some are CPU-bound because the game's logic is now compiled code running on one or two threads; others are GPU-bound because the renderer is doing work the Graphics Synthesizer did in fixed-function hardware. A machine that runs one port comfortably can struggle with another for reasons that have nothing to do with raw performance.

Graphics API support is the most common hard requirement. Projects built around Direct3D 12, Vulkan or Metal list a minimum feature level, and laptops with switchable graphics sometimes launch on the integrated GPU by default. If a port refuses to start or shows a black screen, confirming the active GPU is often more useful than changing game settings.

Storage and memory matter less than they used to, but disc images are large and some projects cache extracted assets next to the executable. Keep enough free space for the image, the extracted assets and the build itself. On handhelds and small laptops, that can be the difference between a working setup and a failed extraction.

The bottom line

PS2 recompilation in 2026 is no longer a single experiment. There are native ports with tagged releases, a browser project with a working Gran Turismo 4 build, long-running decompilations and a growing set of ports built on them. The quality varies enormously, and the status labels on this site are deliberately conservative.

If you own the game and want to try the platform, start with a Playable project that documents its target version, follow the README exactly, and treat In Progress projects as experiments rather than replacements. The catalogue exists to make that choice easier, not to promise that every listed project is finished.