Winlator icon

Winlator

by brunodev85 · LGPL-2.1 · open source

Free · Android 8.0+ · PC Emulators

Runs Windows (x86-64) games and programs on an Android phone, using Wine to handle Windows and Box64 to translate the x86 code.

Needs:64-bit ARM phone · Android 8+ · no root

No known trackers in the code File matches GitHub’s published hashOfficial GitHub release

2113 Apps is independent, not affiliated with or endorsed by brunodev85. Official sources: winlator.org · source code on GitHub.

Download APK · 157.5 MB v11.2 · checked
Version
11.2
Size
157.5 MB
Requires
Android 8.0+
Updated
2026-08-19

Introduction

Winlator lets an Android phone run programs built for Windows on x86-64 PCs, most often games. It isn’t a virtual machine running a copy of Windows. It combines two projects:

  • Wine, which answers a Windows program’s calls to Windows with Linux equivalents, so no Windows licence is involved.
  • Box64, which translates x86 processor instructions into ARM ones that a phone’s CPU can run. The README still credits Box86 as well, but the version 11.2 file contains only Box64 0.4.4; its Wine is laid out for Wine’s WoW64 mode, so 32-bit Windows programs most likely run through that.

Graphics go through DXVK and VKD3D, which turn Direct3D into Vulkan, or WineD3D, which turns it into OpenGL. Underneath sit the graphics drivers: Mesa’s Turnip for Qualcomm Adreno GPUs, and two libraries by Winlator’s own developer, Vortek, a compatibility layer over your phone’s own Vulkan driver, and Gladio, OpenGL through the phone’s GLES driver. Mesa’s Zink and VirGL are there as alternatives. Most of these are other people’s open-source projects, credited in the README. Winlator’s work is packaging them into one app with a desktop, containers and per-game settings.

Before you install

  • A 64-bit ARM phone. This build contains native code for arm64-v8a only, so 32-bit-only phones can’t run it.
  • Your own games. Winlator comes with no games. You copy the game’s Windows files onto the phone and open them from Winlator’s file manager or desktop.
  • Expect it to depend on your GPU. Turnip is Mesa’s open-source Vulkan driver for Qualcomm Adreno GPUs (Snapdragon phones), and Winlator picks it for Adreno 6xx, 7xx and 8xx. Phones with Mali, Xclipse or other GPUs get Vortek, which the release notes have been adapting to Mali and Xclipse since version 10. Which games run, and how fast, varies by phone and by game. We haven’t tested any.

Getting started

  1. Install the APK and open it. On first launch it unpacks its own system files. The README says to wait for that to finish.
  2. Create a container: a separate Wine environment with its own settings.
  3. Copy your game onto the phone and run its .exe from the Winlator desktop. For games you play often, make a shortcut. Shortcuts keep their own settings, so each game can be tuned separately.

Winlator settings explained

Winlator has two levels of settings: the container, a Wine environment with its own C: drive, and the shortcut you make for each game. From the source of version 11.2, this is what a new container gets.

Container settings

Setting Choices New container
Screen Size 640x360 up to 1920x1080, or custom (even numbers only) 1280x720, the size of the Windows desktop the game sees
Graphics Driver, Vulkan Turnip 26.2.0, Vortek 2.1 Turnip on Adreno 6xx–8xx, Vortek on other GPUs
Graphics Driver, OpenGL Zink, VirGL, Gladio Gladio
DX Wrapper, Direct3D DXVK (2.4.1 or 1.10.3), WineD3D DXVK: 2.4.1 with Turnip, or with Vortek when the phone reports Vulkan 1.3; otherwise 1.10.3
DX Wrapper, DirectX 12 VKD3D 2.14.1 Always installed, feature level 12.1
DirectDraw (in the DXVK or WineD3D settings) WineD3D, CNC DDraw 6.6, D7VK WineD3D
Audio Driver ALSA, PulseAudio ALSA, 16 ms average latency
HUD Mode Disabled, Simple (FPS), Full Disabled
Box64 Preset Stability, Conservative, Intermediate, Performance, or your own Performance
Startup Selection Normal, Essential, Aggressive Essential: 15 Wine services off; Aggressive also turns off the Windows Installer and font cache services
Windows Version Windows 2000 to Windows 11 Windows 10
Processor Affinity Which CPU cores Windows programs may use, separately for 32-bit programs All cores
Drives Up to eight extra letters D: is the phone’s Downloads folder, E: Winlator’s own storage; C:, Z: and the X: virtual CD drive are always there

