Azeroth SurvivorsMegabonk.org · Independent guide
Menu
Original game · Independent guide

Check the phone route before moving your save

Try the original wow.aethus.pl in a current WebGPU-capable browser on your phone or tablet. A browser name or OS version alone does not guarantee a usable graphics adapter or successful play. Export your existing save before switching clients.[1]

Megabonk.org editors · Reviewed 29 October 2026 · Original v0.127.0 · Source-based, not a playtest

Choose between two different routes

RouteWhat it usesEvidence limit
Original browser pageThe phone browser, its GPU access and the game’s input handling.Launcher/client support is not a tested-device compatibility list.
Windows build through WinlatorA Windows build and a community compatibility layer on Android.One public player reports success; no universal configuration or performance guarantee is established here.

The Winlator report is by Reddit user starsforfeelings; other replies report mixed browser outcomes. Its indexed and displayed dates disagree, so we do not assign it an exact publication date. [2]

Browser checks, in order

  1. Open Aethus’s original game ↗ (external website, opens in a new tab) directly, outside an embedded frame.
  2. If the page reports no WebGPU, update the browser and inspect whether the device exposes the required GPU feature. Do not use a PC-only flag as a blanket phone fix.
  3. Let the initial download complete; note whether its progress counter moves. A server quota message is a different branch from a GPU warning.
  4. Inspect the actual touch/input controls before committing to a long run. A larger display does not prove that all inputs work on your device.
  5. If the original browser route is unsuitable, retain the PC save and check current original-author/community guidance for your device. Do not install a purported mobile port just because it uses the game’s name.

[1][3]

Your PC and phone do not share storage automatically

Export from the client where your progress exists; export any phone progress separately before importing. Import replaces the destination. Keep both original files until heroes, equipment and zone unlocks match your intention. Browser addon installation is separate again. [4][5]

Follow the full backup and migration order →

What has and has not been checked

We inspected the original launcher and client text and read the public mobile report. We have not completed a run on a physical Android phone, iPhone or iPad, benchmarked Winlator, or verified every cross-version save transfer. Device model, GPU, browser, game version and the exact warning are more useful troubleshooting details than “mobile does not work”.

Sources & verification

  1. Aethus · browser launcher ↗ (external website, opens in a new tab) — Inspected 29 October 2026; resource stamp c33ee61002a5. Original-host and frame checks, startup handling and local-save fallback. The resource stamp is not the game version.
  2. Reddit · starsforfeelings and replies ↗ (external website, opens in a new tab) — Read 29 October 2026. One Winlator report and mixed browser replies; page and search-cache dates differ, so the exact post date is unconfirmed. Device-specific anecdotes.
  3. Aethus · original game ↗ (external website, opens in a new tab) — Original v0.127.0 / d1c85453 public client text inspected 29 October 2026. Single-source menu and talent evidence; no completed run or damage benchmark.
  4. Aethus · browser save bridge ↗ (external website, opens in a new tab) — Inspected 29 October 2026. File export and file selection; the client itself validates imports. Not a save-recovery test.
  5. Aethus · browser addon installer ↗ (external website, opens in a new tab) — Inspected 29 October 2026. ZIP handling, per-browser IndexedDB files and next-run loading. Not proof every addon is compatible.
Back to guide ↑