ARAM
TROUBLESHOOTING

What to check when ARAM does not run

Separate download failures, input-format failures, and unimplemented title services to identify the right next step quickly.

The web player does not start

  1. Check the browser.
    Try a current desktop version of Chrome, Firefox, or Edge first.
  2. Allow the approximately 52MB runtime download.
    A slow connection, data saver, content blocker, or managed-network policy can block the WebAssembly file.
  3. Switch between Stable and Nightly.
    During a deployment update, a channel can temporarily have a mismatched loader and runtime.
  4. Record the exact error.
    Failed to load runtime loader and Failed to start identify 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

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.