# Winlator: running Windows x86_64 applications on Android with Wine and Box64 > Winlator packages Wine, Box86/Box64, Mesa and DXVK into an Android app so phones and tablets can launch Windows .exe files. The README documents a two-step install and a set of per-game tuning knobs, not a compatibility guarantee. **brunodev85/winlator** — Android application for running Windows applications with Wine and Box86/Box64 - Repository: https://github.com/brunodev85/winlator - Website: https://winlator.org - Stars: 19,248 · Forks: 1,794 - Language: C - License: LGPL-2.1 - Published: 2026-09-21 · Updated: 2026-09-21 · Language: en - Canonical page: https://hysenlabs.com/projects/brunodev85-winlator ## What Winlator actually solves for Android users Android has no native path for x86_64 Windows binaries. Winlator's answer is a stack: Wine provides the Windows API layer, Box86 and Box64 translate x86 instructions to ARM, Mesa supplies graphics translation (Turnip, Zink, VirGL), and DXVK plus VKD3D map Direct3D calls onto Vulkan. The repository also carries CNC DDraw for older DirectDraw titles, GLIBC patches credited to Termux Pacman, and its own directories for ALSA audio, input controls, installable components and Wine addons. The intended user is someone with an Android phone or tablet who wants to launch a Windows executable, most often a game, without a PC. That is a narrower audience than "run Windows on Android" suggests. The README's tips are all about coaxing individual titles into working: changing the Box64 preset when things are unstable, installing Wine Mono for .NET Framework applications, setting MESA_EXTENSION_MAX_YEAR=2003 for older games, raising ALSA/PulseAudio average latency to fix audio crackling. Those are compatibility chores, and the project presents them as normal operation rather than bugs to be filed. ## How the Wine, Box64 and Mesa layers fit together The architecture visible in the repository is a set of cooperating native components rather than a single emulator. Box86 and Box64 handle instruction translation for 32-bit and 64-bit x86 code respectively. Wine sits above them and presents the Windows environment. Mesa provides the graphics drivers, with Turnip, Zink and VirGL named in the credits, so the GPU path depends on what the device exposes. DXVK and VKD3D translate Direct3D to Vulkan on top of that. Because these are separate layers, a failure can originate anywhere in the chain. A game that crashes may be hitting an unimplemented Wine API, a Box64 translation gap, or a driver limitation. The README's advice reflects this: the Box64 preset lives under Container Settings, Advanced tab, and the README suggests switching to the Stability preset for Unity Engine games, or adding the exec argument -force-gfx-direct in the shortcut settings. Those two fixes target different layers, and the documentation does not tell you how to distinguish which layer is failing. You diagnose by trying presets. ## Installing Winlator from the APK and launching a first executable The README gives a two-step installation. There is no Play Store listing and no build-from-source instruction in the README; the APK is distributed through GitHub Releases, named Winlator_11.2.apk for the current release. Download that file to the device and install it, allowing installation from the source you used if Android blocks it. ```bash # Nothing to run on a desktop. Download the APK on the Android device: # Winlator_11.2.apk (from https://github.com/brunodev85/winlator/releases) ``` The second step happens inside the app. Launch Winlator and wait for its installation process to finish; the README describes this as a wait, and the app is unpacking the Wine and Box64 components it ships with. Do not kill the app while this runs. After that, the practical first use is a shortcut. The README recommends running games through the shortcut on the Winlator home screen, because a shortcut is where you define settings for an individual title. That is the unit of configuration: not a global preference, but a per-application entry you can tune. ```bash # Shortcut settings worth knowing from the README: # -force-gfx-direct (exec argument, suggested for Unity Engine games) # Force Fullscreen (option, for low resolution games) # MESA_EXTENSION_MAX_YEAR=2003 (environment variable, for older games) ``` For a .NET Framework application, the README points to Start Menu -> System Tools -> Installers, where Wine Mono can be installed. If audio crackles, the README says to increase the average latency in the ALSA/PulseAudio configuration, citing 90ms as the value that resolved audio issues in Unreal Gold. ## Where Winlator breaks down, and when it is the wrong tool The README never claims broad compatibility, and the tips list is effectively a catalogue of failure modes. Instability is addressed by changing the Box64 preset. Older games that do not open are addressed by an environment variable that caps the Mesa extension year. Unity games get a preset change or an exec argument. Audio problems get a latency increase. Each of these is a workaround for a class of application, and none of them is described as a complete fix. The wrong-tool cases follow from that. If you need a Windows application to start reliably on first launch without per-title tuning, Winlator is not that. If the application depends on GPU features the device's driver does not expose through Turnip, Zink or VirGL, no container setting will create them. And if you are deploying to a fleet of devices you do not control, the per-shortcut configuration model means the working setup lives on one device rather than in a repository you can ship. The README documents no rollback path for a component installation that goes wrong, and no way to export a known-good container configuration. ## Winlator compared with running Wine on a Linux desktop or handheld The closest alternative in approach is Wine on a Linux system, including handheld gaming distributions. There, Wine runs on the same x86_64 instruction set as the target application, so Box86 and Box64 are unnecessary: the translation layer that Winlator depends on simply is not in the stack. Graphics go through the system's Mesa or proprietary driver directly. The difference matters when you debug. On a Linux desktop you can isolate whether a title fails in Wine or in the driver, and Proton-style compatibility databases give per-title reports. Winlator adds an ARM translation layer between Wine and the hardware, which means one more place for a title to fail, and the project's own advice is to try a different Box64 preset rather than to inspect that layer. The trade is portability: Winlator runs on hardware you already carry, and a Linux handheld does not fit in a pocket. If your goal is maximum compatibility for a specific game and you own a suitable Linux device, the desktop path removes a variable. If your goal is playing on the phone in your hand, Winlator is the option that exists. ## Release cadence, licence and what maintenance costs you The repository is not archived, and the last push was on 2026-09-14. The release history shows v11.0.0 on 2025-09-26, v11.1.0 on 2026-06-12 and v11.2.0 on 2026-08-19, so the project ships major versions at a multi-month interval rather than continuously. That cadence is relevant if you depend on a fix: you may wait months for the next release, and the README does not describe a nightly or beta channel. Winlator itself is licensed LGPL-2.1. The bundled components carry their own terms: Wine, Box86/Box64, Mesa, DXVK, VKD3D and CNC DDraw are separate projects, and the README credits them individually with links. If you redistribute the app or bundle it into a product, the obligations of each upstream licence apply alongside LGPL-2.1, and the GLIBC patches are credited to Termux Pacman rather than to Winlator. This is not legal advice; check the LICENSE file and each upstream project's terms. The upgrade cost is device-side. Releases arrive as APKs, and the README's installation model is install-then-wait, with no documented migration or export step. If you have tuned shortcuts and container settings, the README does not say whether they survive an APK upgrade, so treat that as something to verify on your own device before replacing a working install. ## Conclusion Winlator is worth adopting if you want to run a specific Windows x86_64 title on an Android device and are willing to tune Box64 presets, environment variables and shortcut arguments per game; the README treats that tuning as expected, not exceptional. Do not adopt it if you need a supported, predictable runtime for business software, or if your device's GPU driver path is one you cannot test. Before committing, install the APK from GitHub Releases, wait for the in-app installation to finish, and confirm that one target application launches from a shortcut before you build a library around it. ## FAQ ### Does Winlator really work? It runs Windows x86_64 applications through Wine and Box86/Box64, but the README frames results as per-title: it lists instability fixes, a Wine Mono installer for .NET Framework apps, and an environment variable for older games. Whether a specific application works is something you determine by trying it with different Box64 presets and shortcut settings. ### Is Winlator legal? Winlator is published under LGPL-2.1 and bundles Wine, Box86/Box64, Mesa, DXVK, VKD3D and CNC DDraw, each credited in the README with its own upstream project. The licence of the app does not grant you rights to the Windows applications you run inside it, and the README says nothing about that. ### Can Winlator run all PC games? The README makes no such claim. Its tips describe workarounds for games that fail: changing the Box64 preset for instability, the Stability preset or the -force-gfx-direct exec argument for Unity Engine titles, and MESA_EXTENSION_MAX_YEAR=2003 for some older games. ### What are the risks of using Winlator? The documented friction is instability and per-title tuning rather than data loss: the README suggests Box64 preset changes, environment variables and audio latency adjustments. It does not document a rollback path if the in-app component installation fails, and it does not say whether shortcut and container settings survive an APK upgrade. ### How do I install Winlator on Android? Download the APK, named Winlator_11.2.apk for the current release, from GitHub Releases, install it, then launch the app and wait for the installation process to finish. The README lists those two steps and nothing else. ### How do I use Winlator to open an .exe file? The README recommends running applications through the shortcut on the Winlator home screen, because a shortcut is where you define individual settings for each title, including exec arguments such as -force-gfx-direct and the Force Fullscreen option. For .NET Framework applications it points to Start Menu -> System Tools -> Installers to add Wine Mono. ## Sources - [brunodev85/winlator on GitHub](https://github.com/brunodev85/winlator) - [License: LGPL-2.1](https://github.com/brunodev85/winlator/blob/main/LICENSE) - [Project website](https://winlator.org) - [README](https://github.com/brunodev85/winlator/blob/main/README.md) - [Releases](https://github.com/brunodev85/winlator/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/brunodev85-winlator