Wine itself is fixed at Wine 10.10: the option to install other Wine builds is hidden in this release, and the container’s Wine picker only appears when more than one is installed. More versions of Box64, Turnip, DXVK, VKD3D and WineD3D can be downloaded in the app; the list is read from the project’s GitHub repository.

Box64 presets

The presets set Box64’s speed-versus-safety switches. From Stability to Performance, they relax memory ordering and flag handling and translate bigger blocks of code at once. Some of the values each one sets:

Setting Stability Conservative Intermediate Performance
Strong memory model (STRONGMEM) 2 1 0 0
Safe flags (SAFEFLAGS) 2 2 2 1
Block size (BIGBLOCK) 0 1 2 3
Double-precision x87 (X87DOUBLE) 1 1 1 0

The default for new containers changed in the September 2026 build of 11.2, from Intermediate to Performance; existing containers keep their own choice. Any BOX64_… variable you type in Environment Variables overrides the preset.

Video memory

The only option called Video Memory Size is in the WineD3D settings, defaulting to 2 GB; there the renderer defaults to OpenGL and the game is told it runs on an “NVIDIA GeForce GTX 480”. DXVK, Turnip and Vortek each have their own Max Device Memory, set to no limit by default. DXVK can also cap the frame rate at 30, 60 or 120 and report a PC graphics card of your choice to the game.

Shortcut settings

A shortcut can override the screen size, graphics driver, DX wrapper, audio, Windows components, environment variables and Box64 preset, and adds a few things of its own:

  • Exec Arguments, with a quick menu of common engine switches such as -force-gfx-direct, -force-d3d11 and -force-dx9.
  • Force Fullscreen, off by default, which stretches a window smaller than the container’s screen.
  • Controls Profile, the on-screen controls to show when the game starts.
  • DirectInput Mapper Type, XInput by default or Standard, for how a controller appears to older games.

A shortcut only stores the values you changed, so later changes to the container still apply to everything else. HUD mode, startup selection, Windows version, processor affinity and drives are container-only.

Controls

Winlator comes with four on-screen control layouts, RTS, Template, Virtual Gamepad and FPS, and can download 53 game-specific layouts from the project’s GitHub repository, such as GTA 5, Skyrim and Fallout 3. Without a layout, the screen works as a touchpad: tap to click, tap with a second finger for a right click, two fingers to scroll, and a four-finger tap opens the menu. Up to four controllers work at once; vibration is off by default, and a global setting makes controllers appear to Windows as an Xbox 360 or Xbox One pad.

Tips from the developer

The README lists fixes for common problems. In short:

  • Crashes or instability: change the Box64 preset in the container’s Advanced settings. For Unity games, the Stability preset or the launch argument -force-gfx-direct is suggested.
  • .NET programs: install Wine Mono from Start Menu → System Tools → Installers.
  • Some older games won’t start: add the environment variable MESA_EXTENSION_MAX_YEAR=2003.
  • Low-resolution games look wrong: turn on Force Fullscreen in the shortcut’s settings.
  • Crackling audio: raise the average latency in the ALSA/PulseAudio settings.

About this file

This is the original Winlator by brunodev85, taken from the project’s GitHub releases. The developer signs releases with an Android debug certificate, as shown under More Information. It is recorded here so a future release signed differently won’t go up without a check.

Many forks circulate under the Winlator name. We checked one that is signed with Android’s public test key and uses another app’s package name. We don’t host builds like that.

What’s inside the APK

Trackers

None found

No code matching the tracker signatures we check, including Exodus Privacy’s list and our published supplements.

Native code

1 CPU type

Needs a 64-bit ARM phone; 32-bit-only devices are not supported.

Android versions

Android 8.0 and up

Built for Android 9 (target API 28).

Permissions

11

3 of them need your approval first.

CPU types in this build: arm64-v8a (64-bit ARM, almost every phone since 2017).

Asks you first (3)

