What a compatibility check can prove
The creator’s launcher checks for navigator.gpu, then asks the browser for a graphics adapter with requestAdapter(). If either check fails, it shows a warning and stops before continuing into the client. Those are separate checks: an exposed API can still return no adapter.
Use the stages below to describe your result precisely. A positive result at one stage does not establish the next.
On a small screen, scroll the table sideways to read every column.
| Result | What it establishes | What to do next |
|---|---|---|
| No WebGPU API | This browser session does not expose the interface required by the launcher. | Check the browser, operating system and secure page address before attempting the game. |
| API visible; no adapter returned | The interface exists, but this session has not provided an appropriate graphics adapter. | Check the browser’s GPU status and platform conditions. This does not identify one guaranteed cause. |
| An adapter is returned | The launcher’s basic graphics preflight can pass. | Open the original game and check whether client loading and startup succeed. |
| The character menu appears | The client reached its menu on this setup. | Try the documented start and controls. A menu is not evidence of sustained gameplay. |
| A run responds to input | That particular session reached gameplay. | Record the environment and result. It does not certify every zone, a full run or a target frame rate. |
Browser compatibility by operating system
The WebGPU working group’s status page was reviewed October 28, 2026; its last edit was October 2. These are API availability conditions, not Azeroth Survivors minimum requirements. Use a current stable browser and check your exact system.
On a small screen, scroll the table sideways to read every column.
| System and browser | Documented WebGPU API status | Decision before play |
|---|---|---|
| Chrome / Edge on macOS, Windows x86/x64 or ChromeOS | Available from 113. Windows ARM64 is listed separately as requiring an experimental setting. | Check architecture, then adapter availability. |
| Firefox on Windows or Apple Silicon Mac | Windows: 141. Apple Silicon: 145 with macOS 26+, or 147 for its other macOS versions. | Other Mac hardware and Linux are listed under Nightly, rather than ordinary stable support. |
| Safari on Mac, iPhone or iPad | Enabled by default with macOS Tahoe 26, iOS 26 and iPadOS 26. | API availability does not establish game controls or performance on a phone or tablet. |
| Chrome / Edge on Linux | Intel Gen12+: 144. NVIDIA: 147 with driver 535.183.01+ and Wayland. Other combinations have experimental conditions. | Check GPU, driver and display session. |
| Chrome on Android | Selected GPUs with Android 12+ from 121; Imagination with Android 16+ from 139. Other GPU conditions differ. | Check the source’s hardware entry. This is not an Android game-playability result. |
Check your setup before opening the game
Keep this check in the browser you intend to use for play. A result from another browser, profile, machine or remote session describes a different environment.
- Identify the setup. Note the operating-system version, device model and GPU if known. Open the browser’s About page, record its full version, complete any normal update and restart if requested.
- Compare the platform conditions. Use the matrix and its source, including architecture and GPU restrictions. Do not treat a developer preview or an experimental flag as equivalent to ordinary stable-browser support.
- Inspect the graphics status. In Chrome, enter
chrome://gpuin the address bar and look for the WebGPU status. The Chrome documentation explains that acceleration settings, blocked hardware and platform conditions can prevent an adapter. A WebGL or general graphics-acceleration result is not a WebGPU result. - Use the original HTTPS page. Open wow.aethus.pl directly in its own tab. WebGPU requires a secure context, and the creator’s client rejects third-party frames. A copy, embedded page or detector on another origin is not the original game’s check.
- Record the furthest successful stage. Distinguish the API warning, adapter warning, loading screen, character menu and responsive run. For the actual start and keyboard inputs, follow the menu and controls guide. If a stage fails, take its exact message to the loading and WebGPU troubleshooting guide.
Browser play, Windows and handheld devices
On a Mac or Linux computer, assess the browser route against the documented system and graphics conditions. This page does not establish a native Mac or Linux release. On Steam Deck, record the installed operating system, browser, graphics stack and input method; the device name alone cannot establish compatibility. No Steam Deck game session was tested for this guide.
The creator also offers a Windows download. Review the Windows source and preparation guide before choosing it. Browser WebGPU availability is not an installation check for that separate package, and these browser documents do not establish its Windows version, RAM, graphics or storage requirements. The Windows package was not run for this guide.
An iPhone, iPad or Android browser may meet a documented WebGPU condition without providing a usable game experience. Touch input, screen layout, sustained performance and a complete run need game-specific device testing; this review does not provide it.
Record an environment someone else can reproduce
If you need help, keep a short record of the conditions and the highest stage reached. Use the creator’s linked community route from the loading-report guide; this independent site cannot change the game’s browser support.
Copy only relevant GPU-status lines or error text. Redact personal paths, account names and unrelated tabs. A public save upload, full browser profile or complete diagnostic dump is not needed to describe compatibility.
- Date and time; original page address; game version only if the interface actually displays one.
- Device model, CPU architecture if known, operating-system name and full version.
- Browser name and full version; normal or remote session; whether the browser is managed by an organization.
- GPU model and driver version if available; whether graphics acceleration is enabled; relevant WebGPU status.
- Highest stage reached and the exact warning or first relevant error, followed by one attempted change and its result.
- For a session that starts: input method, whether movement and a card selection respond, and how far the observation lasted. Describe a short test as a short test.
Evidence and review limits
This review checked the creator’s current launcher and the linked browser documentation on October 28, 2026. The launcher URL includes the resource stamp 56cdea9067bb; that is an asset identifier, not a game version.
The API matrix is documentation evidence, not a device test matrix. No new game, GPU, Windows, phone or handheld session was run for this review, and the sources do not establish a universal minimum hardware specification or a performance target. Browser updates, drivers and the game can change the result, so retain the environment alongside any successful or failed test.
Common questions
Does a WebGPU support result mean Azeroth Survivors will run?
No. The API must be exposed, the browser must provide an appropriate adapter, and the game must still load and start. A generic detector cannot establish controls, sustained gameplay or performance.
Is Firefox automatically incompatible?
No. The reviewed WebGPU status lists stable support on Windows and under specified Apple Silicon Mac conditions. Other systems have different conditions. Check your exact browser, OS and hardware, then the original game.
Does an adapter result give me minimum GPU or RAM requirements?
No. It describes one browser request, not a published game specification or a benchmark. This review cannot turn it into a GPU model, memory minimum or guaranteed frame rate.
Sources & check notes
Sources reviewed on October 28, 2026. A source review is distinct from a successful gameplay or device test.
- Azeroth Survivors — creator’s page, October 28 review (opens in a new tab)
What this source establishes
Current public HTML was read on October 28, 2026 and references rogue.js with resource stamp 56cdea9067bb. This establishes the creator’s current browser entry and script identity; it does not establish a game version, minimum specification or device test.
- Creator’s browser launcher — graphics preflight (opens in a new tab)
What this source establishes
Static source review: gpuProblem first checks navigator.gpu, then calls requestAdapter and treats an exception as no adapter. start stops with a warning when that preflight returns a problem. The source also rejects third-party frames and offers graphics diagnostics. Passing this check does not establish device creation, client loading or gameplay. The resource stamp is not a semantic game version; the script was not executed for this review.
- WebGPU working group — browser implementation status (opens in a new tab)
What this source establishes
Read on October 28, 2026; the page shows an October 2, 2026 edit date. Provides browser WebGPU implementation conditions by OS, architecture, GPU and browser version. It is not an Azeroth Survivors compatibility certification. Development-channel or flag-dependent entries must not be presented as ordinary stable support.
- Chrome for Developers — WebGPU troubleshooting (opens in a new tab)
What this source establishes
Official Chrome documentation, last updated October 17, 2025, reviewed for secure-context requirements, graphics acceleration, adapter availability and chrome://gpu diagnostics. Its older platform overview does not override the newer working-group status snapshot. No experimental flags, blocklist bypass or browser configuration changes were performed.
- MDN — GPU.requestAdapter() (opens in a new tab)
What this source establishes
Developer reference, last modified May 5, 2026. Describes the secure-context requirement, the browser’s adapter choice and a null result when no appropriate adapter is available. Requesting a GPU device and satisfying application requirements are separate later steps. No GPU request was run for this review.