# WinNative: a community Windows emulation layer for Android games

> WinNative is a Kotlin Android app that presents a Windows x86_64 emulation environment built by merging Winlator Bionic and Pluvia, with Steam, Epic and GOG library sync, retro console cores and a Wayland display server. It is a GPL-3.0 project shipping beta builds from a GitHub releases page.

**WinNative-Emu/WinNative** — An Android app for playing Windows games from Steam, Epic Games, GOG, and more on your device.

- Repository: https://github.com/WinNative-Emu/WinNative
- Stars: 715 · Forks: 91
- Language: Kotlin
- License: GPL-3.0
- Published: 2026-10-21 · Updated: 2026-10-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/winnative-emu-winnative

## Two upstream projects merged into one community app

WinNative describes itself as an advanced, high-performance Windows x86_64 emulation environment for Android, and the interesting part of that sentence is the word unifying. The README says it unifies the best of Winlator Bionic and Pluvia, delivering the full Winlator experience while making it easy to connect Steam, Epic and GOG libraries and running classic console games alongside them. That makes this a merger project rather than a new emulator: the value proposition is that one maintainer group assembled two existing lines of work into a single app with one set of settings, one library sync path and one update channel. The audience is Android players with a desktop game library who want the Winlator style of environment, plus retro console players, since the same binary carries console cores from NES through PlayStation 2 according to the linked documentation. The repository credits a long list of upstream authors, which is the clearest sign of what kind of project this is.

## Four package names, one app, and why the name matters

The release artefacts are not four different builds. The README states that all four variants are the same app with a different package name, and the table explains what each one is for. Vanilla uses the standard package name, meant for side-loading alongside other forks. Ludashi forces maximum GPU and CPU clocks on some devices and is described as a performance-mode trigger. Antutu forces maximum GPU clocks on most devices, and the README names that purpose bluntly as benchmark spoof. Pubg uses a PUBG package name, which unlocks some Game Booster advanced features. This tells you something about the project that a features list would hide. The app is designed to be side-loaded next to other forks, and it includes package-name workarounds for device-side tools, including one that exists to change what a benchmark reports. Anyone evaluating it should know that the standard release and the benchmark-facing release are the same code with a different identifier.

## Installing: the APK, the ImageFS, then the library

The documented install path is short. Grab the latest APK from the releases page, launch the app, allow the ImageFS to install, then add games manually or sync your library. There is no command line installation, and the build from source instructions live in a separate document, docs/BUILDING.md, which the README links from its table rather than reproducing. The ImageFS step is the one that needs a moment of attention. A file system image has to be laid down on the device before any Windows title can run, and the app asks permission to do it, so a first launch that appears to stall is expected behaviour rather than a failure. After that, games can be added by hand, one at a time, which suits someone with a handful of titles, or the library can be synced, which suits someone with a large account and wants the whole collection visible at once.

## Beyond Windows: console cores, frame generation and Wayland

Three capability areas are documented in their own files, and they are the reason this is more than a Winlator clone. The retro console support, described as running classic console games alongside the PC titles, is documented from NES through PlayStation 2, which is a considerable range and points at bundled emulator cores rather than a single system. Frame generation is covered separately, with LSFG and OpenFlow named as the two approaches; the repository credits the lsfg-vk project and the open-source OpenFlow engine, along with the Vulkan LSFG port the project derives from. The Wayland document describes winewayland sessions running on an embedded compositor, which is a different display model from the usual approach. The practical effect for a player is that one app can host a console library, a Windows library, and a modern presentation layer, and the fact that these are separate documents rather than README bullets suggests they are the areas most likely to need per-device tuning.

## A repository of vendored cores rather than a single app module

The top-level layout explains how the project is assembled. Alongside the app directory and the Gradle build files there is a vendor directory, a cores directory, and directories named after specific components: armsx2 for the ARM translation layer, dolphin for the GameCube and Wii emulator, framegen for the frame generation work, audio_plugin for the DirectAudio and Steam Controller support, android_sysvshm for shared memory handling, and a tools directory. There is also a .gitmodules file, so at least part of the tree is pulled in as submodules rather than vendored by hand. The credit list in the README matches that structure, naming the ARMSX2, PCSX2 and Dolphin teams, the libretro core authors, Goldberg Steam Emulator work, DXVK for the dxbc translator, Mesa3D, SDL, OpenCV and the DIS algorithm. A reader who wants to know where a specific file came from should look at CREDITS.md, which the README says carries the full acknowledgements including exactly which files came from which upstream project.

