Runs on this device
Browser capability check
This checks APIs and requests a WebGPU adapter. It does not launch a game, benchmark your GPU or upload files. Results stay in the page.
Ready to check. No test has run yet.
Interpreting the checks
| Check | What a result establishes |
|---|---|
| Secure context | The page is using an environment in which restricted browser APIs may be available. HTTPS and localhost are common examples. |
| WebAssembly | The browser exposes the runtime used by the compiled game. This does not certify every feature of a game build. |
| WebGPU API + adapter | The API exists and the browser can obtain an adapter now. Drivers, policy, remote desktop or the active GPU can still affect operation. |
| Cross-origin isolation | Whether this document has the isolated context required for shared-memory threads. The editorial guide does not request game-runtime isolation. |
| SharedArrayBuffer | Whether shared memory is exposed in this document; availability depends on its isolation policy. |
| Gamepad API | Whether the browser exposes the API. A specific controller still needs connection, a button press and a practical input test. |
Why the guide can show isolation as inactive
This editorial site is not a hosted game runtime. Its ordinary content pages need no SharedArrayBuffer threads. An inactive isolation result here describes this page’s headers, not a defect in your computer. For the actual local game, use the supplied server and inspect the game page’s context.
python3 scripts/serve.py build/web-mygame games/mygame/disc.isoThe game server sends Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp. It also supports HTTP Range requests for disc streaming. A different file server might load the HTML yet omit behavior the game needs.
Browser and operating-system notes
The maintainer documents Chrome and Edge with WebGPU on Windows and macOS, and describes additional setup on Linux. Browser support changes with release, operating system and GPU. Prefer the actual API and adapter result over assuming support from a browser name. This checker does not ask you to weaken browser security settings.
If the API is present but no adapter is returned, record the environment and inspect the browser’s GPU diagnostics. A blocked or unavailable adapter is different from the API being absent. The upstream renderer can fall back to software, but the README says that fallback is suitable for menus and too slow for demanding 3D.
What is not tested
The checker does not execute the PS2 runtime, test disc contents, measure frame rate, validate game compatibility or access saved memory cards. A positive capability result is a starting point for a local build, not a pass certificate. For a failure during play, use the symptom-based troubleshooting guide.
Sources: upstream browser notes, MDN WebGPU, MDN crossOriginIsolated.