Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
2026-11-16 · Setup guide
Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.
GameNative is the easiest way to play the PC games you already own on an Android handheld. You sign in to Steam, Epic, GOG or Amazon, press install, and a lot of the time the game simply runs. Somebody else already worked out the settings, and the app applies them for you.
It is also moving fast. Version 1.4.0 arrived on 5 November 2026 with a new default renderer and a new default Proton, and most guides written over the summer describe an app that has since changed underneath them. This one is written against 1.4.0.
The Short Version
- GameNative is free and open source, under GPL-3.0. It is funded by donations and by optional sponsored loading screens you can switch off.
- It is on the Play Store now, and also available as an APK from the official site. On a handheld, take the APK. Step 1 explains why.
- It runs games through Proton and FEX. Older write ups, including one of ours, describe it as plain Wine with Box64. That has been out of date since the end of 2025, when Proton and FEX arrived. Box64 is still there as an option.
- Community settings are applied automatically. That is the whole idea of the app, and it is why it feels easier than Winlator.
- Any Android GPU can try it. Snapdragon handhelds with Adreno graphics are the best supported. The project's own data puts Mali behind, but nowhere near zero.
- Anti cheat games do not work. Nothing on Android can run kernel level anti cheat.
- Support happens on Discord. Bug reports filed on GitHub are closed automatically.
Will It Run on My Handheld?
GameNative publishes something nobody else in this corner does: compatibility data built from real play sessions. Each launch reports the game, how long it ran and its average frame rate, and the project turns that into a rating per device.
Here is how the handhelds our readers own looked on 16 November 2026.
| Handheld | GPU | Games rated Great or Works | Games with enough data |
|---|---|---|---|
| AYN Thor | Adreno 740 | 87% | 8,712 |
| AYN Odin 3 | Adreno 830 | 86% | 4,576 |
| AYN Odin 2 Portal, all tiers | Adreno 740 | 86% | 4,027 |
| Retroid Pocket 6 | Adreno 740 | 85% | 4,770 |
| Retroid Pocket Nova | Adreno 740 | 85% | 2,910 |
| Retroid Pocket Flip 2 | Adreno 650 | 84% | 2,522 |
| Retroid Pocket 5 | Adreno 650 | 82% | 3,478 |
| Mangmi Pocket Max | Adreno 650 | 89% | 301 |
| Anbernic RG477M | Mali-G615 | 81% | 344 |
| Anbernic RG476H | Mali-G57 | 80% | 313 |
| Retroid Pocket Classic | Adreno A12 | 77% | 327 |
| Retroid Pocket 4 Pro | Mali-G77 | 61% | 514 |
Two things to understand before you lean on that table.
It is the share of what people tried, not a score. Each figure is the share of the games owners actually played on that device. Owners of a modest handheld are likely to try lighter games, so a modest handheld can post a big number. The RG476H's 80% does not mean it runs what a Thor runs. It means most of the games its owners chose to try ran.
The bar is low on purpose. A session counts as playable if the game ran for more than 60 seconds at 15 frames per second or better. The project says itself that this is a low bar, and that its most played games skew lighter and older. Demanding new releases will do worse than these figures suggest.
What the table does tell you clearly:
- Every Snapdragon handheld here clears 80%. For the games people actually play in GameNative, the gap between an Adreno 650 and an Adreno 830 is smaller than the price gap. A Retroid Pocket 5 is a real option.
- Mali is not a dead end. Across every device in the data, 65% of Mali game and device pairs rate Great or Works, against 81% for Adreno. Both Anbernics do well. The Pocket 4 Pro lags well behind, even though its Mali-G77 is a stronger GPU than the RG476H's Mali-G57. That is a reminder that this table measures more than raw power. Drivers, Android versions and the games owners choose all feed into it.
- That corrects something we published. Our Steam on Android comparison said Mali handhelds had no path to PC games. That was true of DroidDeck. It is not true of GameNative, and that page now says so.
Before you buy anything for this, check your own game. The official site has a compatibility search where you filter by game and by GPU.
What You Need
- An Android handheld on Android 8 or newer. Android 10 or newer if you want the Play Store build.
- Storage, and more than you think. The APK alone is roughly a 570MB download. Every game gets its own Windows environment on internal storage, and the games themselves are PC sized. A large, fast microSD card is the cheap fix. Our microSD card guide covers which ones are worth buying.
- A Steam, Epic, GOG or Amazon account with games you own in it.
- Optional: Lossless Scaling in your Steam library, if you want frame generation. More on that in step 5.
Step 1: Install It, and Pick the Right Build
There are two official ways to install GameNative, and they are not quite the same app.
The Play Store build installs and updates like any other app. It needs Android 10 or newer. In the project's source it is the "modern" build, and when it arrived it gave up a few things the original build has: adding your own games from a folder, a D drive, and the older glibc container type. Custom games have since been fixed for some devices. Not everything has come back.
The APK from the official site, gamenative.app, is the standard build. It is the download the project's own README links first. It runs on Android 8 or newer and keeps every feature. You update it yourself by installing the next release over the top, which keeps your games and settings. Obtainium can do that for you.
On a dedicated gaming handheld, take the APK. You lose automatic updates and gain the full feature set, and on a device that exists to run games that is the right trade. On a phone you also use for everything else, the Play Store build is a perfectly reasonable choice.
Get it from one of those two places only. GameNative is popular enough to attract unofficial mirrors and repackaged APKs, and an app that signs in to your Steam account is the last thing to take from a stranger. Our guide to downloading emulators safely explains how to spot the fakes.
Step 2: Sign In, Then Point It at Your Card
Steam first. Use QR Login. You scan the code with the Steam app on your phone and you are in, which on a handheld with no keyboard beats typing a password with a thumbstick. A username and password with Steam Guard works too.
Then the other stores. Epic, GOG and Amazon sign in from inside the app, and their libraries appear alongside Steam's. Cloud saves sync for Steam, and the app also handles GOG and Epic saves.
Then storage, before you install anything. Turn on Write to external storage in the settings, and new installs go to your microSD card instead of internal storage. The Container and Storage Manager in the same settings moves a game between internal storage and the card later, and shows what is taking up space.
Two storage details that save headaches:
- Each game's Windows environment stays on internal storage, even when the game itself is on the card. The app calls these containers. Since 1.3.0 they share common files, and the project says pressing Play on a game installed before then shrinks its container by up to 2GB.
- Faster loading from external storage is a separate toggle. The app's own description says it can speed up boot from the card a lot, but may cause issues in some games. It was switched on for everyone in 1.2.0, broke things, and became optional a few weeks later. Leave it off unless load times bother you.
Step 3: Install a Game, and Let Known Configs Do the Work
Make your first game a light one. A 2D indie or something ten years old tells you the setup works before you blame a demanding game for a problem in the setup.
Leave Auto-apply known config switched on. In the app's words, it applies recommended settings for Steam games on first launch. Those recommendations come from other players who got the same game running. This is the feature that makes GameNative feel easy, and it is also why the app reports launches: those reports are where the known configs come from.
Expect the first launch to be slow. The app downloads components and builds the game's container the first time. The second launch is the real one.
Read the labels in your library. GameNative rates games as Great, Works, Unreliable or Broken, from the same play data as the table above. A game marked Broken on your GPU is worth skipping until that changes.
When a fix is announced, apply it. The release notes regularly name games that were broken and are now fixed, with an instruction to use the known config. In 1.4.0 that list included Oblivion Game of the Year Edition, Call of Duty: Black Ops, Spelunky 2, Dragon Ball FighterZ and Civilization V, plus a set of Java games such as Project Zomboid.
Step 4: The Settings Worth Knowing
GameNative shares Winlator's lineage, so its per game container settings look familiar if you have used Winlator. You will rarely need to touch them. These are the ones that change outcomes.
- Wine Version. Despite the label, the default is GameNative's own Android build of Proton, Valve's Wine based compatibility layer. 1.4.0 moved the default to Proton 11. If a game that worked before the update broke after it, try the Proton 10 build first.
- 64-bit Emulator. This is the translator that turns x86 PC code into ARM code your handheld understands. The choices are FEXCore, which is the default, and Box64. A game that crashes at boot on one is worth one try on the other.
- Container Variant. Bionic or glibc. Bionic has been the default since December 2025 and frame generation needs it. Glibc is the older type, and the Play Store build does not have it.
- Graphics Driver. Turnip, the open source driver for Adreno GPUs, plus system, wrapper and Vortek options. 1.4.0's component list adds a Turnip build made for the newest Adreno 8xx chips alongside a newer general Turnip release. On the Adreno 710 family it now defaults to the system driver. The Driver Manager in settings installs other driver packages. Our Turnip drivers guide covers which one to try first on which chip.
- DXVK and VKD3D. These translate DirectX 9 to 11 and DirectX 12 into Vulkan. Leave them on the defaults unless a known config changes them.
- Display Renderer. 1.4.0 made Gamescope the default on Adreno. It brings upscaling (FSR, NIS, Qualcomm's SGSR or integer scaling), HDR in beta, and ReShade effects. The project itself flagged this as a potential breaking change.
That last point is the most useful thing in this section. If a game that worked last week now shows a black screen, switch the Display Renderer back before you change anything else.
Step 5: Controls, the Quick Menu and Frame Generation
Controls map themselves. On a handheld with built in controls there is normally nothing to do. Steam Input can be switched on per game for games that expect a Steam controller layout, and there is gyro aiming, per profile mouse speed, and an editor for on screen controls if you ever play on a phone.
The Quick Menu is the one thing to learn. Press your handheld's Back button during a game and it opens. It holds Exit, the controller settings, the performance HUD, the Gamescope options and, on supported devices, power control. Press Back again to close it.
Frame generation uses LSFG-VK, the Vulkan version of Lossless Scaling's frame generation. There are strings attached, and the app is upfront about them:
- It needs Lossless Scaling in your Steam library. That is a paid app on Steam. Once you own it, GameNative downloads it from your library for you.
- It is only known to work on Adreno 6xx and newer, in the app's own words.
- It needs a bionic container, the default.
Frame generation makes motion look smoother. It does not make a game respond faster, and it looks worst when the real frame rate underneath is low. Use it to smooth a game that already holds a steady 30 or so, not to rescue one that does not.
Step 6: The Handheld Extras
Power control. On devices that support it, GameNative can set CPU clocks and fan speed from inside a game, through the Quick Menu. The app turns this on by default on the three devices it lists as tested: the AYN Odin 3, the Retroid Pocket 6 and the Retroid Pocket Nova. Since 1.3.0 it also resets clocks and fan if the app is force closed, so a crash no longer leaves your handheld running hot.
The performance HUD names the bottleneck. 1.4.0 added a toggle that shows the limiting factor, heat, CPU or GPU. On a handheld that is the most useful single readout there is, because it tells you whether to change a setting or change the fan profile.
A known controller bug on two devices is fixed. Some games, Castle Crashers among them, saw two controllers by default on the AYN Thor and the Retroid Pocket Flip 2. That was fixed in the 1.4.0 cycle, so update before you start remapping.
Online Play, and the Other Launchers
Leave the Steam client setting on headless, the default. The app's own description is the best summary: headless is recommended, it is required for EA, Rockstar, Ubisoft and other launchers, and it enables multiplayer and fixes DRM and controller issues.
That is what made the big additions of the last two months possible. Since 1.3.0, EA games work, tested by the project with Need for Speed: Most Wanted, The Sims 4 and Titanfall. So do Rockstar games, tested with Red Dead Redemption 2, GTA V Legacy, GTA IV and L.A. Noire. 1.4.0 added GOG Galaxy services, fixed Epic games that use Epic Online Services, and lists Battle.net games including Diablo IV and Overwatch 2 as fixed.
There is also an Enable Experimental Bionic Steam option. The app says it enables online play, does not always work, and asks you to back up your saves before you try it. We would say the same.
What still never works: kernel level anti cheat. The anti cheat expects a Windows kernel it can inspect, there is no Windows kernel anywhere in this stack, and no update will change that.
Privacy, Sponsors and the AI Helper
Worth knowing up front, and GameNative is more open about all three than most apps.
Analytics. The README says the app uses PostHog and collects no names, emails, IP addresses or device identifiers. Some events are always sent: game launches, closes and exits with the game name, store, session length, average frame rate and container settings, plus installs and uninstalls. Those are what build the known configs and the table near the top of this page. Everything else, such as feature usage, login success or failure, recommendation clicks and cloud sync events, can be switched off under Settings, Info, Usage Analytics.
Sponsored loading screens. Since 1.2.1 the app can show a sponsor card while a game boots. The project asks you to leave it on to fund development. There is a Sponsored loading screens toggle if you would rather not, and a separate one for game recommendations.
The AI helper. Optional, and you can remove it from view with Hide AI features. If you use it on a broken game, the app warns that it can change that game's files or build a new driver or emulator for your device. That can genuinely help. Back up your saves before you let it.
Known Problems, and What to Do About Them
A game that worked now shows a black screen after updating. Switch the Display Renderer away from Gamescope. If that does not do it, try the Proton 10 build.
A game will not start at all. Work down this list, one change at a time: check the compatibility search for your GPU, use the known config, switch the 64-bit Emulator between FEXCore and Box64, then try another graphics driver.
Games on the card load slowly. Try Faster loading from external storage. Turn it off again if a game starts misbehaving.
Internal storage keeps filling up. That is containers. Open the Container and Storage Manager and remove the containers for games you have finished. The app warns that saves kept inside the Windows environment can be lost when you do. Games with Steam Cloud saves are safe. Check the others first.
Your Steam library shows only part of your games. Fixed in 1.4.0. Update.
You want to report a bug. Use the Discord server or the in app support. GitHub issues are closed automatically, by design.
GameNative, GameHub or DroidDeck?
The short answer, by what you care about:
- GameNative if you own games in more than one store, want settings applied for you, or have a GPU that DroidDeck rejects. It is the broadest of the three and the one with published compatibility data.
- GameHub if you want the fewest steps of all and are comfortable with a closed source app from a controller company. Our GameHub setup guide covers it, including the safety questions.
- DroidDeck if you have an Adreno 730 or newer and want Valve's real ARM64 Steam client rather than an app that talks to Steam for you. See DroidDeck on Android handhelds.
The full side by side, including Armada and Winlator, is in DroidDeck vs GameNative vs GameHub vs Armada.
If you are buying a handheld for this, the chip is the whole decision. Every device at the top of the table runs an Adreno 740 or 830.
Frequently Asked Questions
Is GameNative free?
Yes. It is open source under GPL-3.0 and costs nothing. The project is funded by donations and by sponsored loading screens, which you can switch off in the settings. Frame generation is the one feature that needs a paid app, Lossless Scaling, in your Steam library.
Is GameNative safe?
The app itself is open source and widely used, and its README documents exactly what analytics it collects. The risk is fake copies. Install it only from the Play Store or the official site, gamenative.app, never from an APK mirror, because it signs in to your Steam account.
Is GameNative on the Play Store?
Yes, for Android 10 and newer. The Play Store build gave up some features at launch, including custom games from your own folders and the older glibc container type, and not all of them have come back. The APK from the official site is the full build and runs on Android 8 and newer. On a dedicated handheld, use the APK.
Does GameNative work on Mali or Anbernic handhelds?
Yes, with caveats. The project's own play data rates 65% of Mali game and device pairs as Great or Works, against 81% for Adreno. On 16 November 2026 the Anbernic RG477M showed 81% of the games its owners tried and the RG476H 80%. Those figures describe the games owners chose to try, not everything the device can run. Frame generation and Turnip drivers are Adreno only.
Where is the GameNative compatibility list?
On the official site. There is a compatibility search, filterable by game and GPU, built from player reports, and a "Will it run on my phone?" page built from anonymous play session data, with a figure per device. The same data drives the Great, Works, Unreliable and Broken labels in the app.
Does GameNative use Wine or Proton?
Proton. It has offered Proton builds since December 2025, shipped its own Android builds of Proton from May 2026, and used Proton 11 by default since version 1.4.0. The x86 to ARM translation is done by FEXCore by default, with Box64 as an alternative in each game's settings.
Can GameNative play Epic, GOG and EA games?
Yes. Epic, GOG and Amazon libraries sign in alongside Steam. EA, Rockstar and Ubisoft games that launch through their own launchers need the headless Steam client mode, which is the default. Games with kernel level anti cheat do not work.
What is the difference between GameNative and Winlator?
They share a lineage, and GameNative grew out of the same container approach. GameNative adds store logins, cloud saves, automatic per game settings and published compatibility data. Winlator gives you containers to tune by hand, which is more work and more flexible, and it remains the better tool for games that come from no store at all.
Related Guides
- DroidDeck vs GameNative vs GameHub vs Armada, the full comparison
- GameHub setup guide
- Turnip drivers guide
- Winlator setup guide
- DroidDeck on Android handhelds
- FEX, Box64, Proton, DXVK: what translation layers actually do
- AYN Thor setup guide
- Retroid Pocket 6 setup guide
- Snapdragon 8 Elite handhelds
Written 16 November 2026 against GameNative 1.4.0. Versions, defaults and features come from the project's release notes, README, source code and official site, read the same day. Compatibility figures are the project's own. We have not run GameNative on any hardware and publish no performance figures of our own.

