Winlator 11.2 Setup: Run Windows Games on Android [2026]

What Winlator Actually Is

Winlator is a free, open-source Android application that bundles Wine (the Windows compatibility layer originally built for Linux) with Box64 and Box86, which translate x86/x86_64 CPU instructions into ARM instructions on the fly. On top of that sits a graphics translation stack: DXVK converts DirectX 9 through 11 calls into Vulkan, VKD3D does the same for DirectX 12, and a driver layer turns those Vulkan calls into something the phone’s GPU can actually execute.

The Translation Chain, Step by Step

It helps to picture the full path a single frame takes before it ever reaches the screen. The Windows game issues a DirectX draw call, exactly as it would on a real PC. Wine intercepts that call and routes it through DXVK or VKD3D, which rewrites it as a Vulkan command. Meanwhile, every x86_64 CPU instruction the game executes passes through Box64, which recompiles it into ARM64 instructions the phone’s processor can run natively. Finally, the Vulkan command reaches the GPU driver — Turnip, part of the open-source Mesa project, on Qualcomm Adreno hardware — which hands it off to the actual silicon. Four translation layers, all happening in real time, dozens of times per second. That is also why performance is so sensitive to which chip is doing the work: every layer adds overhead, and a faster CPU and GPU simply has more room to absorb that overhead before frame rate suffers.

None of that is emulation in the traditional sense. Winlator is not pretending to be a Windows PC the way a console emulator pretends to be a PlayStation. It is running real Windows binaries through a chain of real-time translators, which is why performance depends so heavily on which chip is doing the translating. A Snapdragon 8 Elite-class phone with 16GB of RAM has enough headroom to run lighter DirectX 11 titles at a stable 30 to 60 FPS. A mid-range chip from two generations back will struggle with anything beyond simple 2D titles.

Prerequisites: What You Need Before You Start

• An Android device running Android 8.0 or newer, with a 64-bit ARM processor (ARMv8-A or later). Winlator will not install on 32-bit-only devices.
• A Vulkan 1.1-capable GPU. Qualcomm Snapdragon 8 Gen 1 through 8 Elite (Adreno GPUs with Turnip support) give the smoothest results; MediaTek Dimensity and other Vulkan 1.1 chips work through the Vortek fallback driver with reduced performance.
• At least 8GB of RAM for light 2D and older 3D titles, 12GB for mid-weight DirectX 11 games, and 16GB if you intend to push demanding titles like Grand Theft Auto V.
• 20-40GB of free internal storage per container, more if you install multiple games in one Windows environment.
• Winlator 11.2.0 APK, downloaded only from the official GitHub Releases page. Third-party APK mirror sites are a common source of outdated or modified builds.
• Legally owned copies of the Windows game files you plan to install. Winlator does not provide games, and it does not grant a Windows license.
• A USB-OTG adapter or Bluetooth controller if you plan to play with anything other than touch controls (strongly recommended for anything beyond puzzle games).
• A file manager app capable of extracting ZIP/ISO archives, since most PC game distributions arrive compressed.
• About an hour and a half of uninterrupted setup time for your first container, including driver testing and at least one full troubleshooting pass.

A note on terminology before the steps: a “container” in Winlator is a self-contained virtual Windows environment, complete with its own C: drive, registry, Wine version, and driver configuration. You can run multiple containers side by side, each tuned for a different type of game, without them interfering with each other. Think of each container as a separate, disposable Windows installation that lives entirely inside the Winlator app.