
If Winlator feels slow, the answer is almost never a new phone. It is three settings in the right order: the container resolution (lower is faster), the graphics driver (Turnip on Snapdragon, the fallback everywhere else), and the DX wrapper matched to the game's DirectX version. Get those three right and most playable games smooth out.
Every setting here lives in the container's own settings screen. Open it by long-pressing a container on the Winlator home screen and tapping the gear. The best part of the whole system: settings are per container, so you can tune one container for an old DirectX 9 game and another for something heavier without them interfering. When you're experimenting, clone a second container and test there. Keep the working one untouched.
Still installing? Run through the install guide first, then come back. This page assumes Winlator is on your phone and at least one container exists.
The three levers that actually matter
Before the details, the short list in priority order:
- Resolution. Fewer pixels to draw means more frames. This is the most reliable speed boost in Winlator, and it's boring and free.
- Graphics driver. Turnip on Adreno GPUs; the built-in fallback on everything else. Wrong driver here can halve your framerate or worse.
- DX wrapper. DXVK for DirectX 9 through 11, VKD3D for DirectX 12, WineD3D only as a fallback. Match the wrapper to the game's API.
Resolution: the free speed boost
Container resolution is the size of the fake display that Windows programs see inside the container. Lower it, and your phone's GPU draws fewer pixels per frame, which directly means more frames per second. There is no trick here. It is simple arithmetic, and it works every time.
1280x720 is a sensible starting point for most 3D games. Older titles and 2D games can go lower still; some people run classics at 960x540 or even 800x600 and they look perfectly fine on a phone screen. Don't confuse the container resolution with your phone's screen resolution. Winlator renders at the container resolution and scales the result up to fill your screen, so lowering it genuinely reduces GPU work. The image gets a bit softer. The game gets noticeably smoother. That trade is worth making.
If a game feels sluggish, lower the resolution before touching anything else. Most "my game is slow" complaints in the community would die at this step.
Graphics driver: Turnip vs the fallback
The graphics driver is the piece that talks to your phone's GPU, and it is the single biggest lever after resolution. Winlator typically offers Turnip driver builds and a universal fallback driver.
The rule is simple. If your phone has a Snapdragon chip, which means an Adreno GPU, use a Turnip driver. Turnip is an open-source Vulkan driver written specifically for Adreno hardware (the Mesa project's freedreno documentation describes how the driver works), and on those chips it is faster and more compatible than the generic fallback. It is not close. If your phone has a Mali GPU (Samsung Exynos, Google Tensor, most MediaTek chips), Turnip won't work for you. Use the fallback driver and set your expectations accordingly. Mali driver support in this stack is much more limited, and no settings change fixes that.
Turnip comes in versions. Start with the newest one available. If a game misbehaves (strange colors, a crash at one specific screen), try an older Turnip build. Driver regressions happen, and the community usually figures out which build suits which game. Newer is usually better, but "works" beats "newest" every time.
There is a deeper breakdown of every driver, what each GPU family gets, and the Box86/Box64 and Wine layers underneath in the drivers and components explainer. Read it if you want to understand the full stack. You don't need it to pick a driver, though.
DX wrapper: match it to the game's DirectX version
The DX wrapper translates the game's DirectX graphics calls into something your phone can draw. Winlator lets you pick one per container:
- DXVK handles DirectX 9, 10, and 11 by translating them to Vulkan. This is the right pick for the large majority of games people run. If the game came out roughly between 2007 and 2016, DXVK is almost certainly correct.
- VKD3D handles DirectX 12. Only reach for it when the game specifically requires DX12. These are the heaviest workloads in Winlator, and most DX12 titles stay out of reach of phones. Some lighter ones limp along.
- WineD3D translates DirectX to OpenGL. Treat it as a troubleshooting fallback. Switching to WineD3D sometimes fixes a specific graphical glitch that DXVK has, at the cost of speed. It is not a performance choice.
Match the wrapper to the game's API, not to vibes. A DirectX 9 game on DXVK. A DirectX 12 game on VKD3D. WineD3D only when something is visibly broken and you're testing. Picking the wrong wrapper is one of the most common reasons a game "doesn't work" on hardware that is otherwise fine.
CPU cores and memory: what they actually do
The container settings include a CPU core count and a memory size. Here's the honest version of how they behave.
More cores help up to a point, and the point is roughly "what your phone actually has." Setting 8 cores on an 8-core phone doesn't double anything. Emulation overhead means diminishing returns arrive fast. A sensible starting point is around half to two-thirds of your phone's cores, then adjust if a game seems CPU-starved. Some games want fewer cores with higher per-core speed; the translation layer is often bottlenecked on single-threaded performance, which no core-count slider can fix.
Memory works the same way. Give the container enough for the game (a few GB covers most titles), but don't allocate 8 GB on a phone with 6 GB of RAM. The container and Android share the same physical memory. Starve Android and it starts killing background processes, including Winlator itself, and everything gets worse. Leave your phone breathing room.
Wine version: start with the default
Containers let you choose a Wine build. Newer Wine supports more programs and fixes more bugs. Occasionally a specific game prefers an older build. Start with the default or newest, and only switch when you have a reason. "The game crashes on launch and the driver, wrapper, and resolution are all correct" is a reason. Curiosity is not.
Per-game tweaks: one container per game type
Because settings are per container, the practical workflow is: one container per game, or at least per game type. An old DirectX 9 RPG gets DXVK, a low resolution, and Turnip. A heavier DX11 title gets the same driver but a higher resolution and more memory. Cloning a container is cheap. Rebuilding settings from memory every time you switch games is not.
When a game almost works but has one glitch (flickering shadows, a black menu, a crash at one cutscene), change one setting at a time and test. Driver version first, then wrapper, then Wine version. If you change all three at once and it starts working, you've learned nothing, and the next game will break the same way.
How to show FPS in Winlator
You can't tune what you can't measure. Turn on the FPS overlay so you're working with real numbers instead of gut feel.
In the container settings, look for the performance or overlay options and enable the FPS counter. It draws a small frames-per-second readout over the game while it runs. Use it to answer one question at a time: did that change help? Drop the resolution, check the number. Switch the driver, check the number. That's the whole method.
Two things the overlay won't tell you: it measures rendering speed, not input lag, and a high FPS number with stuttering usually means the CPU translation layer is the bottleneck, not the GPU. If the number is fine but the game feels choppy, the problem is almost never the graphics settings. It's the CPU struggling with translation, and the fix is a lighter game or a faster phone, not a different driver.
Settings myths you can ignore
- "Max out every slider." No. More cores and more memory past the sensible point make things worse, not better.
- "A newer Turnip is always faster." Newer is usually more compatible. Sometimes an older build is faster or more stable for a specific game. Test.
- "VKD3D makes DX12 games playable." VKD3D makes DX12 games launch. Whether they're playable depends on the game and the phone, and usually the answer is no.
- "Lowering resolution doesn't help much." It helps the most. It's the first thing to try, every time.
- "You need a gaming phone." You need a Snapdragon chip with an Adreno GPU and enough RAM. The "gaming" branding on the box is irrelevant. The device guide breaks down which hardware actually matters.
Frequently Asked Questions
How do I make Winlator faster?
Lower the container resolution first (1280x720 is a good starting point), use the Turnip graphics driver if your phone has a Snapdragon/Adreno chip, and match the DX wrapper to the game's DirectX version (DXVK for DX9-11). Give the container a sensible share of CPU cores and memory without starving Android, then turn on the FPS overlay and change one setting at a time so you can see what helps.
What are the best Winlator settings for low-end phones?
Lower everything that costs GPU work: drop the container resolution (960x540 or lower for old games), use the lightest driver available for your GPU, and stick to DXVK with DirectX 9-era games. Give the container modest memory so Android isn't fighting for RAM. Then pick games that fit the hardware. Settings can only do so much; a light game on modest settings beats a heavy game on any settings.
How do I show FPS in Winlator?
Enable the FPS counter in the container's settings (look under the performance or overlay options). It draws a small framerate readout over the game while it runs. Use it to test one change at a time: adjust a setting, check the number, and keep what helps.
Should I use DXVK or WineD3D?
DXVK for DirectX 9 through 11 games, which is most of what people run. WineD3D is a fallback for troubleshooting specific graphical glitches, not a performance option. If a game renders wrong on DXVK, trying WineD3D is reasonable. If it renders fine, leave DXVK alone.
How many CPU cores should I give the container?
Around half to two-thirds of your phone's cores is a sensible starting point. More cores help up to the point where emulation overhead and single-thread bottlenecks take over, and that point arrives sooner than people expect. If a game stutters despite a good FPS number, it's usually CPU translation struggling, and no core count fixes that.
Do Winlator settings apply to all games or per container?
Per container. Each container keeps its own driver, wrapper, resolution, core count, and memory settings. That's why the practical setup is one container per game or per game type: tune each one for what it runs and they never interfere with each other.