DroidDeck vs Winlator: which should you run on Android?

What each one actually is

DroidDeck is a 2026 open-source project (GPL-3.0) that runs Valve’s official Steam client in Big Picture mode, natively on Android. The client itself is the ARM64 build Valve ships for Linux; DroidDeck runs it inside a proot Linux environment and adds a Vulkan compositor. Windows games then run through Valve’s ARM64 Proton, with FEX-Emu translating x86/x64 game code to ARM64. No root is required, and nothing is streamed — games run on the device.

Winlator is the established veteran: an Android app that runs Windows (x86_64) applications with Wine and Box86/Box64. Instead of a native Steam client, you work inside a Windows-like container — run games directly, or install launchers inside it. It has years of community presets and a large library of per-game reports, and its compatibility layer covers a wider range of chipsets than DroidDeck’s strict Adreno requirement.

Side by side

Steam integration: the biggest practical difference

If your games are on Steam, this is the row that matters. DroidDeck runs the real Steam client — the same ARM64 build Valve ships for Linux — so cloud saves, achievements, playtime tracking and the Big Picture interface all work the way you expect them to on a Steam Deck. Your handheld shows up as a Steam machine, not an emulation project.

Winlator has no native Steam client. You can install Steam inside a container and it will mostly work, and many players just launch individual games directly instead. But the integration is manual, and per-game fixes often mean digging into container settings. If you don’t care about Steam features, this difference shrinks to a preference.

Device requirements: where the choice is made for you

DroidDeck’s requirements are explicit in its documentation: Android 9+ on a Snapdragon chip with Adreno 730 or newer graphics (or any Adreno 8xx). That covers Snapdragon 8 Gen 1-era chips and newer — including the handhelds the community tested first, like the Ayn Odin 2, Retroid Pocket 5 and Ayaneo Pocket S. Mali, Xclipse, PowerVR and Adreno 710 devices are unsupported; Adreno 6xx is experimental.

Winlator’s compatibility layer is not tied to the same narrow GPU list, which makes it the realistic option on older or non-Snapdragon devices — with the caveat that performance and stability vary a lot by device and game.

See the full device compatibility list for DroidDeck.

Performance: what we can honestly say

You won’t find our own FPS charts on this page. We don’t run hardware benchmarks, and benchmark numbers for tools like these are notoriously sensitive to the exact device, driver, game version and settings — a chart from one setup rarely transfers to another.

What is fair to say is how the two stacks differ. Both translate x86 game code to ARM on the fly, but with different translators: DroidDeck rides Valve’s Proton with FEX-Emu, while Winlator uses Box64 under Wine. Both end up rendering through Vulkan with the Turnip driver on Adreno hardware. In practice, per-game results vary in both camps, and both projects state plainly that compatibility and performance depend on your device.

For game-specific expectations, the communities are the best source: the DroidDeck Discord collects device reports, and Winlator has years of per-game threads and shared presets.

Setup and day-to-day use

DroidDeck’s setup is unusually guided for this category: install the APK from GitHub Releases, install the Linux runtime, press Play and sign in to Steam. One system setting matters — “Restrict child processes” in Developer options must be turned off before Steam launches; on Android 12 and 13, where the option isn’t always exposed, the app offers a “Fix it for me” button on first launch. After that, it is Steam as usual: download games, launch, play.

Winlator asks more of you up front. You create a container, pick your graphics driver and Box64 preset, and install or launch what you need. The project’s README is full of tips for exactly this — stability presets, Wine Mono for .NET apps, audio latency tweaks. If you enjoy that kind of fiddling, it is a feature. If you don’t, DroidDeck is the shorter path.

The verdict

These two are less competitors than neighbors. DroidDeck is the polished, Steam-native newcomer with a strict hardware gate; Winlator is the flexible veteran that runs on more devices and welcomes tweakers. If your handheld has Adreno 730+ graphics and your games live on Steam, start with DroidDeck. If it doesn’t — or your library lives outside Steam — Winlator remains the workhorse. And since the two don’t conflict, there is no harm in trying both.