The web player does not start
- Check the browser.
Try a current desktop version of Chrome, Firefox, or Edge first. - Allow the approximately 52MB runtime download.
A slow connection, data saver, content blocker, or managed-network policy can block the WebAssembly file. - Switch between Stable and Nightly.
During a deployment update, a channel can temporarily have a mismatched loader and runtime. - Record the exact error.
Failed to load runtime loaderandFailed to startidentify different stages.
An input does not open
Format not recognized
Renaming an extension does not turn a file into a WIPI container. Check that the original package is intact and belongs to a WIPI, JAR, or DAT family that ARAM handles.
Loads but does not execute
A recognized container can still stop on a carrier OEM service, device-specific behavior, or an ARM instruction that is not supported yet.
An integrity-checked package link fails
- The package URL must use HTTPS and cannot contain a username or password.
- The source host must allow a browser cross-origin request through CORS.
- The package must be at most 32MiB and the link must include a 64-character SHA-256 digest.
- A SHA-256 mismatch means the file changed or the digest is wrong. Refusing to run it is the intended behavior.
Information to include in a report
Include the operating system and browser, Stable or Nightly channel, ARAM version, input kind, image SHA-256, last compatibility milestone, and exact error. Do not send the original game, firmware, keys, or a memory dump.