## Licence obligations come with the borrowed components

WinNative is released under the GNU General Public License v3.0, with the LICENSE file at the root of the repository. The more interesting document is EMULATOR_CREDITS.md, which the README describes as carrying the per-component licence table and the GPL corresponding-source statement. That distinction is the practical one. A GPL project that embeds components with their own licences, some of them permissive and some copyleft, has to state which is which, and the table is what tells a distributor what they owe. The README credits run from brunodev85 for Winlator, Pipetto-crypto for Winlator Bionic, the Pluvia and GameNative community, Mr. Goldberg and Detanup01 for the Goldberg Steam Emulator, Filippo Scognamiglio for LibretroDroid, the libretro core authors, PancakeTAS, Camille LaVey of the Eden Emulator Project, qwertypower of DEVAR Entertainment, The412Banner for DirectAudio and Steam Controller support, and the SDL contributors. The README is careful that its own list is only a summary and that the attribution itself lives in the two files.

## Beta builds, active commits and a community contribution model

The release tags say beta, all of them. v0.7.0-beta on 2026-09-26, v0.7.1-beta on 2026-09-28 and v0.8.0-beta on 2026-10-12, with the last push to the repository on the same date as the newest tag. So the project is being worked on at a steady pace, and the version numbers are below 1.0 with a beta suffix on every artefact. That combination matters for anyone depending on it: the app is not versioned in a way that promises stability, and the four package-name variants mean an update is effectively a fresh side-load rather than an in-place upgrade, since a new package name installs alongside the old one. The contribution guidance in the README asks for pull requests covering bug fixes, driver updates and UI improvements, asks contributors to match the existing code style, and asks that any AI-assisted code be thoroughly reviewed and tested before submission. Community activity is centred on a Discord server linked from the header.

## Conclusion

WinNative fits an Android player who owns a Steam, Epic or GOG library and wants one emulator app that also carries retro console cores, with the option of forcing maximum clocks on a device that needs it. It does not fit someone who wants a stable, non-beta release with a predictable update path, and it does not fit a user who is unwilling to read the credits and per-component licence table. Before installing, check which variant matches your device, read EMULATOR_CREDITS.md for the per-component terms, and expect to reinstall on every beta, since the package name and behaviour change between builds.

## FAQ

### What is WinNative and how is it different from Winlator?

WinNative is an Android app that unifies Winlator Bionic and Pluvia into a single Windows x86_64 emulation environment, and it adds Steam, Epic and GOG library sync plus classic console support. The repository is written in Kotlin and released under the GPL v3.

### How do I install WinNative?

Download the latest APK from the GitHub releases page, launch the app, allow the ImageFS to install, then add games manually or sync your library. Build-from-source instructions are in docs/BUILDING.md.

### What is the difference between the Vanilla, Ludashi, Antutu and Pubg variants?

They are the same app with different package names. Vanilla uses the standard package name for side-loading with other forks, Ludashi forces maximum GPU and CPU clocks on some devices, Antutu forces maximum GPU clocks for benchmark spoofing, and Pubg uses a PUBG package name that unlocks some Game Booster advanced features.

### Does WinNative support retro consoles and frame generation?

Yes. The documentation lists retro console support from NES through PlayStation 2, frame generation through LSFG and OpenFlow, and Wayland display server support with winewayland sessions on the embedded compositor.

## Sources

- [Issues](https://github.com/WinNative-Emu/WinNative/issues)
- [License: GPL-3.0](https://github.com/WinNative-Emu/WinNative/blob/main/LICENSE)
- [README](https://github.com/WinNative-Emu/WinNative/blob/main/README.md)
- [Releases](https://github.com/WinNative-Emu/WinNative/releases)
- [WinNative-Emu/WinNative on GitHub](https://github.com/WinNative-Emu/WinNative)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/winnative-emu-winnative