# Cricket 07 browser requirements: PC, Mac and WebGPU

Check desktop browser requirements, WebGPU support, and OPFS storage needs for Cricket 07 browser play.

## Recommended desktop browsers

Use an up-to-date desktop version of **Google Chrome** or **Microsoft Edge** on Windows or macOS with hardware acceleration enabled. When you click Play, the Cricket 07 browser player runs an automatic preflight check before requesting any large downloads.

## Required web platform features

Running EA Sports Cricket 07 natively in a browser tab relies on four modern browser APIs:

1. **WebGPU (`navigator.gpu`)**: Translates Cricket 07 Direct3D draw calls into modern GPU shaders at 60 frames per second.
2. **Cross-Origin Isolation & `SharedArrayBuffer`**: Enabled by this site's `COOP: same-origin` and `COEP: require-corp` response headers for low-latency audio and memory sharing.
3. **Origin Private File System (`navigator.storage.getDirectory`)**: Stores the unpacked `c07game` archive (`515 MB` to `1.17 GB`) and `userdata` saves on your local drive.
4. **AudioWorklet (`c07-ring`)**: Streams multi-channel stadium audio, bat-on-ball effects, and commentary without main-thread crackle.

## Mobile, Android and iPhone status

Although the `cricket-07.org` interface adapts cleanly to mobile screens, mobile browsers are not verified for running the Cricket 07 WebAssembly runtime. Phone browsers frequently lack desktop WebGPU adapter features, sufficient memory headroom, or persistent OPFS quota for gigabyte-scale game archives.

## Troubleshooting missing WebGPU adapters

If the preflight check reports that WebGPU is unavailable, open `chrome://settings/system` (or `edge://settings/system`), turn on **Use graphics acceleration when available**, relaunch your browser, and try launching the Cricket 07 browser player again.

## References

- [Cricket 07 WebAssembly & WebGPU runtime reference](https://cricket07.dhaiwat.com/)