Tool · runs locally

Can my browser run it?

Checks the features browser game ports depend on, then tells you which games on the list should start. Nothing is uploaded.

    What should run

    • Run the check to see results.
    How classic PC games like Quake and Half-Life run in a browser: the game's source code is compiled to WebAssembly and WebGL, then combined with free demo data or files from your own copy. Needs WebAssembly, WebGL 2 and sometimes SharedArrayBuffer.
    Why these features matter: every port is compiled to WebAssembly and draws with WebGL.

    What each test means

    WebAssembly
    Runs compiled C, C++ and Rust code at near-native speed. Every port on the list needs it.
    WebGL 2
    The 3D graphics API most ports draw with. Missing it usually means an old browser or a blocked GPU driver.
    WebGPU
    The newer graphics API. A few modern projects need it: the Skate 3 recreation only runs in Chrome or Edge 113+ with WebGPU.
    SharedArrayBuffer
    Multi-threading for heavier engines such as reVC (Vice City). The game's host must enable it, so this test only shows whether the current page has it.
    Memory & CPU cores
    Rough guide to whether big downloads and 3D scenes will be smooth. Browsers round these numbers.

    Questions

    Why does a browser game get stuck on a black screen?

    Usually the browser is missing WebGL 2 or SharedArrayBuffer, the graphics driver is blocked, or a large first download was cut off by the network.

    What is SharedArrayBuffer and why do some games need it?

    It lets a game run code on several threads at once. Browsers only enable it on sites that send special security headers, so whether you have it depends on the game's host as well as your browser.

    Does this tool send my data anywhere?

    No. Every test runs locally in your browser and nothing is uploaded.