Want to run Windows games and apps on your phone? Winlator is a free, open-source app that lets you run Windows programs on Android by combining Wine with Box86 and Box64 translation inside isolated containers. To install it, download the official APK (v11.2, the current release as of October 2026) from the developer’s GitHub releases page, allow “Install unknown apps,” install the APK, open Winlator once to finish its first-launch setup, then create a container with the Turnip graphics driver and DXVK wrapper at 1280×720. The whole process takes about 15 minutes on a compatible phone. Here’s the complete step-by-step guide.
What Is Winlator?
Winlator is a free Android app by developer brunodev85 (also known as BrunoSX) that creates a Windows-like environment on your phone or tablet. Instead of being a traditional console emulator, it runs actual Windows x86 and x64 programs: you install .exe files the same way you would on a PC.
Under the hood, Winlator uses Wine to translate Windows system calls, Box86 and Box64 to translate x86 processor instructions to your phone’s ARM processor, and graphics wrappers such as DXVK to convert DirectX graphics calls to Vulkan. Everything lives inside containers, which work like separate virtual PCs. You can create one container for games, another for a specific app, and each keeps its own settings and installed files without interfering with the others.
Winlator is not available on the Google Play Store, so you must sideload the APK from the developer’s official GitHub releases page. According to community reports, the app is fully free with no subscription or per-game charges. Your only costs are the device itself and the games you already own.
What You Need Before Installing
Winlator works on a wide range of Android phones, but performance depends heavily on your hardware. Check the requirements below before you start.
| Requirement | Details |
|---|---|
| Chipset | A Snapdragon processor with an Adreno GPU gives the best results, because the Turnip graphics driver is built specifically for Adreno. Phones with MediaTek (Mali) or Exynos GPUs can run lighter games and 2D titles using the VirGL or experimental Vortek drivers, but 3D PC games will struggle. Pixel phones use Mali GPUs, so they fall in this second group. |
| RAM | 8 GB of RAM is the practical minimum. 12 GB or more is noticeably better for heavier titles, since the app shares your phone’s memory with the emulated system. |
| Android version | The APK metadata lists Android 8.0 and newer as the minimum. Community guides, however, recommend Android 9 or newer, and Android 13+ feels more comfortable in practice. If you are still on an older build, this is a good excuse to check whether your phone can be updated. |
| Storage | The APK itself is around 150 MB, and the first-launch setup downloads additional files. Your games and containers will need gigabytes of their own, so have at least 5 to 10 GB free. |
| Chipset support (64-bit) | Your phone must be a 64-bit device (arm64), which virtually every Android phone sold in the United States since 2015 is. |
If you want to know exactly which chip your phone has, open Settings, go to About Phone, and look at the processor field. Snapdragon 8-series chips (such as the 8 Gen 2 or 8 Gen 3) with an Adreno GPU are the sweet spot. If your phone feels sluggish in everyday use, it will also benefit from some general cleanup. See our guide on how to speed up your Android phone before running anything demanding.
How to Install Winlator on Android: 14-Step Guide
Step 1: Check your phone’s chipset and Android version
Go to Settings > About Phone and note your processor and Android version. This matters because the graphics driver you pick in Step 9 depends on your GPU: Turnip for Snapdragon/Adreno, VirGL for everything else (MediaTek, Exynos, Pixel), or Vortek as an experimental option for Mali devices. Writing down your chip now saves guesswork later.
Step 2: Download the official APK from GitHub
Open your browser and go to the official Winlator GitHub repository (brunodev85/winlator) and open the Releases page. Download the APK from the latest release, which is v11.2 as of October 2026. This is the only source you should trust for the download.
Important safety note: many third-party APK sites host “modded” or “full” versions of Winlator. These repackaged APKs are a well-known malware vector and can bundle adware or spyware. Since Winlator itself is free, any site selling a “premium” or “mod” version is a red flag. If you ever compare download sources, our explainer on APKMirror vs APKPure vs Uptodown covers how to tell trustworthy APK mirrors from risky ones.
Step 3: Allow “Install unknown apps”
When you tap the downloaded APK, Android may block the install and show a message like “Install blocked.” This is normal: Android blocks sideloading by default. Tap Settings on that prompt and enable Allow from this source (Chrome, or whichever browser you downloaded the APK with). On older Android versions this is a global toggle called “Unknown sources.”
Step 4: Install the APK
Tap the APK file again and choose Install. The install takes under a minute. Tap Open when it finishes. Do not delete the APK file yet in case you need to reinstall.
Step 5: Let the first-launch setup finish
The first time you open Winlator, it extracts and installs its internal files (Wine, Box86/Box64, the root filesystem). Keep the app open and the screen on until this process completes. Interrupting it can cause a broken install, in which case you would need to clear the app’s data and start over. This one-time setup can take a few minutes on slower phones.
Step 6: Create your first container
After setup, you will see the Winlator home screen with a + button. Tap it. A container is an isolated Windows-like environment with its own settings, installed programs, and files. Think of it as a separate virtual PC. You can create multiple containers later (for example, one per game), but start with just one.
Step 7: Name your container
At the top of the container settings screen, give your container a name like “Games” or “Main.” This is just a label so you can find it later.
Step 8: Set the screen size (resolution)
Choose a Screen Size for the container. This is one of the biggest performance levers. The widely recommended starting points are:
- 1280×720 for most phones and most games.
- 960×544 if your phone is mid-range or a game runs slowly.
- 800×600 for maximum performance on low-end devices.
Do not use your phone’s full native resolution. Rendering at 1080p or higher forces the translation layer to do far more work, and frame rates usually collapse. You can always raise the resolution later once you know a game runs well.
Step 9: Choose the graphics driver
Under Graphics Driver, pick the driver that matches your GPU:
- Snapdragon / Adreno GPU: choose Turnip. This is the community-recommended driver for Adreno and the reason Snapdragon phones perform best.
- MediaTek / Mali, Exynos, or Pixel: choose VirGL. Some builds also offer Vortek, an experimental driver aimed at Mali devices that has seen ongoing improvements in recent releases.
Some releases also list a Turnip Zink option for Adreno. If Turnip misbehaves with a specific game, trying Zink is a common troubleshooting step reported by the community.
Step 10: Choose the DX wrapper
The DX Wrapper translates DirectX graphics calls. Pick based on your game:
| DX Wrapper | Best for |
|---|---|
| DXVK | DirectX 9, 10, and 11 games. This is the best default for most modern-ish titles. |
| WineD3D | Broader compatibility. Try this if DXVK gives you a black screen or graphical glitches. |
| VKD3D | DirectX 12 games. Note that D3D12 support is still experimental and many D3D12 titles will not run acceptably on phones. |
| CNC DDraw / D7VK | Very old 2D and early-3D games that use legacy DirectDraw. |
If you are unsure, start with DXVK and switch to WineD3D only if a game has rendering problems.
Step 11: Set video memory and audio driver
Under Video Memory Size, allocate a sensible amount based on your phone’s RAM: 2048 MB on 6 GB phones, 4096 MB on 8 GB phones, and 6144 MB on 12 GB phones. Do not allocate more than about half your total RAM, or Android itself will run out of memory and start killing the app. For the audio driver, PulseAudio is the common recommendation for in-game sound; ALSA is also available.
Enabling Show FPS is useful while you tune things, since it puts a live frame counter on screen so you can see whether each setting change helps.
Step 12: Set the Box64 preset (Advanced tab)
Swipe to the Advanced tab and set the Box64 Preset to Performance. This preset adjusts how Box64 translates the game’s code and is the standard recommendation for the best frame rates. You can also experiment with processor affinity here, but the default (all cores) is fine for most games.
Step 13: Save and launch the container
Tap the checkmark icon to save the container. You will see it listed on the home screen. Tap its play button to launch it. A Windows-style desktop should appear after a short startup. If it launches, your core install is working.
Step 14: Install your first game or app
Copy your game’s installer (or the installed game folder) from your PC into your phone’s Download folder, which appears as the D: drive inside the container. Launch the container, open the D: drive, double-tap the installer (for example, setup.exe), and install the game just like on a PC. DRM-free copies you own, such as GOG offline installers, are the safest and most reliable source: they install without online activation servers, which cannot be reached reliably through the translation layer.
After installing, find the game’s executable, and use the container’s Start Menu to create a shortcut so you can launch it directly next time. Some community guides also install the Steam client from a Start Menu option added in recent releases, but Steam compatibility varies and many Steam games with anti-cheat will not run (more on that below).
Best Winlator Settings for Performance
Once the basic install works, use these community-reported baselines and adjust per game:
| Setting | Recommended value | Why |
|---|---|---|
| Screen size | 1280×720 (or 960×544) | Lower internal resolution is the single biggest FPS gain on phones. |
| Graphics driver | Turnip (Snapdragon) / VirGL (others) | Turnip is purpose-built for Adreno GPUs. |
| DX wrapper | DXVK | Best DirectX 9-11 translation for most games. |
| Box64 preset | Performance | Maximizes translation speed in the Advanced tab. |
| Video memory | 2048-6144 MB (based on RAM) | More helps textures; too much starves Android. |
| Audio driver | PulseAudio | Most reliable audio output in community reports. |
| Show FPS | On while tuning | Lets you measure whether changes actually help. |
A few practical habits also help: close background apps before launching a heavy game, keep your phone cool (thermal throttling is the main reason frame rates drop after 10-15 minutes), and plug in a mouse and keyboard or use Winlator’s built-in input controls for games that need them. Many players also find that one container per demanding game works better than cramming everything into a single container with compromised settings.
Game Compatibility Notes
Winlator runs a surprising range of Windows games, but it is not a magic “every PC game on phone” box. Community reports generally point to these patterns:
- Best candidates: older single-player titles from the DirectX 9 and DirectX 11 eras (roughly 2005-2015), indie games with modest requirements, and classic strategy or RPG titles. These are the games where you are most likely to get smooth, playable frame rates.
- Mixed results: DirectX 12 games. VKD3D exists, but D3D12 support is experimental and many titles either fail to start or run too slowly to enjoy on current phones.
- Generally will not work: online multiplayer games with kernel-level or aggressive anti-cheat systems (such as Valorant-style or competitive-shooter anti-cheat). The anti-cheat components do not function under Wine/Box64 translation, and trying to force them is not worth the risk to your game accounts.
- Apps too: Winlator is not only for games. Lightweight Windows utilities and older productivity software often run fine, which is handy if you need a desktop-only tool on the go.
Compatibility can vary between Winlator versions, so a game that struggles on one release sometimes works better after updating to the latest APK from GitHub.
Troubleshooting Common Errors
| Problem | Likely cause | Fix |
|---|---|---|
| “Install blocked” when tapping the APK | Sideloading is disabled | Enable “Allow from this source” for your browser in Android settings, then tap the APK again. |
| App crashes during first-launch setup | Interrupted extraction or low storage | Free up several GB of space, clear Winlator’s app data, and reopen it to restart setup. |
| Black screen when launching a game | Wrong DX wrapper or graphics driver | Switch the DX wrapper from DXVK to WineD3D, or try a different graphics driver for your GPU. |
| Very low frame rates | Resolution too high or wrong preset | Drop the container resolution to 960×544 or 800×600, set Box64 preset to Performance, and close background apps. |
| No sound or crackling audio | Audio driver issue | Switch between PulseAudio and ALSA. Community reports note that raising audio latency in the driver settings can reduce crackling. |
| Game installer will not start | Online activation or anti-cheat dependency | Use DRM-free offline installers where possible. Games that require online activation servers often cannot complete installation. |
| Container fails to start on Android 14+ | Version-specific bug | Update to the latest Winlator release. Recent versions include fixes for newer Android builds, but if problems persist, try a fresh container. |
Safety and Legal Notes
Winlator itself is free, open-source software, so installing and using the app is legal. What matters is what you run inside it: only install games you own. DRM-free installers from stores like GOG, or discs and installers you already purchased, are the safe and legal route. Downloading pirated game files is illegal regardless of the emulator you use, and sketchy “game pack” downloads bundled with Winlator APKs are exactly where malware hides.
Two more cautions. First, never disable Android security features beyond the standard “install unknown apps” prompt for your browser, and re-disable that permission when you are done if you like to keep a tight ship. Second, if you download large files over public Wi-Fi, a reputable VPN adds a layer of privacy to the connection. See our roundup of the best VPNs for Android in 2026 for current picks.
Frequently Asked Questions
What is Winlator used for?
Winlator lets you run Windows x86 and x64 programs on Android, most commonly PC games. It creates isolated containers that act like separate virtual PCs, translating Windows system calls and processor instructions so software written for Intel or AMD chips can run on your phone’s ARM chip.
Is Winlator free?
Yes. According to the developer’s GitHub page and community reports, Winlator is completely free to download and use, with no subscription, no paid tiers, and no per-game fees. Be suspicious of any site charging for a “premium” or “mod” version.
Is Winlator legal?
The app itself is legal, open-source software. The legality depends on the games you run: playing copies you own is fine, while downloading pirated games is not. Games with anti-cheat systems generally will not run anyway.
What Android version do I need for Winlator?
The APK metadata lists Android 8.0 as the minimum, but community guides recommend Android 9 or newer, with Android 13+ being the most comfortable. Newer Android versions also benefit from recent Winlator fixes for container startup on Android 14 and above.
Does Winlator work on MediaTek or Exynos phones?
It runs, but with limits. Snapdragon phones with Adreno GPUs perform best thanks to the Turnip driver. On MediaTek (Mali) or Exynos phones, use the VirGL driver (or the experimental Vortek driver for Mali) and stick to lighter 2D games or older titles. Demanding 3D games will likely be too slow.
Can I play online multiplayer games in Winlator?
Usually not. Games with kernel-level or aggressive anti-cheat do not work under Wine/Box64 translation, so competitive online shooters are effectively off the table. Single-player and co-op games without anti-cheat are where Winlator shines.
Do I need to root my phone to use Winlator?
No. Winlator works on unrooted phones. You only need to allow installing apps from your browser once (the standard “install unknown apps” prompt), which is a normal Android feature, not rooting.
Final Thoughts
Installing Winlator on Android is straightforward: download the official APK from GitHub, allow sideloading, let the first-launch setup finish, and create a container with Turnip and DXVK at 1280×720. From there, performance is mostly about matching settings to your hardware, with Snapdragon phones having the clear advantage. Keep your games to DRM-free copies you own, tune one setting at a time with the FPS counter on, and you will have a pocket PC gaming setup in about 15 minutes. If anything behaves oddly, work through the troubleshooting table above before reinstalling, since most problems trace back to the graphics driver, the DX wrapper, or the resolution.
Sources
- Winlator official releases (brunodev85/winlator on GitHub) — checked October 12, 2026; latest release listed is v11.2.
- How to Run Winlator PC Games on Android (2026) — container and driver recommendations referenced for the setup steps.
- Winlator vs GameNative vs GameHub 2026 — version and anti-cheat context as of October 2026.
What do you think?
Share your experience or ask a question. A useful conversation starts with you.
Join the discussion