Start with the right install route
D2R Mobile is an independent open-source compatibility project for playing the Switch edition of Diablo II: Resurrected offline on compatible Apple devices. You need your own game files; a clean shell is not a playable app. Check the device table, choose a build for your operating system, then follow one installation route. Android currently has experimental community work, not a stable release verified by this site.
The short version
You are not downloading a conventional App Store game. Installation has three distinct parts:
- Your game files: the supported Switch executable and resource files, obtained from your own purchased copy.
- An assembled app: the project's open-source host combined with the game-derived program and shaders. A clean source archive or shell alone cannot play.
- Installation and resource import: signing the iOS package, or opening the correct Mac build, then supplying the resource archives.
The project patches selected ARM64 instructions ahead of time and implements the services and graphics interface the game expects. It is not a complete Switch system emulator. Graphics still need translation to Metal, so native CPU execution is not a blanket guarantee of performance.
1. Check your device first
Open the compatibility table before preparing files.
- A17 Pro and newer supported iPhones, and M-series iPads, use the standard resource route.
- Supported A14–A16 devices with at least 6 GB RAM need an additional Legacy Device Pack made from your own files. A14 devices with 6 GB remain unverified in upstream's current table.
- Devices with only 4 GB RAM and A13-or-earlier hardware are currently unsupported. A12X/A12Z iPad Pros are not an exception.
- The Mac app requires Apple silicon, not an Intel Mac.
Your operating system chooses the package: iOS 26+/macOS 26+ use the default build; iOS 18–25/macOS 15–25 need the older-API build. The texture-pack requirement is a separate decision based on the chip.
2. Prepare the supported game version
The file checklist explains the exact layout. The upstream requirement is Switch 1.0.34.0, including Reign of the Warlock. The internal PC-style identifier 3.3.94012 refers to that same supported version in the tooling.
A clean shell is open-source build input. A finished IPA or prepared-input package can contain rewritten commercial code and game-derived assets even if it does not contain the multi-gigabyte resource archives. Do not redistribute those outputs. Ownership and a private repository are not substitutes for permission.
3. Pick one route
| Your situation | Route | What to expect |
|---|---|---|
| You have an Apple silicon Mac and Xcode | iPhone/iPad installation | Upstream's primary build route; shaders can be compiled on the Mac. |
| You have Windows and want to install on iPhone/iPad | Windows packaging | Experimental shell packaging; Python, LLVM, .NET and a pinned shader translator are required. |
| You want to play on the Mac itself | Native Mac setup | Local app build or a compatible community build; their portability differs. |
| You understand Actions and private prepared inputs | Cloud builds | Community-maintained workflow, version-sensitive inputs and possible runner costs. |
| You use Android | Android progress | Community development and gameplay reports; no stable consumer release verified here. |
Do not mix instructions from different build paths. For example, on-device shader preparation applies to packages made without Apple's shader compiler. It does not apply to every Xcode or community precompiled build.
4. Install, import and back up
Follow the chosen guide through file import, not just the install button. If you encounter No game resources yet, open troubleshooting and compare the actual resource directory with your build's instructions.
Once a character exists, make a copy of the entire documented save folder. Read save files and backups before refreshing a signature, replacing an app or moving progress. Never uninstall the app as a routine signing fix without a backup.
What the evidence labels mean
Upstream documented means the maintainer describes a capability or test. Community reported means a player or fork developer reports it. Unverified means there is no adequate report for that exact combination. This site has reviewed those sources, not reproduced their physical game tests.
We do not promise fixed frame rates, a permanent iOS signature, Battle.net support or an official Android APK. The practical goal is to help you choose the right route and understand its current limits before spending time on installation.
Frequently Asked Questions
Is this an official Blizzard mobile game?
No. D2R Mobile is a community compatibility project, and this website is an independent guide. Neither is an official Blizzard product. The project is offline-only, not a Battle.net client.
Will owning the PC edition supply the files I need?
No. The documented build targets the Nintendo Switch edition at version 1.0.34.0, with the Reign of the Warlock expansion. A PC purchase does not provide the required Switch executable files or a license to download somebody else's dump.
Have you tested the game on these devices?
No. Our first edition checks primary documentation and community reports. Device support and performance claims belong to their cited sources; they are not this site's independent hardware test results.