Running full Windows PC games on an Android phone or handheld used to be a party trick. In 2026 it is a genuine alternative to buying a Steam Deck. Three apps dominate the conversation: Winlator, the open-source Windows container that started the movement; GameNative, the slick newcomer that plugs straight into your Steam, Epic and GOG libraries; and GameHub, the closed-source “performance king” from controller maker GameSir. If you have searched “Winlator vs GameNative” or “GameHub vs GameNative” and come away confused, this comparison settles it with specs, benchmarks, pricing and a clear verdict.
All three use the same underlying magic: Box64 to translate x86 instructions to ARM, Wine to provide the Windows layer, and DXVK/VKD3D to convert DirectX calls into Vulkan your phone’s GPU can run. Where they differ is philosophy: Winlator hands you a configurable Windows desktop, GameNative wraps the same engine in a console-style launcher that auto-installs your owned games, and GameHub chases the highest possible frame rate at the cost of privacy. Below we test that trade-off across the full picture, from a 16-row spec sheet to real FPS numbers on a Snapdragon 8 Elite.
Quick verdict: GameNative is the best pick for most people who own a Steam library and want the least friction, and DROIX’s September 2026 testing backs that up by naming it the strongest of the three for library polish and stability rather than outright FPS. Winlator remains the most flexible and battery-friendly for tinkerers and non-game Windows software, though it trails badly on untuned, default-driver hardware. GameHub posts the highest benchmark numbers but carries documented privacy baggage that pushes informed users to the community “GameHub Lite” rebuild instead. Here is the data behind that call.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Are Winlator, GameNative, and GameHub?
Before the benchmarks, it helps to understand that these are three different products solving the same problem in three different ways. They are not forks of each other, and the names are easy to mix up because all three end up running a Windows .exe on your phone. Here is what each one actually is as of September 2026.
Winlator: the original Windows container for Android
Winlator, built by developer brunodev85, is the project that made x86 PC gaming on Android mainstream. Its GitHub repository sits at roughly 17,986 stars and is licensed under LGPL-2.1, making it genuinely open source. The current build is Winlator 11.1 (Hotfix 2), following the 11.0 “Final” release from September 2025. Winlator gives you a configurable Windows container: you create a “container,” set your Box64 and graphics options, then install games from their setup files exactly as you would on a PC. It is the only one of the three that also runs non-game Windows software, including emulators, old productivity apps and launchers, because it does not assume you are playing a game at all.
GameNative: your Steam library, on your phone
GameNative, maintained by utkarshdalal, is the fastest-rising project in the space. Created in April 2025 and grown out of the Pluvia unofficial-Steam-client community, it reached its 1.0.0 release on June 6, 2026, with a 1.1.0 pre-release following on June 23. Its repository holds around 8,303 stars under a GPL-3.0 license, written in Kotlin with a PlayStation-style console UI. The pitch, straight from its README, is simple: “Play the PC games you already own, from Steam, Epic and GOG, on your Android device, with cloud saves.” You log in to Steam, your library appears, you tap install, and a community-sourced config is applied automatically so many titles “just work.” A 35,000-strong Discord drives compatibility fixes.
GameHub: the closed-source performance king
GameHub is the outlier. It is a proprietary, closed-source app distributed by GameSir (the Xiaoji controller brand), reported to be around version 5.3.5 in Q2 2026 according to DROIX’s testing. GameHub ships highly tuned DXVK and VKD3D builds plus AMD FSR 3 upscaling and frame generation, which is why it tops the raw FPS charts. The catch is that the official build has drawn heavy criticism over invasive permissions and telemetry, enough that the community produced a stripped-down rebuild called GameHub Lite. We cover that controversy in detail further down.
Winlator vs GameNative vs GameHub: Full Specs Comparison
The table below maps every meaningful difference across the three apps, current as of September 2026. Star counts and version numbers are pulled directly from each project’s GitHub and release pages; GameHub figures are sourced from independent reviewers since it is closed source. Read this first, then dive into the sections that matter for your hardware.
| Feature | Winlator | GameNative | GameHub |
|---|---|---|---|
| Developer | brunodev85 (community) | utkarshdalal (community) | GameSir / Xiaoji (commercial) |
| License | LGPL-2.1 (open source) | GPL-3.0 (open source) | Proprietary (closed) |
| Latest version (Aug 2026) | 11.1 (Hotfix 2) | 1.0.0 / 1.1.0 pre-release | ~5.3.5 (reported) |
| GitHub stars | ~17,986 | ~8,303 | N/A (closed) |
| Core engine | Wine + Box86/Box64 | Wine/Proton + Box64 | Wine + Box64 (modified) |
| Graphics translation | DXVK, VKD3D, D7VK, Gladio | DXVK, VKD3D, FEX profiles | DXVK, VKD3D + FSR 3 |
| Store integration | None (manual install) | Steam, Epic, GOG, Amazon | Built-in catalog |
| Cloud saves | No | Yes | Limited |
| Interface | Windows desktop / container | PS5-style console UI | Mobile hybrid |
| Minimum Android | 8+ (varies by fork) | 8–14 | 10+ |
| Runs non-game Windows apps | Yes | No (games only) | No |
| Controller support | Yes | Yes (+ editor, on-screen HUD) | Yes |
| Custom GPU drivers | Manual import (Turnip) | Manual import (Turnip) | Bundled / optimized |
| Telemetry | Minimal | Anonymous, opt-out (PostHog) | Heavy (cleaned in Lite) |
| Price | Free | Free (donations) | Free |
| Best for | Tinkerers, battery, any .exe | Steam/Epic/GOG owners | Maximum AAA FPS |
Three patterns jump out. First, the two open-source options (Winlator and GameNative) are converging on the same engine but diverging hard on user experience. Second, GameHub trades transparency for speed. Third, only Winlator is a true general-purpose Windows environment; the other two are gaming-only. Keep those three facts in mind as we move into how the emulation actually works.
How Android PC Emulation Works: Box64, Wine, DXVK and Proton
None of these apps is an “emulator” in the console sense. They are translation layers. Your phone’s Snapdragon or MediaTek chip uses an ARM64 instruction set, but Windows games are compiled for x86/x86-64. Bridging that gap takes a stack of separate technologies working in real time, and understanding the stack explains why the same game can run at 60 FPS in one app and stutter in another.
At the bottom sits Box64 (and Box86 for 32-bit titles), the dynamic recompiler by developer ptitSeb that converts x86 CPU instructions into ARM on the fly. Above it runs Wine, or in GameNative’s case increasingly Proton (Valve’s gaming-tuned Wine variant), which provides the Windows API so the game thinks it is talking to Windows. Graphics are the hard part: games issue DirectX calls, which DXVK (DirectX 9/10/11) and VKD3D (DirectX 12) translate into Vulkan. Winlator 11.1 even added D7VK for ancient DirectX 7 DirectDraw titles, plus an experimental OpenGL path called Gladio.
The final link is the Vulkan driver itself. Stock Android GPU drivers are tuned for mobile games, not desktop workloads, so the community ships custom Mesa Turnip drivers for Qualcomm Adreno GPUs that can lift frame rates 30–50% in many titles. This is the single biggest performance variable, and it is why two people with the “same” phone report wildly different results. GameHub bundles optimized drivers; Winlator and GameNative ask you to import them. A typical Winlator container tuning looks like this:
# Example Winlator 11.1 container tuning (Box64 + DXVK)
BOX64_DYNAREC_BIGBLOCK=1 # larger recompiled blocks = faster CPU
BOX64_DYNAREC_STRONGMEM=1 # fixes some multi-threaded crashes
BOX64_DYNAREC_FASTNAN=0
DXVK_FRAME_RATE=60 # cap to save battery / reduce heat
DXVK_HUD=fps,frametimes # on-screen performance overlay
MESA_VK_WSI_PRESENT_MODE=mailbox
WINEDEBUG=-all # silence Wine logging for performanceGameNative hides almost all of this. Instead of editing variables, you rely on its automatically applied per-game configs, which the community has tuned and uploaded. That is the core philosophical split: Winlator exposes the knobs, GameNative sets them for you, and GameHub solders them shut. For a broader look at how on-device translation compares to streaming, our guide to the best cloud gaming services in 2026 covers the alternative approach.
Performance Benchmarks: FPS on Snapdragon 8 Elite and Handhelds
Benchmarks for Android PC emulation are messy because results swing on the GPU driver, the per-game config, and thermal headroom. To keep this honest, the numbers below are drawn from independent testing by DROIX on a Snapdragon 8 Elite handheld (the AYN Odin 3), cross-referenced with project release notes and community compatibility reports. Treat them as realistic ranges, not guarantees. All testing is at 720p, the standard target resolution for this class of device.
| Game (Snapdragon 8 Elite, 720p) | Winlator 11.1 | GameNative 1.0 | GameHub 5.3.5 |
|---|---|---|---|
| Cyberpunk 2077 (720p, Low + upscaling) | Demanding, sub-30 baseline | In testing | 60+ FPS (FSR 3 + Frame Gen) |
| The Witcher 3 (Medium) | 55–60 FPS (device spoof) | Playable | 55–60 FPS |
| GTA V (Normal) | 40+ FPS | Playable | 50–60 FPS |
| Skyrim LE (modded, GOG) | 50–60 FPS | Stable 60 FPS (Glibc/Modded) | 60 FPS |
| NFS Payback | Variable | – | 55–60 FPS |
The headline from DROIX’s September 2026 testing is that GameHub wins raw FPS in heavy AAA titles: its bundled FSR 3 frame generation is the only path that pushes Cyberpunk 2077 to 60+ FPS at 720p Low on a Snapdragon 8 Elite, where Winlator and GameNative both struggle. But that number is not the full story once you leave bleeding-edge AAA titles. DROIX’s own comparison labels GameNative the pick for “library polish” rather than top frame rate, and its benchmark table backs that up: Skyrim Legendary Edition on GOG holds a stable 60 FPS with Glibc/Modded settings, matching GameHub thanks to community FEX compatibility profiles, while Winlator lands within a few frames after manual tuning. The DROIX testing also notes that Winlator’s “device spoofing” trick, making a game think it is on a different GPU to unlock a better driver path, can close a 30 FPS gap on its own.
Older silicon tells a different story. On a Snapdragon 8 Gen 2 device (a Galaxy Z Fold 5 in XDA’s testing), even Portal 2 took effort, and demanding titles dropped to the 30–40 FPS range across all three apps. On a Snapdragon 8 Gen 3 handheld like the AYANEO Pocket S2 Pro, the same DROIX comparison puts The Witcher 3 at just 30–40 FPS on Winlator with default drivers, against 55–60 FPS on GameHub with FSR 3 enabled on that same chip and title. The lesson: chip generation and driver tuning matter more than which app you pick, and Winlator specifically pays a bigger tax for staying on default drivers than GameHub does. If you are choosing hardware, our Steam Deck vs ROG Ally comparison is a useful reality check on what dedicated handhelds deliver for the money.
September 2026 Verdict: Best FPS, Best Library, Best Flexibility
Boiled down to one line each: GameHub wins on raw AAA frame rate, GameNative wins on library polish and stability, and Winlator wins on flexibility for tinkerers and non-game software. Here is what that means in practice, category by category:
- Best raw FPS: GameHub. Its bundled FSR 3 frame generation is the only path that reaches 60+ FPS in Cyberpunk 2077 at 720p Low on a Snapdragon 8 Elite.
- Best library polish and stability: GameNative. Its Skyrim Legendary Edition result on GOG holds a stable 60 FPS with Glibc/Modded settings, and its auto-applied per-game configs mean less manual tuning than Winlator day to day.
- Best (and worst) on untuned hardware: neither, really. Winlator’s default-driver result on a Snapdragon 8 Gen 3 handheld is just 30–40 FPS in The Witcher 3, well behind GameHub’s 55–60 FPS with FSR 3 enabled on the same chip and game, which is exactly why installing a Turnip driver pack (covered next) matters more for Winlator than it does for GameHub.
GPU Drivers: The Single Biggest Performance Variable
If you take one thing from this article, make it this: the custom Vulkan driver you install matters more than the app you choose. Qualcomm’s stock Adreno drivers are not built for desktop DirectX workloads, so the community maintains Mesa Turnip driver packs tuned per GPU generation. Installing the right one can be the difference between a slideshow and a smooth 60 FPS. GameHub bundles these, which is a big part of why it benchmarks ahead out of the box. Winlator and GameNative both let you import them manually.
| Adreno GPU | Example chip | Recommended Turnip driver pack |
|---|---|---|
| Adreno 8xx | Snapdragon 8 Elite | StevenMXZ / whitebelyash builds |
| Adreno 7xx | Snapdragon 8 Gen 2 / Gen 3 | Mr Purple T25 / T26 |
| Adreno 6xx | Snapdragon 865 / 870 | K11MCH1 R5 |
Importing a driver is the same basic flow in both Winlator and GameNative: download the Mesa Turnip .zip for your exact Adreno GPU, open the app’s graphics-driver settings, import the file, then assign it to your game container along with a matching DXVK version. Mismatched driver and wrapper versions are the most common cause of black screens and crashes, so changing one variable at a time is the golden rule. MediaTek and Samsung Exynos GPUs have far weaker community driver support, which is why Snapdragon devices dominate this scene, a recurring theme in how the wider mobile gaming market has fragmented by chipset.
Pricing and Hardware: What It Really Costs to Run PC Games on Android
The good news: all three apps are free. There is no subscription, no paywall, and no per-game charge. The real cost is the hardware and the games you already own. Unlike cloud services such as GeForce Now or Xbox Cloud Gaming, you are running locally, so you pay once for a capable device and nothing monthly. The table below lays out the practical cost of entry in 2026.
| Cost factor | Winlator | GameNative | GameHub |
|---|---|---|---|
| App price | Free | Free | Free |
| Distribution | APK (GitHub) | APK (GitHub / site) | APK (third-party) |
| In-app purchases | None | None (Ko-fi donations) | None reported |
| Games | You own (any .exe) | You own (Steam/Epic/GOG) | You own |
| Recommended chip | Snapdragon 8 Gen 2+ | Snapdragon 8 Gen 2+ | Snapdragon 8 Elite |
| Recommended RAM | 6–8 GB | 8 GB | 8–12 GB |
| Storage per AAA game | 30–100 GB | 30–100 GB | 30–100 GB |
| Typical device cost | $200–$600 | $200–$600 | $500+ flagship |
| Monthly cost | $0 | $0 | $0 |
In practice, the sweet spot is a Snapdragon 8 Gen 2 or newer Android device with at least 8 GB of RAM and plenty of storage. Dedicated Android gaming handhelds from AYN, AYANEO and Retroid, many of which ship in the $200–$600 range, are the most popular hosts because they have physical controls and better cooling than a phone. A flagship phone with a Snapdragon 8 Elite will out-benchmark them but throttles faster under sustained load. Either way, the headline remains: this is a one-time hardware cost versus the recurring fees of streaming, which is the central calculus we break down in our Parsec vs Moonlight vs Steam Link guide to streaming your own PC instead.
Setup and Ease of Use Compared
This is where the three apps feel most different. GameNative is the closest to “install and play.” GameHub is nearly as easy but asks for trust. Winlator is the most powerful and the most fiddly. Here is the realistic onboarding experience for each as of September 2026.
GameNative: log in and tap install
GameNative’s flow is the shortest: download the APK, install it, log in to your Steam account, pick a game from your library, and hit play. Because community configs are applied automatically, many titles boot with no tuning. The PS5-style interface, controller support, custom control editor and on-screen HUD make it feel like a console. When a game needs help, the 35,000-member Discord usually has an answer. A typical auto-applied per-game config, which you normally never see, looks like this:
# Example GameNative auto-applied per-game config (illustrative)
graphicsDriver: turnip-24.x
dxWrapper: dxvk-2.x
box64Preset: performance
audioDriver: pulse # reworked, low-latency in v1.1
renderer: surfaceflinger # v1.1: lower latency, higher FPS
proton: 10 # enables Bionic Steam client / DRM
cloudSaves: enabledWinlator: build your own container
Winlator expects more from you. You create a container, choose your Box64 preset, pick your DXVK and Wine versions, import a GPU driver, then install the game from its setup files and point Winlator at the executable. None of this is hard, but it is several decisions deep, and the reward for getting it right is the broadest compatibility and the best battery life of the three. Winlator is also fragmented into many community forks (CMOD, Frost, Bionic and others), which adds choice but also confusion about which build suits your chip.
GameHub: fast, but read the permissions
GameHub’s official build is genuinely quick to set up and benchmarks well immediately because drivers are bundled. The friction is not technical. It is the permissions it requests and the telemetry it ships, which we detail in the controversy section below. Many experienced users sidestep this by running GameHub Lite, the community rebuild that strips the tracking. If you value the least setup overall, GameNative is the safer “easy” choice. If you have ever set up RetroArch or EmuDeck, Winlator’s container model will feel familiar.
Game Compatibility: What Actually Runs in 2026
Compatibility is the question that decides whether any of this is worth your time. The honest answer in 2026 is “a lot, but not everything, and not always on the first try.” Each app approaches the problem differently, and that shapes what you can realistically expect to play.
GameNative maintains a public compatibility database at gamenative.app/compatibility where the community logs which games run and how well, broken down by device. This is its biggest practical advantage: before you spend an hour, you can check whether your exact title works on your exact phone. The app then applies known-good configs automatically. Its 1.1 pre-release added “Bionic Steam client” support on Proton 10, which improves DRM handling, online connectivity and DLC, a meaningful step for games that previously refused to launch.
Winlator’s compatibility is theoretically the widest because it imposes the fewest assumptions: if a game runs under Wine and Box64, Winlator can usually run it, including older and non-Steam titles, and even non-game software. The trade-off is that you may have to find the right settings yourself. GameHub leans on its optimized DXVK/VKD3D builds and FSR 3 to brute-force demanding AAA games to playable frame rates, but its closed nature means you cannot inspect or fix a broken title yourself, so you wait for GameSir. The single biggest compatibility blocker across all three remains anti-cheat: most kernel-level and many user-mode anti-cheat systems simply do not work under translation, so competitive online shooters are largely off the table regardless of which app you choose.
The GameHub Controversy: Trackers, Permissions and GameHub Lite
No comparison of these apps is complete without addressing why GameHub is described as “the most controversial app in the scene.” The performance is real, but so are the concerns, and they are well documented by mainstream outlets rather than rumor. According to XDA-Developers’ investigation, the official GameHub APK has shipped with invasive permissions, including location, microphone, camera and contacts, alongside telemetry from Firebase, Google Analytics and the Chinese trackers Umeng and JPush.
There are also attribution disputes. Per the same XDA report, developers have accused GameSir of using their work without credit. One contributor said his Vulkan renderer was incorporated without attribution, and another said a code-comparison check flagged the “Vulkan graphics wrapper” inside GameHub as his own code with 95.7% certainty. The report further notes that GameSir previously released EggNS, a Nintendo Switch emulator that allegedly contained unattributed code from the Yuzu and Skyline projects. For an app that requests camera and contacts access to play single-player PC games, that history understandably makes privacy-conscious users uneasy.
The community response was GameHub Lite, currently maintained by a developer known as Producdevity (originally created by Clippy). It is a reverse-engineered rebuild that removes the trackers, unnecessary permissions and background services. XDA reports the cleanup shrinks the app from 118 MB to about 52 MB and that the lighter build actually runs faster than the official one. If you want GameHub-level frame rates without the tracking and permissions baggage, GameHub Lite is the safer way to get them, and it is the build several of the benchmark figures above, including the NFS Payback result, were actually measured on.
Which App Is Growing Fastest in 2026?
Momentum looks different depending on how you measure it. GameNative is iterating the fastest of the three: it went from a 1.0.0 release on June 6, 2026 to a 1.1.0 pre-release just seventeen days later on June 23, with Bionic Steam client support and a reworked, lower-latency audio and rendering path among the headline changes. Winlator remains the largest project by GitHub stars at roughly 17,986, but its release cadence has slowed to hotfixes, sitting at 11.1 (Hotfix 2) since the 11.0 “Final” build shipped in September 2025.
GameHub’s growth shows up differently because it is not open source, so there is no star count to point to. GameSir reported the app had passed five million downloads by February 2026, which would give it by far the largest raw install base of the three. That figure needs a caveat: a meaningful share of GameHub’s active users, especially anyone chasing top benchmark numbers without the tracking baggage covered above, are likely running the community GameHub Lite rebuild rather than the official tracked APK, so five million overstates how many people are actually using the version XDA investigated. As of early September 2026, none of the three projects had shipped a verified update since GameNative’s June 23 pre-release.
Frequently Asked Questions
Is GameHub safe to use in 2026?
The official GameHub APK still ships with more invasive permissions and third-party telemetry (Firebase, Google Analytics, Umeng and JPush) than Winlator or GameNative, and the attribution disputes covered above remain unresolved. If you want GameHub’s frame rates without that baggage, install the community GameHub Lite rebuild instead of the official app.
What are the latest versions of Winlator, GameNative and GameHub right now?
As of September 2026, Winlator is on 11.1 (Hotfix 2), GameNative has shipped 1.0.0 with a 1.1.0 pre-release from June 23, 2026, and GameHub is reported at around version 5.3.5. None of the three had shipped a verified update beyond that as of early September 2026.
Do I have to pay for Winlator, GameNative or GameHub?
No. All three apps are free to download with no subscription and no per-game charge. Your only real cost is the Android device itself and the games you already own.
Can I play online multiplayer or competitive games?
Rarely. Kernel-level and many user-mode anti-cheat systems do not work under Wine/Box64 translation on any of the three apps, so competitive online shooters are largely off the table regardless of which one you pick. Single-player and co-op titles without anti-cheat are where all three shine.
Which one should I actually pick?
If you own a Steam, Epic or GOG library, GameNative’s auto-installed configs and library polish make it the least friction day to day. If you want to run non-game Windows software or need the deepest tuning options, Winlator is more flexible, though it needs a manually imported driver pack to compete with GameHub on untuned hardware. If raw AAA frame rate is what matters most, GameHub’s FSR 3 frame generation gives it the edge, but install GameHub Lite rather than the official app to avoid its tracking and permissions issues.
None of these apps has replaced a dedicated Windows PC for the most demanding, competitive or brand-new AAA releases, but for a huge slice of existing libraries they have closed the gap further than most people expect. Start with GameNative if you want the least setup and the most polished library experience, keep Winlator on hand for anything outside a normal Steam library, and treat GameHub the way XDA and the developer community have: enjoy the frame rate, skip the official tracker-laden build in favor of GameHub Lite.
