BEFORE YOU BUILD

Check your browser.
Know your next step.

A quick check for WebGPU and the WebAssembly features the project requires. Find missing pieces before spending time on a local build.

01 / YOUR CURRENT BROWSER

Does it have the essentials?

Run this on the device and browser you plan to play on.

Ready when you are. No game files needed.
  • Secure context

    HTTPS or a trusted localhost page

    Not checked
  • WebGPU adapter

    An adapter for the GPU renderer

    Not checked
  • WebAssembly JSPI

    JavaScript promise integration

    Not checked
  • WebAssembly exceptions

    The try_table instruction

    Not checked
  • WebAssembly tail calls

    The return_call instruction

    Not checked
  • WebAssembly SIMD

    Vector instruction support

    Not checked

The checks run on your device. This tool does not upload or save your results.

02 / ON YOUR GAME SERVER

One more check belongs
on the game page.

Shared memory requires cross-origin isolation. That depends on the server serving your game, so this community website cannot verify your local build’s headers.

Check on your game page

This website’s isolation setting is separate from your game server’s. It does not change the browser results above.

Use the project’s supplied server from your checkout:

python3 scripts/serve.py build/web-mygame games/mygame/disc.iso

Replace mygame with your build’s name. On the game page, the runtime’s startup check must confirm cross-origin isolation; its Start action lists missing features.

Check the required server headers
03 / KEEP MOVING

From a result to a working setup.

Feature check, not a gameplay benchmark. Passing these checks does not establish frame rate, game compatibility, a successful build, or full playability. No game is loaded or tested here. Checks follow the upstream startup checks at ebf86d3 and the browser’s WebGPU adapter response. See WebGPU adapter behavior and cross-origin isolation for browser API details.