Android shows a prompt before the app can use these.

  • Show notifications (Android 13+) · POST_NOTIFICATIONS
  • Read shared storage (Android 12 and older) · READ_EXTERNAL_STORAGE
  • Write shared storage (Android 10 and older) · WRITE_EXTERNAL_STORAGE
Granted at install (8)

Low-risk permissions Android grants automatically, plus any we have not classified.

  • ACCESS_NETWORK_STATE
  • ACCESS_WIFI_STATE
  • FOREGROUND_SERVICE
  • FOREGROUND_SERVICE_MEDIA_PLAYBACK
  • INTERNET
  • MODIFY_AUDIO_SETTINGS
  • VIBRATE
  • WAKE_LOCK

More Information

Package name
com.winlator
Version
11.2 (build 33)
File size
157.5 MB (157,549,075 bytes)
Requires
Android 8.0 or later
Category
PC Emulators
License
LGPL-2.1
Developer
brunodev85
Released
Aug 19, 2026
Signer SHA-256
e576bf5035e4bba4efb2c5099f9d74a95cc3abe8e3b6b0c72219cc07eac8c8fb
Certificate
Android debug certificate. The developer signs releases with the debug key of their own build machine. It isn’t a public key, but it isn’t a dedicated release key either: if the developer changes machines, the next release can carry a different signer and won’t install over this one.
File SHA-256
ea5c81bf0e5b90a6b9ccb8007121ab6738c8646a5a60b341ce0ac2b33f1d100a
Checked
, against the v11.2.0 release on GitHub · how we check · verify it yourself

Common questions

Is this APK the official Winlator release?

Yes. It is the file from the project’s v11.2.0 release on GitHub, byte for byte, and it matches the SHA-256 checksum GitHub publishes for it. It is signed with the certificate we recorded when we first checked Winlator (SHA-256 e576bf5035e4bba4efb2c5099f9d74a95cc3abe8e3b6b0c72219cc07eac8c8fb); a release signed with a different key would not be published here. That certificate is an Android debug certificate, so a release built on another machine could carry a different signer.

What Android version does Winlator need?

Android 8.0 or later (API level 26). Version 11.2 is built for Android 9 (target API 28). Needs a 64-bit ARM phone; 32-bit-only devices are not supported.

Can Winlator access the internet?

Yes. The APK requests Android’s internet permission. In total it declares 11 permissions, and 3 of them need your approval first.

Does Winlator contain trackers?

No known trackers: our scan of version 11.2 found no code matching the tracker signatures it checks. Those include Exodus Privacy’s list and the published local supplements described on How We Check; the scan doesn’t show what data the app itself sends.

Is Winlator open source?

Yes. Winlator is released under the LGPL-2.1 licence, and its source code is published at https://github.com/brunodev85/winlator.

Which graphics driver does Winlator use on my phone?

A new container picks one by itself. If the GPU name matches Adreno 6xx, 7xx or 8xx (Snapdragon phones), it uses Turnip; on every other GPU, Mali included, it uses Vortek. For OpenGL, new containers use Gladio either way. You can change both in the container settings.

Where is the video memory setting?

In 11.2 the only “Video Memory Size” option is inside the WineD3D settings, the gear next to DX Wrapper when WineD3D is chosen, and it defaults to 2 GB. DXVK, Turnip and Vortek each have a separate “Max Device Memory”, which defaults to no limit.

Does changing a shortcut’s settings change the container?

No. A shortcut only saves the values you set differently from its container, and follows the container for everything else. Environment variables in a shortcut are added on top of the container’s; where both set the same name, the shortcut’s value wins.

Recent releases

Version Released Size
v11.2.0 · this download Aug 19, 2026 157.5 MB
v11.1.0 Jun 12, 2026 156.9 MB
v11.0.0 Sep 26, 2025 153.3 MB
v10.1.0 Jul 8, 2025 147.8 MB
v10.0.0 Feb 28, 2025 147.7 MB

Recent releases on the project’s GitHub. We host and check only the newest one. Full changelog.

Alternatives and related apps

  • Vita3K Console Emulators·29.6 MB·v0.2.1 If the games you want are PlayStation Vita titles rather than PC ones.
    Download