Winlator games list 2026: what runs well, why games crash, and native ports to try instead

Winlator turned a lot of Android phones into small Windows gaming machines. It is also the reason for thousands of forum threads that start with the same question: which games actually work? There is no single official Winlator games list, because the answer depends on your phone, your graphics chip and your settings. This guide explains what tends to run well, what tends to fail, how to fix the most common problems, and where a native port is the easier road.

How Winlator runs a PC game

Winlator packs Wine, which translates Windows system calls, together with Box64, which translates x86 processor code into ARM instructions. DirectX graphics go through a further layer such as DXVK or WineD3D before they reach the phone's graphics driver. Every frame passes through these layers, so the same game needs much more power under Winlator than it would as a native app.

Games that usually run well

• Older DirectX 8 and DirectX 9 games from roughly 2000 to 2012: classic shooters, older RPGs and strategy games
• Indie and 2D games with light graphics and no heavy launcher
• Games that run offline without an online account, anti-cheat or a separate store client
• Games tuned down to 720p or lower, with shadows and post-processing switched off

Games that usually struggle

• Modern DirectX 11 and DirectX 12 games that need a strong desktop GPU
• Anything with kernel-level anti-cheat or always-online checks
• Games that ship with heavy launchers or DRM wrappers
• Open-world games that stream large amounts of data from disk, especially on phones with 8 GB of RAM or less

Black screen or crash on start: the usual fixes

• Change the graphics driver: on Adreno (Snapdragon) phones try Turnip, on Mali phones try VirGL or the WineD3D path
• Try a different DXVK version, or switch from DXVK to WineD3D for older DirectX 9 games
• Change the Box64 preset from performance to stability
• Lower the screen resolution of the container and of the game itself
• Give the container more video memory, and close other apps so the phone does not run out of RAM
• Run the game executable directly instead of its launcher

Your phone's chip matters more than the list

Two people with the same game can report opposite results because their phones differ. Snapdragon phones with Adreno graphics have the widest driver choice thanks to Turnip. Mali-based phones have fewer options and often need more tuning. Heat matters too: a game that starts at a smooth frame rate can slow down after twenty minutes once the phone throttles.

The other road: native Android ports

A native port skips the translation layers: the game is rebuilt to run as an ordinary Android app on the phone's own processor and graphics chip. There are no containers, drivers or presets to set up, you install it like any other app, and the phone does less work per frame. Zodita publishes unofficial community ports of PC classics built this way. They are not affiliated with the original publishers.

• Call of Duty 4 (MDW1 Mobile): free demo; on a POCO X7 Pro we measured 75 to 87 FPS
• Skyrim Mobile: free demo
• The Witcher 3 Mobile: free demo set in Kaer Morhen
• BioShock Mobile: free demo
• Half-Life 2 Mobile: demo in testing
• Max Payne 1 and 2, and F.E.A.R.: early access builds

Which one should you choose?

If you own a large PC library and enjoy tuning, Winlator is a great tool and you get the full PC game, mods included. If you want a classic to start in one tap, run cooler and keep working when you are offline, a native port is simpler. Many players keep both: Winlator for experiments, native apps for the games they actually play every day. You can try the Zodita demos for free in the Zodita app and decide for yourself.